New posts to the forums are closed for now.
Read more about this decision.
Terminal services client high encryption with WM5
|
11/11/05 8:27am
berwickl |
I am trying to connect to my corporate terminal server (Windoes 2000 application mode) and get an immediate rejected connection when using my Dell Axim x51v (Windows Mobile 5). I am able to connect successfully to lots of other terminal servers (win2k, win2k3 and XP pro). I was able to get some feedback from our IT department that showed my session was being rejected due to incompatible encryption levels. (the error is right in the terminal server's event viewer). I have recreated this issue on other terminal servers by changing encryption from "client compatibility" to "high". Since my corporate IT department is unwilling to lower the encryption standard to "client compatibility", I must figure out a way to get WM5's TS client to work. Has anyone else experienced this issue? I noticed a Pocket IE High Encyption pack out on the Microsoft site, but it explicitly states it is not for Mobile 2003 SE because high encryption is built in. I assume WM5 has the same built in...? Any thoughts are most welcome!
|
Printer-friendly version
Sooner Al
Older versions of the PPC OS, ie. WM 2003 SE/WM 2003/PPC 2002/etc, contained a version of TSC that only did 64-bit encryption... If your having problems with a WM 5 device then I would say the same lack of support for 128-bit encryption still exists in the TSC...
Bummer...
An alternative is to either configure your Terminal Server to accept connections at the lower encryption level (not an option in your case) or run TSC through a VPN tunnel...
------------
"When all else fails, read the instructions..."
Al Jarvi
MS-MVP Windows Networking (http://mvp.support.microsoft.com)
This posting is provided "AS IS" with no warranties, and confers no rights...
------------
"When all else fails, read the instructions..."
Al Jarvi
MS-MVP Windows Networking (http://mvp.support.microsoft.com)
This posting is provided "AS IS" with no warranties, and confers no rights...
Sooner Al
I just reconfirmed your observation with a Mobile Devices MVP that in fact the TSC built-in to WM 5 only supports 64-bit encryption. He ran a test on his Windows 2000 Server running Terminal Server (TS) and had to configure TS for medium security in order to get his WM 5 device to connect using TSC. High encryption caused the connection to fail.
Tunneling TSC through a VPN or Secure Shell (SSH) would be a work around to this issue...
------------
"When all else fails, read the instructions..."
Al Jarvi
MS-MVP Windows Networking (http://mvp.support.microsoft.com)
This posting is provided "AS IS" with no warranties, and confers no rights...
------------
"When all else fails, read the instructions..."
Al Jarvi
MS-MVP Windows Networking (http://mvp.support.microsoft.com)
This posting is provided "AS IS" with no warranties, and confers no rights...
berwickl
Thanks very much for the quick and detailed explanation and test. I am really disappointed to learn about this incompatibility between server and client. It seems very odd that MS would let you turn up encryption on the terminal server, offer a Windows XP client (RDP) that supports 128-bit encryption, but leave 128-bit support out of the brand new TS client for WM5?!
"Bummer" is right!
My company uses Nortel contivity for VPN and requires employess to install a client on laptops, etc. to connect. I understand that Movian and Apani make a client for Pocket PC 2003, but don't have one for WM5 yet. Anyway, I'd have to shell out $$$ for it and I'm not too exited about spending any more money to get WM5 to do what I need.
Guess I'll go back to carrying a laptop everywhere I go...
[:(]