We help IT Professionals succeed at work.

Trust Relationship Failed

Medium Priority
469 Views
Last Modified: 2012-05-06
I replaced a network card in my server over the weekend and now none of my clients can login.  They get stuck at "Applying your personal settings".  If I disconnect the network card, I can get access to the machine.  I have tracked this problem down to a failed trust relationship.

I would like to just re-establish this somehow but that doesn't appear likely.

So, I've tried to re-join the domain but I can't do that either.  When I connect the cable again, then try to join the domain I get "The network path was not found"

I'm having a hard time dealing with the idea of reconfiguring a network because of a bad NIC.  
Comment
Watch Question

Commented:
Are there any errors in the event logs of the server and the clients?

Author

Commented:
on the client side-

Source: Userenv
ID: 1053
User: NT AUTHORITYSYSTEM

Windows cannot determine the user or computer name.  (The specified domain either does not exist or could not be contacted).  Group Policy processing aborted.

On the server - there are a few.  The most important seems to be -

Windows cannot access the gpt.ini for the GPO


Commented:
Please login to a client computer with the network cable disconnected, then after login connect the network cable. Does the client get an IP address? If yes, can you ping the server on its IP address? If yes, can you ping the server with its DNS name.

For me it sounds like a DNS issue. Does the server has the same IP address with the new network card? If not, make sure that the DHCP server sends the correct DNS server IP address to the clients.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts
Commented:
I suspect that your DNS server was bound to the network adapter that failed on the server. Now that it's been replaced, the DNS server (or possibly WINS, but ... more than likely DNS) has failed.

You can test this by adding an entry of the format:

DOMAINNAME.COM              IP.ADDY.OF.DC

into your c:\windows\system32\drivers\etc\hosts file (where ip addy of dc) is the ip address of any domain controller in your network that the host can ping.

If setting this in there works, then you have a name resolution issue.

Troubleshoot DNS functionality, Correct IP address resolution, and host connectivity.
Commented:
I reconnected all the machines to the domain.  
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.