Discussion Locked

Can't find DC in XP... at first.

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Odd thing happening. We have a Win2K server, and 95/98, and some XP clients. The XP clients are getting event viewer errors saying it can't find the Domain Controller, and the W32 time is complaining that it can't sync. When it loads, though, the network is accessible. A minute or two later, W32 syncs. It looks, from the log, like the time and Userenv logon stuff is running before the network/tcpip services are all loaded. When I set the computers up originally, they found, and joined, the domain with no problem. Is it possible that these things are running before the network components are ready? Is that a problem?
I also have one user who gets a notice that network drives cannot be reconnected. If he opens "my computer" and clicks on the drive, it connects, and works fine from then on. Related?

1 reply

by ben.t[at]paradise.[windows2003server].nz

I suspect the network drive is a related issue.
I guess you might want to try checking you've got TCP/IP doing its thing okay with no DHCP errors or are using static IP addresses?
Doesn't sound like a driver issue, but more DNS or similar.
Maybecreate another hardware profile, with another NIC (whichever HW profile you're in, disable the 'other' NIC...) and re-create the ip settings to test with?
I'm not actually sure if you'd get away with re-creating you LAN settings very safely, so best to do it under a different HW profile so you can at least boot back to square 1.

This discussion is closed to new replies.