Computer can't to Windows Server 2003 domain

My computer can no longer connect to the domain but no other computers are having this problem. The client is an XP Pro machine and the Domain is Windows Server 2003. Here is what I have tried so far:
1. pinged the domain controller by name: ping request could not find host
2. pinged the domain controller by IP and many other devices on the network: SUCCESS
3. restarted the computer
4. reset the computer account in Active Directory
5. restarted the computer
6. restarted the domain controller
7. restarted the computer: I was able to ping the domain controller for a few moments and then it started failing again
8. restored the computer to the latest restore point before this problem

Does anyone have any ideas on what I can do to fix this?

Thanks,
Luke
bornhuskerAsked:
Who is Participating?
 
feptiasCommented:
The setting may not have changed from last night, but it would strongly recommend that you change it if you want to fix the problem. Your preferred DNS server should be set to the internal DNS server. It has to look at that DNS server in order to find the domain controller and to authenticate your login.
0
 
feptiasCommented:
What is the setting for your Preferred DNS server? You can see this typing the following command at the command prompt:
ipconfig /all
0
 
Toni UranjekConsultant/TrainerCommented:
Name resolution is very complex process. Client can perform up to seven different name resolution methods to find the resource.

1. Client resolver cache (ipconfig /displaydns)
2. Hosts file
3. DNS server
4. NetBIOS name cache (nbtstat -c)
5. WINS
6. Broadcast
7. lmhosts file

If your clients and domain controllers are on the same subnet they can use broadcast as one of the options.


0
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

 
bornhuskerAuthor Commented:
The preferred DNS server is pointing to my ISP's DNS server then to my internal DNS server. However, that setting has not changed from when I was able to connect to the domain -- last night.

thanks.
0
 
bornhuskerAuthor Commented:
I changed my preferred DNS server to my internal DNS server and it started working. The internal DSN server should be my primary DNS server and I should use the ISP's DNS server as a secondary server.
0
 
Toni UranjekConsultant/TrainerCommented:
The prefered DNS server on your client should always point to your internal DNS server which should use external ISP DNS as forwarder! In your case, if your ISP DNS server responds, client will not issue another DNS query to your internal DNS.
0
 
Toni UranjekConsultant/TrainerCommented:
You should NOT use IPS DNS as secondary DNS. Your ISP's DNS  doesn't know how to resolve SRV resource records!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.