• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 367
  • Last Modified:

Windows XP client drops the Domain Controller Connection

Dear Sir,

I have windows 2003 Domain Controller having proper Primary DNS & Secondary DNS.  I have joined all my Windows XP machine to this domain controller.

Every day few of these XP client machine throws the following errors. Rest of all are working fine.

"Windows cannot connect to the domain either because the domain controller is down or other wise unavailable, or becuase your computer account was not found"

Due to this error, I have to again join this Windows XP client to the Domain Controller.

Please help
0
liji77
Asked:
liji77
  • 2
  • 2
  • 2
1 Solution
 
adamdrayerCommented:
I know you say its proper, but can you quickly tell me what the DC and workstations have configured as their DNS servers?  Also, verify that the time on the workstations and server are synchronized.  How many DCs do you have?  Do you know where the Global Catalog Sever is?

Next time a computer cannot join the network, try reseting the computer account with NETDOM.exe just to test it:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q260575

Due to your terminology, I assume you have some programming experience.  Did you write any custom network scripts that access LDAP or the registries?

0
 
liji77Author Commented:

1. Domain Controller is Active Directory with Primary DNS
2. I have additional Domain Controller with Seconday DNS
3. All the workstation's DNS  is the above machine's IP address
4. I have only one domain controller
5. Global catalog server resides in the Local Area Network
6.  Yes I have wrote some scripts in vb to get the appropriate logon script

Please feel free if u need more clarifications
0
 
adamdrayerCommented:
2. I have additional Domain Controller with Seconday DNS
4. I have only one domain controller

These seem to be conflicting statements.  I'm just having a difficult time understanding your setup.  You only have one domain controller?  Then it should be the only entry in both it's own DNS server configuration and the clients as well.  You should never have a DNS server that is not a DC in your domain appear anywhere in the DNS configuration.  Even if its the 2nd or 3rd one, DNS does not always use the first one available and you will have outages like this.
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
georgecooldudeCommented:
Try adding this to your domain logon script.

NET TIME \\servername /set /y

It will sync the time with your domain controller and the PCs. Then see if you get the same issue after a few days.
0
 
liji77Author Commented:
Thanks for your comment.  I have now added "NET TIME \\servername /set /y"  in the logon script.

The user who are logged on the domain controller are restricetd user and the time is not getting sync.  I tried to logged on to the server using administrator account, the time is getting sync.

What I have to do to sync the time for the restricted user. I mean the user those not member of the administrator group.

regards,

avs
0
 
georgecooldudeCommented:
http://www.winguides.com/registry/display.php/1118/

Try the following reg hack on a machine and set the time server either to an official goverment one or set it to your domain controller which is probably best. That way the time in ur organisation is more organised.

Make sure you do a backup of the reg before u make changes
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

  • 2
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now