Bug 7279 - wxp fails to join S4 AD DC / cannot login using domain account
wxp fails to join S4 AD DC / cannot login using domain account
Status: RESOLVED FIXED
Product: Samba 4.0
Classification: Unclassified
Component: AD: LDB/DSDB/SAMDB
unspecified
Other Solaris
: P3 normal
: ---
Assigned To: Andrew Bartlett
samba4-qa@samba.org
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-03-22 15:16 UTC by Bernd Markgraf
Modified: 2013-02-18 13:30 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bernd Markgraf 2010-03-22 15:16:54 UTC
while testing S4 AD DC I installed a wxp test box. It seems to join the domain ok (I get a welcome message) But after reboot I am told that the name (machine name?) already exist on the network and the domain oculd not be joined. Snooping the network I see nothing suspicious except for the last to packets:

192.168.2.33 -> 192.168.2.255 NBT NS Registration Request for BLA[0], Success
192.168.2.22 -> 192.168.2.33 NBT NS Registration Response for AKUMA[0], Active Error

192.168.2.22 being the S4 server, 192.168.2.33 being the client. Both client IP and hostname (bla) are uniq on the network. The S4 AD DC was freshly provisioned. Upon login I get a message that the domain was unreachable and could not be used. The debug output from the server shows incoming stuff from the client though - I even got a message that the machine account was authenticated. No funny stuff here as well.
The Windows7 client joins and works just fine with the same server (same settings, same database, different client ip/name)
Comment 1 Matthias Dieter Wallnöfer 2010-03-24 11:34:47 UTC
We provide a very good support for Windows XP as a client. Might therefore the client itself be the problem? Do you have another Windows XP client ready for a join test?
Comment 2 Andrew Bartlett 2010-03-24 17:07:34 UTC
From the trace I've seen privately, this looks very odd, and very real.  I cannot see how the client triggered this particular response. 
Comment 3 Bernd Markgraf 2010-03-26 03:29:30 UTC
(In reply to comment #1)
> We provide a very good support for Windows XP as a client. Might therefore the
> client itself be the problem? Do you have another Windows XP client ready for a
> join test?
the client was a fresh install of wxp pro sp2, no patches though (I just wanted to check if xp works). I'll try to find another xp box to test.
Comment 4 Andrew Bartlett 2010-03-26 03:35:22 UTC
Don't spend too much time on it.  I've examined the trace you provided privately, and if it is complete, no matter the client, it should not be doing that. 
Comment 5 Bernd Markgraf 2010-03-26 07:23:54 UTC
i tried another box with wxp pro this time sp3, halfway recent patchlevel. same result. 
Comment 6 Matthias Dieter Wallnöfer 2010-04-17 07:57:09 UTC
What to do here? Still the same issue?
Comment 7 Bernd Markgraf 2010-04-18 14:40:14 UTC
gotta check that again... right now I'm up to my ears in w7 clients though.
Comment 8 Matthias Dieter Wallnöfer 2010-09-11 12:41:41 UTC
Still an issue?
Comment 9 Matthias Dieter Wallnöfer 2010-10-01 08:38:01 UTC
I close this until I hear again from you.