How to put an XP machine on 2k-server network?

[SpiffGQ]

I just got three new Windows XP-based machines, and I need to put them on my Windows 2000 Server-based network. Two of the machines hopped on just like they were suppose to, but one of them is being a bit of a brat, and I'm not sure what's going wrong.

I go to System Settings (either through Control Panel or by right-clicking on the My Computer desktop icon). I click on Computer Name tab and click on the Network ID button. It is a network id wizard.

1. Welcome to the Network ID Wizard -- clicked on Next.
2. Selected "This computer is part of a business network". Clicked Next.
3. Selected "My company uses a network with a domain". Clicked Next.
4. Clicked Next.
5. Entered the Administrator password and domain. Clicked Next.
6. Entered the computer's name and domain. Clicked Next.
7. Error

For the error step above, the first two computers would usually ask me for a user name and password, and then all was good to go. But not for this last one.

The error I get is as follows (it is paraphrased because I couldn't copy it, print it, or email it, so I had to hand write it. Ugh):

Quote:

A domain controller for the domain DOMAIN could not be contacted.

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

...

Any ideas? The problem is obviously a configuration error with the client computer, because all of the other computers work just fine. Sorry, too, for the newbieishness (now there's a word for ya ) of this question. This is what happens when the suits upstairs assign a Unix programmer as a Windows network admin. I have a lot to learn (any good links, btw?). Thanks for your help.

[FatalException]

Sounds like your networking isn't even working properly on this client machine. Can you ping out on the system to the internet? Does the client PC have a valid IP address assigned by your server or router? Can it ping the DNS name of the server you are connecting to?

[MadMan2k]

You might, next, try uninstalling the TCP/IP protocol in Network Connections, and adding it again.

[Front242]

How many seats do you have set up on you win2k? Five is usually the default so if you have more computers connecting than seats you may get an error.

[SpiffGQ]

Quote:

Originally Posted by FatalException

Sounds like your networking isn't even working properly on this client machine. Can you ping out on the system to the internet? Does the client PC have a valid IP address assigned by your server or router? Can it ping the DNS name of the server you are connecting to?

I can ping other machines on the network, the server itself, and www.google.com. So there is something there, which probably just demonstrates that it isn't a hardware problem but a configuration setting somewhere.

[SpiffGQ]

Quote:

Originally Posted by MadMan2k

You might, next, try uninstalling the TCP/IP protocol in Network Connections, and adding it again.

I'll try that -- tomorrow.

Quote:

Originally Posted by Front242

How many seats do you have set up on you win2k? Five is usually the default so if you have more computers connecting than seats you may get an error.

[mikey71497]

Instead of using the wizard, just right click on my computer and go to properties. Click on the computer name tab, and then click on "change." Dont use the wizard. Once you enter in the new computer name, and the new domain name, it will ask you for a admin username and password, or someone's username and password with the appropriate rights to make this change. If that dosent work, make sure you are getting a valid IP addy for your network. Also, try joining it to a workgroup first, then remove it from a workgroup and try adding it to a domain.

[GroundZero3]

yup thats how we add win2kxp machines to a domain

[hokie64]

I also remember, for some reason, (and i could be wrong) that you are NOT able to change the number of seats once you install. You can only change the license to per server, and it gets messy. In my MCSE classes they told me to jack up the number of seats no matter what, just to avoid a potential problem.

[DVNT1]

So your internal Windows related domain name is really "Domain"? If so, the computer may not be using the correct DNS server.

As mentioned, go first as Workgroup in this case so you can easily check DNS server and related settings.