Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

XP pro in a Windows 2003 Domain

Status
Not open for further replies.

Smooth23

MIS
Dec 11, 2005
100
GB
Hello,

Has anyone ever had problems with XP pro on a Windows 2003 AD Domain? Well I do, and nothing too serious I hope, the problem is this:

All XP clients keep getting Event ID: 1054 logged and it reads.

Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

However all users can login. The two domain controllers are fine and event logs are all clean however, before i installed SP1 on the 2k3 dc’s, there were loads of ‘Usernv’ logs and i also had to tidy up DNS. (MS article 887303 helped with this)

Since this work was carried out, the domain controllers are performing much better, now it’s the dam clients…..

DNS is running on both domain controllers and the IP DNS config is setup as below: Is this correct?

DC1 Primary ip ad lDC1 IP address
Secondary ip ad DC2 IP address

DC2 Primary ip ad DC1 IP address
Secondary ip ad DC2 IP address

XP Pro clients have
Primary ip ad DC1 IP address
Secondary ip ad DC2 IP address

DNS is set to ‘Active Directory Integrated’ and ‘Dynamic updates’ are enabled for ‘Non secure and secure’

I have just read article 326152
and it suggests the NIC drivers are causing this so i will check this out.

But any feedback on this will be great… many thanks.
 
You might try downloading an Active Directory Checker. I use NETIQ ADcheck. It has been able to clue me in on some AD issues my network was having. This will at least let you narrow it down a little.
 
Downloaded ADCheck, a very useful tool, and all the results were good, no problems with DNS or replication or anything which was good.

I have also downloaded the most recent network card drivers for the D230m (Broadcom 440x onboard NIC), cleared the Application events, restarted and checked app event logs and there it was.... the usernv, 1054 log, ggrrr....

This is strange and it's not all Windows XP Pro clients, some are running with very clean event logs.

I will try re-join the machine to the domain tomorrow and see what happens.

Will let you know.
 
Hey all,

just thought i'd bring this back to the top to see if anyone has any suggestions, feedback or previous experience with these kind of errors.

Thanks
 
Smooth23,
I will try re-join the machine to the domain tomorrow and see what happens.
What was the result of this?
DNS is running on both domain controllers
You did not state the function of each.
Are they both located Locally?
Are you running Gb NIC's on the clients not connecting?
If so, have you tried another NIC or updating NIC drivers?
Are you using DHCP?

Try this on the PC's refusing to authenticate

Ipconfig /Release
Ipconfig /Renew

Check client connectivity by trying to 'ping' the DNS primary.

also try using the nslookup command to test whether the server can respond to DNS clients.

Some known conflicts




rvnguy
"I know everything..I just can't remember it all
 
Hi all,

Apologies for the delay in updating this thread, pressures of work an all that….

Any way, I disjoined, and then rejoined the windows XP work stations with the USERNV 1054 error and this resolved the problem.

I have run the group policy results within GPMC and all policies are applied successfully.

All is running fine.

Thank you all for your feedback.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top