• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3199
  • Last Modified:

Remote Desktop

I am running a Windows 2003 Server and I am having trouble using the remote desktop feature.  This feature has been working for over a year now but for some reason has started giving me some problems.  When trying to login, it closes the connection and says "The remote computer has ended the connection."  This is the same message I used to get when I logged off from the remote computer.  Everything used to work but I believe a windows update might be the cause of this problem.  I don't know exactly what update this was or what else to do.  I have tried to check (and then recheck) the option to allow remote connections on the server machine but with no luck.  Does anyone have further suggestions?  Thanks!
1 Solution
Do you see the following errors in System EventLog:

Event Type:      Error
Event Source:      TermDD
Event Category:      None
Event ID:      50
Date:            26.04.2005
Time:            15:35:14
User:            N/A
Computer:      Server01
The RDP protocol component "DATA ENCRYPTION" detected an error in the protocol stream and has disconnected the client.

Here's the cure:

1. Start Registry Editor.
2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters
3. Under this registry subkey, delete the following values:
    • Certificate
    • X509 Certificate
    • X509 Certificate ID
4. Quit Registry Editor, and then restart the server.

Somehow the Terminal Services gets its certificate keys mixed and wont accept any connection. Deleting certificate registry values and rebooting the server will help.

See http://support.microsoft.com/default.aspx?scid=kb;en-us;323497& for full details.

sbryant007Author Commented:
Thanks ajsaasta,
I am not getting this error in the system eventlog but I will try to see if it will resolve the problem.  Will let you know.
how are you connecting via IP or Names??
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

sbryant007Author Commented:
They both are doing the same thing.
Does your problem occur from any client machine ?

Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
What are you using to initiate your remote connections?  (ie, Remote Desktop Connection, Terminal Services Manager, or Remote Desktop MMC)?

sbryant007Author Commented:
Yes, it happens from all machines that attempt to login to the server.  I am trying with Remote Desktop Connection.  I still have not gotten this issue figured out.
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Remote Desktop Connection INTO a server is Terminal Services.  Server 2003 only has two "slots" for remote connections and ONLY for administrative purposes unless you have initiated the Terminal Server for Applications role.  This requires separate User or Device CALs and your server needs to be configured appropriately.

To test your connections though, enter this in START > RUN:  mstsc v/:servername /console  (where "servername" is the host name of the server you are trying to connect to)

You can also look at your server's Terminal Services Management console and see if there are any sessions which are "stuck" and blocking further connections.  

Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Also, if it's not responding at all, please see this:  http://support.microsoft.com/?scid=kb;en-us;821467&spid=3208&sid=global
I am posting these details so the search engines will hopefully pick up this fix.

Problem: Remote Desktop Connection disconnects immediately on the computer you are sitting at - displays the message "the Remote computer has ended the Connection".

This was a niggly one. I spent 2 hours on the phone with Microsoft paid support yesterday and was able to resolve this problem. Build is WinXP Pro SP2 - this fix can also apply to Win2003 Server. I had ruled out every possible cause - Virus software, Firewalls, Ports, Routers. I run a Server-Desktop-Network support company in Vancouver, Canada, and was feeling pretty cocky until I hit this bump in the road. Guess I was ripe for a dose of humility.

Close all programs as the PC will reboot automatically immediately after this fix is run.

First, download the devcon utility from support.microsoft.com:


Unzip the package and make sure to put a copy of the executable devcon.exe in to \windows\system32.

Next, open a command prompt (I ran it from c:\) and run the following command:

devcon.exe -r install %windir%\inf\machine.inf root\rdpdr

Hit Enter.

The machine will reboot. You should be able to connect via RDP (Remote Desktop Connection).

I am almost certain that RDP was broken by an update. I have since changed my Automatic Update download config (System Properties->Automatice Updates tab) to only notify me rather than automatically install updates every day at 3AM.

The chap I dealt with was in a call centre in India - he was great, very patient and methodical - my initial call was escalated to him after the first tech was unable to resolve this. My $45.00 CDN was well spent! I did a fresh build a few months ago in August and was DREADING a rebuild.
The devcon fix was the key, thanks for the solution.

Featured Post

Granular recovery for Microsoft Exchange

With Veeam Explorer for Microsoft Exchange you can choose the Exchange Servers and restore points you’re interested in, and Veeam Explorer will present the contents of those mailbox stores for browsing, searching and exporting.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now