Geeks With Blogs

News Clicky Web Analytics

web stats View David Caddick (davidcaddick@gmail.com)'s profile on LinkedIn

Search this Site!

Locations of visitors to this page
View My Stats eXTReMe Tracker
This posting is provided "AS IS" with no warranties, and confers no rights. The opinions expressed within are my own and should not be attributed to any other Individual, Company or the one I work for. I just happen to be a classic techie who is passionate about getting things to work as they should do (and are sometimes advertised and marketed as being able to?) and when I can I drop notes here to help others falling in to the same traps that I have fallen in to. If this has helped then please pass it on - if you feel that I have commented in error or disagree then please feel free to discuss with me either publically or privately? Cheers, Dave
Thin Clients, VDI and Linux integration from the front lines.... Raw and sometimes unedited notes based on my experiences with VMware, Thin Clients, Linux etc.

I was helping build a Road Case for demos at MS 2008 Launches and other uses and while building a couple of VDI's as well as BladePC's for the Thin Client's to connect to we found that roughly half of the devices were not responding at all to a simple RDP connection.

One point here is that although this was just a small Road Case for demo's we had decided to try and emulate a proper enterprise environment as possible in that the systems had been setup as Multi-Homed with dual NIC's so that there is a Private VLAN for Altiris imaging jobs as well as a Public VLAN for the connections and normal work, this enables BladePC's, VDI's and Thin Clients to be re-imaged without causing disruption to normal LAN activity.

So with that caveat in mind, what went wrong and how did we fix it?

Earlier we had discovered that RGS (HP's Remote Graphics Software) was not connecting either and this was traced to the fact that ALL of the systems we had set up to run RGS had managed to bind to the wrong NIC.

Action: Disable NIC2, restart RGS Sender service - test, OK

Open Networks, click on Advanced, make sure the correct NIC is at the top of the order

re-enable NIC2, still test's OK

reboot, tested again, still OK.

As a consequence we have checked back up with the Product Development Team and the feedback is that there is now an enhancement request in so that during installation of the Sender component it will check for NIC's and with more than 2 it'll ask you which NIC to bind to. There will also be a configuration to ensure the right NIC is bound.

So that was the RGS sorted, so what was happening to the RDP connections?

We could ping them, we could connect via Telnet on 3389, the Remote Connection box was checked, and the user was part of the Remote Desktop Users group.....  very strange.

Checked the Event Log and found some curious reference to TermDD and an error 50?

At one stage I thought it might be MS kb555382

But it finally transpired that it was this "The RDP Protocol Component "DATA ENCRYPTION" Detected an Error..." error message

Unbelievably the cause is: 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 simply means the invalid certificate is deleted and it is recreated on the fly on the next reboot

Resolution:

To resolve this issue, follow these steps:

  1. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\TermService\Parameters
  2. Under this registry subkey, delete the following values:
    Certificate
    X509 Certificate
    X509 Certificate ID
  3. Quit Registry Editor, and then restart the server.  (Although this states Server - it can happen on XP SP2)

 

Interestingly enough there is also a mention of this very same KB article at VMware with reference to VMware Virtual Desktop Manager (VDM) 2.0 Release Notes

Posted on Saturday, March 1, 2008 4:14 PM | Back to top


Comments on this post: RDP Connection to VDI fails, almost immediately, what is the cause?

# re: RDP Connection to VDI fails, almost immediately, what is the cause?
Requesting Gravatar...
Note this also happens with Windows XP SP3. Same resolution.
Left by Rocky on Aug 09, 2008 1:28 AM

Your comment:
 (will show your gravatar)


Copyright © Dave Caddick | Powered by: GeeksWithBlogs.net