PDA

View Full Version : Computer not wanting to connect to the domain

AuthorityAction
11 Oct 2004, 8:55pm
I get a call from one of my companies asking me to come in quick because they're having trouble. First off this it my day off and they woke me up and thats when all my troubles began. When I first got there none of the computers would connect to the server to use a program called Business Works. I got all the computers working and connect except for one. This one computer will not connect to the domain. I took if off the domain to test somethings and then it wouldn't reconnect. So I tried logging on to the local machine, which I didn't know the user name or password for. :rolleyes: When I finally got in I couldn't view any of the files/folders on the server. I can't reconnect to the domain. I can't see any of the other computers on the network. I tried accessing the server through its IP \\192.168.2.2\ and still nothing. I can ping the server and the rest of the network and I can get on the internet. This is confusing the hell out of me :scratch: If you have any ideas for me to try please post them quick. Thanks in advance for any help! Let's hope this is an easy fix that I just over looked after being there for 4+ hours.

It's time to take a nap ;D
primesuspect
11 Oct 2004, 10:03pm
Is the client OS XP or 2000?
AuthorityAction
11 Oct 2004, 10:04pm
I guess that information might help. The computer is running 2000 pro and the server is 2000 server ;)
Shorty
11 Oct 2004, 10:38pm
Test your active directory...

1. Create a test AD user account.
2. Make that account a member of the domain administrator group
3. Remove the PCs account from AD.
4. Use that created test admin account to add the machine to the domain.
5. Check to see if it's definitely added.

If not, you have have a problem with your server.
AuthorityAction
11 Oct 2004, 10:46pm
Alright I will try that while I'm there, thanks.

Could there be a problem with the server even if all the other computers can connect to it ok? It's just this one machine that's giving me trouble :mad:
primesuspect
11 Oct 2004, 11:53pm
Don't discount raw connectivity problems either. Try a sustained ping with large packets and see if there is any packet loss.

ping -t -l:65500 server ip

This will ping with huge packets (64K) until you tell it to stop. Let it ping about 20 times to see if there is any packet loss. Hit CTRL-C to abort the ping.