Link to home
Start Free TrialLog in
Avatar of Bill H
Bill H

asked on

Server 08 RDS Issue

I am troubleshooting an issue for a friend, they have a RDS server (server 08) that is a hyper-V vm and it was working fine until the other day. No recent changes have been made that i am aware of. When trying to RDP into the box and use your domain login, i receive this message:
 the trust relationship between this workstation and primary domain failed

I can ping the DC from this server and i see the computer object for this server in AD.
I get other errors also in the event viewer such as:
3210 - stating it could not authenticate with the DC
1067 - The terminal server cannot register 'TERMSRV' Service Principal Name to be used for server authentication. The following error occured: Access is denied.
1055 - The processing of Group Policy failed. Windows could not resolve the computer name. This could be caused by one or more of the following:
a) Name Resolution failure on the current domain controller.
b) Active Directory Replication Latency (an account created on another domain controller has not replicated to the current domain controller).
Avatar of SaadAhmedFarooqui
SaadAhmedFarooqui
Flag of Pakistan image

are other computers able to authenticate with the Domain controller?
Avatar of Bill H
Bill H

ASKER

yes, only this one has this issue.
Check the DNS entries, are they pointing to the DC?
ASKER CERTIFIED SOLUTION
Avatar of 0x6
0x6

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Bill H

ASKER

0x6, yes i did this already and it took care of the issue.

What i was worried about is that if users were going to lose their user profiles when they logged in again (since i took it off the domain and rejoined it). I havent heard anything yet, so i'm assuming since the domain name did not change, their user profiles were not affected. Does this sound right to you?
Yes, their existing profiles will be used.
Good to know the issue is resolved. Correct. User profiles should not be affected.
Avatar of Bill H

ASKER

Any idea why the trust would just break?
The reason for this is computer/member server password mismatch with the domain.
Computers change their password every 30 days by default which has to be in-sync with the domain, and at that time if there was a miscommunication or network issue between the DC and a server then the passwords don't get synchronize, hence 'a broken trust'.
Avatar of Bill H

ASKER

Oh ok, that makes sense.
On the off chance was the RDS's time wrong? VMs sometimes have issues with holding time.

Philip
If you have trouble logging into the machine that's having this issue, just unplug the network cable and then log in.  Once you get logged in you can plug it back in and follow the procedure above.  

Thanks guys.