Question Locked

Problems with Windows Server 2003 domain controller

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a Windows 2003 server (not SBS) and 10 winXP pro machines accessing it. After 3 years of working fine, I have one machine that takes a very long time to log in (5-10 times as long as other machines) and then cannot access any network share. I can access the internet (direct from hub to modem) and MS Exchange Server (on the same machine as the shares), but not any share. Sometimes I get a "No Domain controller available message). When I move the PC to another location, i get the same problem, and when I put a machine in this location, i do not have a problem. Happens regardless of who is logged on. I have rebuilt the machine to no avail.

4 replies

by swesterhoff

Are you pointing to the same DNS server as the working machines? Turn off DNSCache (DNS Client) in services and make sure your DNS queries are working by doing NSLOOKUP and entering the servername where the shares are and also just the domainname all by itself. You should see results back with IPs of the server. Are they accurate? Can you do a NET USE \\SERVER-NAME and see shares? If so, can you DIR \\SERVER-NAME\SHARE-NAME and see files? Next look at the event log for errors on the server you are connecting to.

by animatech

Try to reset the computer account on the server.
If not working try and delete and re-create the computer account (Or via AD or by taking the PC of the domain and back).
You may also want to run "arp -a" on cmd and clear any static IP address (Be careful not to delete ones that you are using if you are using any static address)
To delete you are using "arp -d xx.xx.xx.xx where xx is the IP address).

by swells

Try another network card, sometimes a lot of weird problems can occur as nic's start to die :). I mean ther client NIC of course .....

This discussion is closed to new replies.