Connecting XP Pro to Win2000 server

I have tried the answers from the previous questions and am still having this problem.  

So background information:  We have 8 XP Pro machines already connected to the 2000 server.  The company recently bought a 9 XP Pro machine to be added to the domain.  I added the machine to the domain and could access the shared netowrk drives.  I then started updating Norton, XP, Office, etc etc.  After I restarted the computer I have received the following message:
The domain name [domain name] might be a NetBIOS domain name.  If this is the case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain [domain name]:

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.[domain name]

Common causes of this error include the following:

- The DNS SRV record is not registered in DNS.

- One or more of the following zones do not include delegation to its child zone:

[domain name]
. (the root zone)

For information about correcting this problem, click Help.

Since none of the other solutions worked I decided to wipe the system and reinstall everything.  After doing that I am still receiving the message above.  

I have compared the settings from all the XP machines already on the Domain with the settings of the new XP machine and other then then Domain name everything is correctly set up.  

If anyone can help me out it would be much appreciated.
Who is Participating?
Is the workstation registering with DNS? Check the IP configuration if you're not sure.  Might just be a missed checkbox.
vds450Author Commented:
Just checked to make sure that the XP machines was setup up to register with the DNS and it is.  
We Need Your Input!

WatchGuard is currently running a beta program for our new macOS Host Sensor for our Threat Detection and Response service. We're looking for more macOS users to help provide insight and feedback to help us make the product even better. Please sign up for our beta program today!

As you have reinstalled the OS, it could not be something that is on the client that is causing this. The server also should be working as the other systems are connecting to that. So, please try changing the name and the IP of the system in question and try connecting, it could be that these settings for this particular client on the server are somehow corrupted.
NetoMeter ScreencastsCommented:

Can you check whether the radio button "enable Netbios over TCP/IP" under "TCP/IP properties/ Advanced - WINS tab"  is chosen?

vds450Author Commented:
In response to cooljai1:
I have tried renaming the system in question with no luck.  The network uses DHCP provided by a linksys router (I have turned it off and used the 2000 server one also) but still have no luck.

In repsonse to NetoMeter:
I do have Netbios enabled over TCP/IP.  
Ron MalmsteadInformation Services ManagerCommented:
logon to the local machine......put back on work group....then reboot.....rejoin domain...and reboot again.  That always works for me.
vds450Author Commented:
Thanks for all the help.  It  ended up being Norton Personal Firewall that was causing the problem.

/sigh Why didnt I even think about turning that off? Oh well
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.