how to make RDP startup persistent 2

[mf99]

In some thin client connection managers it's possible to make a connection peristent - if it disconnects the interface brings up the session logon automatically over and over until reconnected or shut down. I would like to have the same occur with Windows embedded on a thin client or with XP/Vista/W7 on a PC. I've searched the web with no luck. Does anyone know a registry setting that would make a run key persistent, or some other means? Thanks for any/all suggestions.

 

[vacunita]

Why not use the Reconnect if "Connection is dropped" checkbox within the RDP configuration dialog. Its under the Experience Tab.


----------------------------------
Phil AKA Vacunita
----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.

Behind the Web, Tips and Tricks for Web Development.

http://behindtheweb.blogspot.com/

 

[mf99]

Thanks for the suggestion, sounds sensible and I've seen this work on some thin client sessions. However, I tested by creating a new session with this config (which is default anyway) and then disconnecting the session, but despite the setting there was no automatic attempt to reconnect. I have some HP/Linux thin clients that have a setting in the connection manager for peristence. With this enabled if your session gets disconnected in any way the RDP logon pops up again (and again and again). But how to do this in Windows with no connection manager?

 

[Sympology]

I can't help a great deal, but may shed some light (I use RDP a lot).

The reconnect seems to only work if the connection drops, i.e. the network falls over. If the session is forcibly disconnected, either by an admin or by a server reboot, it sits there and does nothing.
Sorry I couldn't help with fix though, Only thing I can think of is a 3rd party RDP client.

Robert Wilensky:
We've all heard that a million monkeys banging on a million typewriters will eventually reproduce the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true.

http://alvechurchlounge.org.uk

 

[BadBigBen]

check the following settings, they may be the answer...

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"DeadGWDetectDefault"=dword:00000001
"EnablePMTUDiscovery"=dword:00000001
"EnablePMTUBHDetect"=dword:00000001
"TcpMaxDataRetransmissions"=dword:0000000a

also, if you have access to a W2k3 server or CD, the RDP client is a newer version, and it does attempt to reconnect after a session drop...

more than this I am afraid I wont be able to help, I hardly use RDP, I still prefer VNC or for support over the internet, either CrossLoop or TeamViewer...



Ben
"If it works don't fix it! If it doesn't use a sledgehammer..."
How to ask a question, when posting them to a professional forum.
Only ask questions with yes/no answers if you want "yes" or "no"

 

[mf99]

Sympology & BigBadBen - thanks for your posts. I'm working with RDC Client 6.0.6001 which supports RDP 6.1. Apparently the latest version is 7.0 - I'll look into whether that would make a difference.

I'll also check out the registry keys, that may do the trick. I was told there was a registry key solution but the person who said that didn't have specifics.

Thanks again for your help - Martin