Windows Server 2003 Terminal Services Manager you could not be authenticated on this server
Hi!
I keep getting an error when I try to view the remote users for several servers in my domain. When I open terminal services manager, the servers are displayed, but when I double click on them to display the logged on users, in the pane to the right, I get an error that says "you could not be authenticated on this server". For generally about 5 minutes, I keep getting the same error, but if I leave TS Manager open, after about 5 minutes, I'm able to authenticate and see the server. This began happening out of the blue about a month or so ago. I use this regularily as we are in a complete RDP environment for all remote users. Having to wait 5 minutes is sometimes the difference between being able to fix a problem and not.
I've done some online research and found that it seems people are saying to make sure that the "remote registry service" is started on the target server. Remote registry service is started on all the servers with the specified issue. Does anyone have any other suggestions?
There have been no upgrades to the OS except for updates that have been applied by Windows Update.
I keep getting an error when I try to view the remote users for several servers in my domain. When I open terminal services manager, the servers are displayed, but when I double click on them to display the logged on users, in the pane to the right, I get an error that says "you could not be authenticated on this server". For generally about 5 minutes, I keep getting the same error, but if I leave TS Manager open, after about 5 minutes, I'm able to authenticate and see the server. This began happening out of the blue about a month or so ago. I use this regularily as we are in a complete RDP environment for all remote users. Having to wait 5 minutes is sometimes the difference between being able to fix a problem and not.
I've done some online research and found that it seems people are saying to make sure that the "remote registry service" is started on the target server. Remote registry service is started on all the servers with the specified issue. Does anyone have any other suggestions?
There have been no upgrades to the OS except for updates that have been applied by Windows Update.
What Antivirus/AntiSpyware/Anti
ASKER
I'm using Vipre Enterprise. It isn't any issue on the other servers...only on this cluster of 4.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Clint--thank you for your comments and suggestions.
I do have a solution to report back. It turns out it was a time issue on the virtual servers. For some reason, the servers weren't synching their time with the DC. So, once I corrected the time to match the DC (and the current time), the authentication issue went away. Like you said, complicated issue, simple solution.
I do have a solution to report back. It turns out it was a time issue on the virtual servers. For some reason, the servers weren't synching their time with the DC. So, once I corrected the time to match the DC (and the current time), the authentication issue went away. Like you said, complicated issue, simple solution.