Re: Unable to reconnect using remote desktop connection
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 06 Oct 2005 11:58:53 -0700
Anything in the EventLog on the Terminal Server?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
"=?Utf-8?B?RENCU0k=?=" <DCBSI@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on
05 okt 2005 in microsoft.public.win2000.termserv.clients:
> Using Remote Desktop Connection 5.2.3790.0 to connect to Windows
> Server 2000 in Administrator mode, the first connection after a
> reboot works just fine. After that connection is finished
> (time-out, disconnect, end session, doesn't matter how), no new
> connections are allowed until the server is rebooted.
> Attempting to use reset within Terminal Services Manager from
> the physical console does not help. Why is this happening now?
> This didn't used to happen until the most recent crop of
> Microsoft updates were applied. The message the client gets
> when attempting to reconnect is: "The client could not
> establish a connection to the remote computer. The most likely
> causes for this error are:...". This happens whether the client
> is internal (on the LAN) or external (coming in through the
> WAN/Internet). The primary terminal services client settings
> are "Terminate after 1 minute of losing connection" and "End
> session upon termination". The remainder of the settings are
> set to "Never". The server is set to ignore the client settings
> and use these 'defaults'.
.
- Prev by Date: RE: Ctrl-Alt-End not working
- Next by Date: RE: Ctrl-Alt-End not working
- Previous by thread: Re: Remote desktop printer redirect
- Next by thread: client profiles
- Index(es):
Relevant Pages
|