RE: The client could not establish a connection to the remote compute
From: Jetro CockpIT (JetroCockpIT_at_discussions.microsoft.com)
Date: 12/08/04
- Next message: Jetro CockpIT: "RE: Auto logon to a terminal server site"
- Previous message: Kim Alsted: "Problems with "all users" on TS"
- In reply to: Andy Nelson: "The client could not establish a connection to the remote computer"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 8 Dec 2004 04:27:02 -0800
Did you try to telnet the 3389 port right after you failed to log in?
telnet <serverIP> 3389
Jetro CockpIT
Fulfilling the promise of Server Based Computing
http://www.jp-inc.com
"Andy Nelson" wrote:
> Hello all,
>
> I'm having a bit of a wierd issue..
>
> I have a win2k advanced server box that I'm attempting to set up
> access to via Remote Desktop. This box is housed at a colo facility,
> and I have several other boxes on the same block of IP addresses that
> I can remote desktop into fine. With the box in question... I can
> successfully RDP in and login and work on the box fine, but only
> immediatly after a reboot. If I try to login more than 2 minutes
> after the box is rebooted, or after I have already logged in once,
> finished my session, logged out, and try to log back in again I get
> the following error
>
> The client could not establish a connection to the remote computer
>
> The most likely causes for this error are:
> 1)Remote Connections might not be enabled at the remote computer
> 2)The maximum number of connections was exceeded at the remote
> computer
> 3)A network error occurred while establishing the connection
>
> I know reason 1 isn't it cause I can log in successfully once right
> after server re-boot
>
> I know reason 2 isn't it cause I have the connections limit set to
> unlimited for testing purposes
>
> Which leaves only number 3. I get this error with absoutly NO delay
> between the time I click the "Connect" button on the Remote Desktop
> window... It seems like there is not even an attempt to connect, it
> just throws this error.
>
> I have checked the logs numerous times and there are no errors in
> either the system or application logs that relate to terminal services
> and both connections (client and server side) to the WAN are working
> fine.
>
> The only thing that I can think of is that possibly there is a network
> setting, or security setting that isn't loaded directly at boot time
> (giving me the window to login right after a reboot) that is then
> applied later on in the start up cycle... but again I can log in up to
> 2-3 minutes after a re-boot, and that seems like a long time for
> network/security setting to be applied. Anyway... I've searched
> forums through and through, to no avail so I'm deciding to post.
>
> Any insight at all is appriciated... a million heads are better than
> my puny little one :-) Thanks
>
- Next message: Jetro CockpIT: "RE: Auto logon to a terminal server site"
- Previous message: Kim Alsted: "Problems with "all users" on TS"
- In reply to: Andy Nelson: "The client could not establish a connection to the remote computer"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
