Discussion Locked

Join WinXP Pro to W2K Server Domain

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
As network supervisor I need to join a new WinXP Pro Desktop-usually very easy. Performed usual steps to configure for end user - among other steps, uninstalled Norton, turned off Win Security Center Firewall, entered domain user name and password in Network ID, etc. then plugged in network cable, opened my computer to properties to join domain on server. Surprised to see LAN already connected, and able to ping server and other network machines, can't ping it back. But tried to change from workgroup to domain, and join - mssg - can't detect domain, make sure spelled right. Used other network machine as example to validate names,spellings. Spent two hours on phone with manufacturer techie-stumped. Ran Diagnostics-all okay. Suggestions?

15 replies

by sgt_shultz

...otherwise how will i narrow down all those links i get when i go to support.microsoft.com and search the Windows XP knowledgebase using 'join domain error' as my keywords...there's bunches of reasons for this to happen. it is dns related betcha. your error will help us. also look in the event logs on the client that should help also

by cg it

if your running DHCP, your steps "entered domain user name and password,... then plugged in network cable" may not have allowed sufficent time for DHCP to provide the workstation with an IP address and DNS servers.

run ipconfig/all and if you have a valid IP address on the subnet the domain is on, try rejoining with an account that has privileges to "join computers to domain".

If you run ipconfig/all and get a 169.xxx.xxx.xxx ip address run ipconfig/release then ipconfig/renew to obtain a valid ip address from DHCP or you can configure TCP/IP with a static address on the same subnet as the domain.

by p.j.hutchison

You might have got an APIPA address which is an automatic IP address when there is no DHCP server available when you boot up the PC.
An APIPA address is non-routable so it might not be accessible outside its subnet.
You need to renew the IP address (see other reply) to get a valid IP address and other info to allow you to join the domain!

by pritchards

Use complete user name ie. domian\.
If this does not work, machine name...Ip address duplication could be reason. Sysprep tool is very handy to strip SID and then try again.

by noly_big_boy

You said, "can't ping back". Try to reconfigure your ip (if you're using a static ip) that is in the range of your pre-defined ips. Recheck the domain name that you were entering and check also the username and password which you are using to grant access to the network if it has a priviledge in order for you to join the domain. Worse, replace your network card and do it from the start again.

by stuck_in

I have had a similar problem with a lot of laptops. They could se the Internet, ping everything and otherwise worked fine but would not join the domain. My problem lied in what administrator account I was using to setup up the PC for the domain. Since I have multiple admin accounts there should not be a difference but the PC liked one better than another even though they had exactly the same rights.

by fieldy

Hi,

Did you point the client NIC Card DNS to the server IP? sounds like that is the issue here. Try to ping the machine NETBIOS names, instead of the IP's (Office1 etc)Also, the error meesage should give you a details TAB, which if you click on it, may point out which type of issue it is.

Let me know how you get on??

Thanks

by jprice53

Make sure when you log admin rights... you enter user name ... tab to password and enter Domain/password to achieve access. Leaving the domain out leaves you out.

by tjonas

I had that situation once before. Make sure your computer BIOS name is not the same as soemone already on the network. Also make sure if you using static IP that is not used already. To join domain you must have login with admin right to the domain.
Hope this helps.

by chris

I would also check WINS, W2K and XP are not supposed to rely on WINS, but I have had experience in the past where by entering the server into the lmhosts file and adding the #PRE, I get the desired result.

When you say you can't ping the local host PC, you're pinging the netbios name, and not the IP addr. itself. try that too, as the others mentioned run "ipconfig /all" check DNS and WINS entries, and note host IP addr. then from server ping host IP addr. and netbios name. if no reply to name ping, DNS is not working right. enter server into lmhosts file on local PC, remove .txt extension and reboot. Also verify that the client has an entry in your DNS servers host table.

The commment about the auto-address not being routed is irrelevent, 172. and 192. are non-routed also and they are the most common private subnets in existence, in fact for this reason, I don't want my private net to be routed into public space.

by ron

This really sounds like a DNS issue. Are you using your domain controller for DNS. Do you have the correct DNS entry in the workstation. I have had the same problem several times, and it was always am incorrect DNS setting.

by mjunderwood

Can you see this machine name in network neighborhood ? Has this machine name been added to the domain ? If not add the machine name, release the ipconfig, power down and up and try again.

by tejas73

I faces simmilar problem with my laptop and i solves it by removing DNS entry fom the active directory and them rejoining it to the domain

This discussion is closed to new replies.