P
Peter Hornby
We have a number of servers in our test lab which are commonly accessed by
RDP. There is a small subset of these servers which one user, and one user
only, cannot successfully logon to. It seems as though the common
characteristic of the affected servers is that they're all set up by our lab
administrator to be members of a particular Active Directory OU.
When he supplies his domain credentials to the RDP logon screen, an error
dialog is displayed with the text: "The system cannot log you on due to the
following error: The RPC server is unavailable".
An entry is written to the server's application event log with source
Winlogon, and EventID 1219. The text for the message is "Logon rejected for
<user-id>. Unable to obtain Terminal Server User Configuration. Error: The
RPC server is unavailable".
This user can perform a successful RDP logon to other servers, and can
successfully logon to the affected servers directly. All other users can
logon to all servers with their domain credentials. The servers are mostly
running some flavor of Windows Server 2003.
If anyone has seen this and worked out what's going on, that would be
wonderful. However, I'm just as interested in any suggestions on how to
debug this problem. I'm not a Terminal Services/RDP expert, so I'm not
familiar with the expected path of the logon protocol and how you might go
about diagnosing problems with it.
Thanks,
Peter Hornby
Unisys
Mission Viejo/CA
RDP. There is a small subset of these servers which one user, and one user
only, cannot successfully logon to. It seems as though the common
characteristic of the affected servers is that they're all set up by our lab
administrator to be members of a particular Active Directory OU.
When he supplies his domain credentials to the RDP logon screen, an error
dialog is displayed with the text: "The system cannot log you on due to the
following error: The RPC server is unavailable".
An entry is written to the server's application event log with source
Winlogon, and EventID 1219. The text for the message is "Logon rejected for
<user-id>. Unable to obtain Terminal Server User Configuration. Error: The
RPC server is unavailable".
This user can perform a successful RDP logon to other servers, and can
successfully logon to the affected servers directly. All other users can
logon to all servers with their domain credentials. The servers are mostly
running some flavor of Windows Server 2003.
If anyone has seen this and worked out what's going on, that would be
wonderful. However, I'm just as interested in any suggestions on how to
debug this problem. I'm not a Terminal Services/RDP expert, so I'm not
familiar with the expected path of the logon protocol and how you might go
about diagnosing problems with it.
Thanks,
Peter Hornby
Unisys
Mission Viejo/CA