Reg Edit

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a problem with an XP desktop I have set it up via a registry edit to
load a remote desktop session to our terminal server, the computer
automatically logs on locally without the user knowing it and kicks off a
remote desktop session rather than loading explorer. The problem I am facing
and it has never been a problem before is that it seems to load the remote
desktop session before the computer has had a chance to connect to the
network and so I get an error warning "The specified remote computer cannot
be found, verify that you have typed the correct computer name or ip address
and then try connecting again. I then alt + ctrl + delete and log off and the
session will start as nothing was wrong this only happens when the computer
is first turned on. Is there any fix to this issue? Such as an edit to make
the remote desktop connection load a few seconds later as a guess?. Any help
would be greatly appreciated.
 
This is a know pain in the backside ! The problem is based by the fact that
it is impossible to predict how long it will take to establisch a connection.
Windows does try to initiate the network first but since it uses multi-tread
processes it is possible that another process start before the connection is
set up. One solution that springs to mind is to move the connection process
to the Start section of the desktop. This should execute after the processes
defined in the other sections of the registry. This is a guess though, I
don't know wether it will work ...

best regards
 
That's a good thought. Another might be to launch a batch process which
includes a SLEEP command to give the OS enough extra time to get the network
up properly before MSTSC trys to connect.
 
Back
Top