Terminal Services / Remote Desktop Troubles...

[justinmann]

I just got finished configuring a server with terminal services on it, but I'm getting the following message when I try to connect to it "The connection was ended because of a network error. Please try connecting to the remote computer again." I can't seem to find any substantial information on this particular message. Microsoft gives the very helpful advice "contact your server administrator." Ack! 🙂
I'm being rejected in this manner on the LAN side. I've checked my firewall settings on both the server 2003r2 and the windowsxp that I'm trying to connect to it. Additionally, I can remote desktop from the server to the xp machine with no troubles at all, so it doesn't seem like a general networking problem. Finally, I can telent to port 3389 normally.
I've configured several servers with terminal services now, and I've never run into anything like this before. Does anyone have any ideas? Please? 🙂

 

[nweaver]

don't install terminal services, that is the "terminal server" not the RDP "Remote Management" like 2kAdvanced Server. Remove terminal services, and enable remote desktop just like XP (computer properties)

 

[justinmann]

Thanks for the input. 🙂

I figured out what the problem was by doing a wee bit more searching, and I feel like I should leave the answer here for any more wayward administrators. 🙂 The key, of course, was in the event viewer (duh).

Event Type: Error
Event Source: TermDD
Event ID: 50
Description:
The RDP protocol component "DATA ENCRYPTION" detected an error in the protocol stream and has disconnected the client.

A potential race condition between the Icaapi.dll and Rdpwsx.dll dynamic-link libraries (DLLs) may cause the private certificate key on the Terminal Services server not to be synchronized.

It's not exactly what I would have guessed, but hey, following the knowledge base (deleting a few registry keys) fixed the problem. (323497)

And there was much rejoicing!

Justin