terminal server encryption

  • Thread starter Thread starter james
  • Start date Start date
J

james

I have changed the encryption level of terminal services
on all of our servers, but it is stll registering as 128
bit on the rdp client about tab! We are experiencing alot
of disconnects when the signal drops for a second! I
think using the lowest encryption would help because the
encyption would not be broken. Why are the clients not
using the lowest encryption after i have set the level on
the server! Is there a way to increase the time period
the server will wait to end a session that dros for a
second! I have set everything to override the client
settings for disconnect times and encryption level! We
are using tkip preshared keys on fujitsu lifebooks with
intersil wireless nics and cisco 1100 access points! I
have updated xp with all the wpa patches available.
please HELP!!!!!!!!!
 
Encryption could not have caused disconnect, have you enable auto-reconnect?
to increase timeout, maybe this will help,
http://support.microsoft.com/default.aspx?scid=kb;EN-US;314053.

Encrption setting on server always overwrite client setting so it does not
matter if client setting is different, here are encryption settings and what
it mean.

a.. Low: All data sent from the client to the server is protected by
encryption based on the maximum key strength supported by the client. This
option was removed in RDP 5.1 and added back for RDP 5.2.

a.. Compatible: All data sent between the client and the server is
protected by encryption based on the maximum key strength supported by the
client.

a.. High: All data sent between the client and server is protected by
encryption based on the server's maximum key strength. Clients that do not
support this level of encryption cannot connect.

a.. FIPS: All data sent between the client and server is protected using
Federal Information Processing Standard 140-1 validated encryption methods.
Clients that do not support this level of encryption cannot connect. This
option is new for RDP 5.2.
Hope this help.

-HueiWang
 
How do I enable auto reconnect???????? Do have have to edit the registry to do so!!!

----- Huei Wang [MSFT] wrote: -----


Encryption could not have caused disconnect, have you enable auto-reconnect?
to increase timeout, maybe this will help,
http://support.microsoft.com/default.aspx?scid=kb;EN-US;314053.

Encrption setting on server always overwrite client setting so it does not
matter if client setting is different, here are encryption settings and what
it mean.

a.. Low: All data sent from the client to the server is protected by
encryption based on the maximum key strength supported by the client. This
option was removed in RDP 5.1 and added back for RDP 5.2.

a.. Compatible: All data sent between the client and the server is
protected by encryption based on the maximum key strength supported by the
client.

a.. High: All data sent between the client and server is protected by
encryption based on the server's maximum key strength. Clients that do not
support this level of encryption cannot connect.

a.. FIPS: All data sent between the client and server is protected using
Federal Information Processing Standard 140-1 validated encryption methods.
Clients that do not support this level of encryption cannot connect. This
option is new for RDP 5.2.
Hope this help.

-HueiWang
 
Seems highly unlikely that encryption has something to do with
your frequent disconnects. Check these troubleshooting tips,
enabling KeepAlives and changing TcpMaxDataRetransmissions often
stabilizes an unreliable connection (and yes, editing the registry
is sometimes a part of the deal :-)

http://terminal.servebeer.com/php/flaky_connections.php

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

How do I enable auto reconnect???????? Do have have to edit the
registry to do so!!!

----- Huei Wang [MSFT] wrote: -----


Encryption could not have caused disconnect, have you
enable auto-reconnect? to increase timeout, maybe this will
help,
http://support.microsoft.com/default.aspx?scid=kb;EN- US;3140
53.

Encrption setting on server always overwrite client setting
so it does not matter if client setting is different, here
are encryption settings and what it mean.

a.. Low: All data sent from the client to the server is
protected by
encryption based on the maximum key strength supported by
the client. This option was removed in RDP 5.1 and added
back for RDP 5.2.

a.. Compatible: All data sent between the client and the
server is
protected by encryption based on the maximum key strength
supported by the client.

a.. High: All data sent between the client and server is
protected by
encryption based on the server's maximum key strength.
Clients that do not support this level of encryption cannot
connect.

a.. FIPS: All data sent between the client and server is
protected using
Federal Information Processing Standard 140-1 validated
encryption methods. Clients that do not support this level
of encryption cannot connect. This option is new for RDP
5.2. Hope this help.

-HueiWang

--
This posting is provided "AS IS" with no warranties, and
confers no rights.

"(e-mail address removed)" <[email protected]>
wrote in message
I have changed the encryption level of terminal services
on all of our servers, but it is stll registering as 128
bit on the rdp client about tab! We are experiencing
alot of disconnects when the signal drops for a second!
I think using the lowest encryption would help because
the encyption would not be broken. Why are the clients
not using the lowest encryption after i have set the
level on the server! Is there a way to increase the time
period the server will wait to end a session that dros
for a second! I have set everything to override the
client settings for disconnect times and encryption
level! We are using tkip preshared keys on fujitsu
lifebooks with intersil wireless nics and cisco 1100
access points! I have updated xp with all the wpa
patches available. please HELP!!!!!!!!!
Click to expand...
Click to expand...
 
Back
Top