Will not join domain properly

Hello,
      I have a computer giving me fits joining a domain. I set it up offline and had no issues. When I connect it to the network and join the domain it joins t
he domain very quickly with no errors. When it reboots, as required, it takes forever to load personal settings to load. I am logging in as an administrator. It does not connect network drives as told to through login script but does connect to the user folder. I can browse the network and access the internet but if I try to add a user and browse to find the user it tells me the server is unavailable. I have slicked and reloaded twice thinking that something may be corrupt. My computer, which is usually fine starts running very slow and I cannot connect to the Active Directory Manager. It tells me the domain is not available. If I take the trouble computer off the network and reboot mine I can then again access the Active Directory Management console. Could this be a bad nic?

Thank you
LVL 1
daskas27Asked:
Who is Participating?
 
jhyieslaCommented:
A NIC is always possible, but you could start a perpetual ping to something and watch it for awhile.

Try this. From the commuter itself, remove it from the domain. Then wait for a bit to make sure that everything synchronizes. then go to your ADUC and check to make sure that it's gone. Then go to all your DNS servers looking for that name AND the IP that it's using to make sure that no other computer has or had that IP in DNS. Remove all entries for that name and either remove any other computers with that IP or if there really is another compeer running with that IP, assign a static IP to this one.  If something else that is really running has that IP you should have gotten a conflict message, so a running computer with that IP is not very likely. Then check your WINS server, if you have one and delete any WINS entries for that IP that are associated with this computer and any that might still be there in error from some other computer that is no longer in service.  As with DNS make sure you are not nuking something that wanted that IP that is still active.

After all that is done, rejoin this computer to the domain, changing the IP first if it was necessary from the steps above and see if things straighten up.
0
 
Juan OcasioApplication DeveloperCommented:
Are you set up for DHCP?
0
 
Red-KingIT ManagerCommented:
You might possibly have a duplicate IP on the network.
Verify your network configuration. If its DHCP then make sure that the IP you're receiving has all the right information. Check the entry in DNS.
Watch the traffic going in and out of the nic using something like Wireshark.
Check the Event Viewer of the PC for errors in the System Log and Application log.
Check the Event Viewer of the Domain Controllers for errors too.

That should give you a better idea of what is going on and give you some more places to look too.


0
Get Cisco Certified in IT Security

There’s a high demand for IT security experts and network administrators who can safeguard the data that individuals, corporations, and governments rely on every day. Pursue your B.S. in Network Operations and Security and gain the credentials you need for this high-growth field.

 
daskas27Author Commented:
Yes, we use DHCP.
0
 
daskas27Author Commented:
I do not see any ip conflicts. This is a very small network. 15 to 20 users.
0
 
jhyieslaCommented:
If your ADUC, DNS and WINS looked clean, you might try rebooting the DC(s). Typically if there are no naming or IP anomalies, Windows machines will join a Windows domain without issue.
0
 
daskas27Author Commented:
I know. That is what makes this so strange. I have never seen it before. It impacting other machines on the network scares me the most.
0
 
jhyieslaCommented:
That's why I was thinking that there was some naming or IP issue with this machine.

You might check the health of your domain:

http://techsterity.wordpress.com/2011/03/18/ad-health-check-server-2003/
0
 
Red-KingIT ManagerCommented:
Did you check the event viewers for any errors related to this? Its an invaluable source when dealing with issues like this. The only drawback is that there is a big volume of information but you should be able to narrow it down to a reasonable timeframe from when you were doing this.

0
 
daskas27Author Commented:
I checked the event viewer on the DC and found nothing.
0
 
daskas27Author Commented:
It was the NIC!
0
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.