15 replies
by sgt_shultz
by sgt_shultz
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.
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
by stuck_in
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
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
by mjunderwood
by tejas73
by mcleodcomp
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending