Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Failure to join domain

Created: 20 May 2010 | 4 comments
Art W's picture
0 0 Votes
Login to vote

I am trying to push an image to XP SP3 clients from a GSS 2.5.1 (build 2266) and receive the following error :
Failed to join Domain xxxx: Logon failure: unknown user name or bad password.
The tasked completes all tasks successfully until the configuration task after the 'to Operating System' task and then get this warning.  I have double checked the Support Domains List and the proper domain name, user name and password are there.  I can successfully push the image using the same domain, username and password if I use sysprep and include that info in the sysprep.inf file. 
Any help where to look for the problem would be appreciated.
Thanks

Discussion Filed Under:

Comments

Nitin's picture
20
May
2010
0 Votes 0
Login to vote

DNS issue

Hi,

DNS failures really are responsible for the vast majority of all AD problems, and so a packet trace is the most important starting point to verify that everything is 100% and that the replies to the queries for the various _msdcs records are OK and look sane. Please check that you have set the appropriate DNS.

Please send NetSetup.log which is typically located at C:\Windows\debug to investigate the problem. Also attach answer file.

Regards,
Nitin

If you feel your issue has been addressed to, please use the "Mark as Solution" link for the relevant thread

Nitin's picture
20
May
2010
0 Votes 0
Login to vote

Also send the setup

Also send the setup information (AD, Network, static dynamic ips etc)

Regards,
Nitin

If you feel your issue has been addressed to, please use the "Mark as Solution" link for the relevant thread

aka001's picture
10
Jun
2010
0 Votes 0
Login to vote

Are you using static IP addresses?

Are you using static IP addresses on your machines? If so there is an issue assigning the DNS settings correctly in Windows PE that could potentially trigger this issue. Let me know and if this the case, I may be able to provide a workaround.