Trust Relationship Failed

Posted on 2009-02-17
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.  
Question by:fekdep
    LVL 21

    Expert Comment

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

    Author Comment

    on the client side-

    Source: Userenv
    ID: 1053

    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

    LVL 21

    Assisted Solution

    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.
    LVL 11

    Assisted Solution

    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:


    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.

    Accepted Solution

    I reconnected all the machines to the domain.  

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Maximize Your Threat Intelligence Reporting

    Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

    #Citrix #Citrix Netscaler #HTTP Compression #Load Balance
    Join Greg Farro and Ethan Banks from Packet Pushers ( and Greg Ross from Paessler ( for a discussion about smart network …
    After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
    This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor ( If you're looking for how to monitor bandwidth using netflow or packet s…

    779 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    14 Experts available now in Live!

    Get 1:1 Help Now