Remote Desktop Disconnected.

[Mitesh Patel]

Hi,
I have serveral problem with my terminal server. I have Windows 2000 domain
and Novell server and one Windows 2k terminal server. I use remote desktop
client to connect terminal server.
1st problem.
If I don't use terminal session (minimize) and just use my regular desktop
then I'm getting "Remote desktop Disconnected"
The connection to the remote computer was broken. This may have beeb caused
by network error. Please try connecting to the remote computer again.

And when I try to connect back I'm getting this error:
The remote connection has timed out. Please try connecting to the remote
computer again.

Only way I can connect back in I have to reboot the Terminal server.
Need help

Thanks

[Vera Noest [MVP]]

Could well be that there is a router between your client and your
server, which sees no traffic and decides that the session must
have ended and throws it out. The solution in that case is to
enable KeepAlives. For the correct registry key, check:

216783 - Unable to Completely Disconnect a Terminal Server
Connection
http://support.microsoft.com/?kbid=216783

Also check this link:
http://terminal.servebeer.com/php/flaky_connections.php

And check the time-out setting on idle sessions. You might have to
change that as well.

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

=?Utf-8?B?TWl0ZXNoIFBhdGVs?=

Post by Mitesh Patel
Hi,
I have serveral problem with my terminal server. I have Windows
2000 domain and Novell server and one Windows 2k terminal
server. I use remote desktop client to connect terminal server.
1st problem.
If I don't use terminal session (minimize) and just use my
regular desktop then I'm getting "Remote desktop Disconnected"
The connection to the remote computer was broken. This may have
beeb caused by network error. Please try connecting to the
remote computer again.
The remote connection has timed out. Please try connecting to
the remote computer again.
Only way I can connect back in I have to reboot the Terminal
server. Need help
Thanks

[Mitesh Patel]

Hi Vera,
Thanks for reply.
I have one more question.
I do not have any kind of registry key such as
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveInterval
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime
Is it ok to add this key ? After adding this keys do I need to reboot the
server?

Thanks

Post by Vera Noest [MVP]
Could well be that there is a router between your client and your
server, which sees no traffic and decides that the session must
have ended and throws it out. The solution in that case is to
216783 - Unable to Completely Disconnect a Terminal Server
Connection
http://support.microsoft.com/?kbid=216783
http://terminal.servebeer.com/php/flaky_connections.php
And check the time-out setting on idle sessions. You might have to
change that as well.
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
=?Utf-8?B?TWl0ZXNoIFBhdGVs?=

Post by Mitesh Patel
Hi,
I have serveral problem with my terminal server. I have Windows
2000 domain and Novell server and one Windows 2k terminal
server. I use remote desktop client to connect terminal server.
1st problem.
If I don't use terminal session (minimize) and just use my
regular desktop then I'm getting "Remote desktop Disconnected"
The connection to the remote computer was broken. This may have
beeb caused by network error. Please try connecting to the
remote computer again.
The remote connection has timed out. Please try connecting to
the remote computer again.
Only way I can connect back in I have to reboot the Terminal
server. Need help
Thanks

[Vera Noest [MVP]]

If the value does not exist, it means that the default value is
used.
So you definitively want to create the DWORD value of
KeepAliveEnable and set it to 1.

If you want to create the other values depends on if you want to
change the defaults.

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

=?Utf-8?B?TWl0ZXNoIFBhdGVs?=

Post by Mitesh Patel
Hi Vera,
Thanks for reply.
I have one more question.
I do not have any kind of registry key such as
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAlive
Interval
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAlive
Time Is it ok to add this key ? After adding this keys do I need
to reboot the server?
Thanks

Post by Vera Noest [MVP]
Could well be that there is a router between your client and
your server, which sees no traffic and decides that the session
must have ended and throws it out. The solution in that case is
216783 - Unable to Completely Disconnect a Terminal Server
Connection
http://support.microsoft.com/?kbid=216783
http://terminal.servebeer.com/php/flaky_connections.php
And check the time-out setting on idle sessions. You might have
to change that as well.
--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
=?Utf-8?B?TWl0ZXNoIFBhdGVs?=

Post by Mitesh Patel
Hi,
I have serveral problem with my terminal server. I have
Windows 2000 domain and Novell server and one Windows 2k
terminal server. I use remote desktop client to connect
terminal server. 1st problem.
If I don't use terminal session (minimize) and just use my
regular desktop then I'm getting "Remote desktop
Disconnected" The connection to the remote computer was
broken. This may have beeb caused by network error. Please
try connecting to the remote computer again.
The remote connection has timed out. Please try connecting to
the remote computer again.
Only way I can connect back in I have to reboot the Terminal
server. Need help
Thanks