Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

terminal server has ended the connection 3

Status
Not open for further replies.

yizhar

MIS
Sep 1, 2001
2,282
IL
HI.

I'm having problems with a Terminal Server.
In the main site, there is the Win2K server with TS, which is a Member Server in NT4 domain.
A remote office is located in another country and connected via a VPN between 2 pix firewalls.
The VPN works fine and I can ping in both directions.
The clients in the remote office are using Win2K pro,
and the stand alone "Terminal Services Client" (not tsac).

The users have no problem connecting to the TS, but after several hours, they get the message
"The terminal server has ended the connection"
and then they need to create a new connection.

The strange thing here, is that the server is still showing the original connection as active, and "netstat" at the server also shows the TCP session as still established.
There are no relevant messages in event viewer of the server, I have not yet checked the client event viewer.

I have searched MS KB support site but did not find a relevant document.

This is not a licensing issue because there is no problem with creating the connection and logging in, and we have enough licenses, and the clients are W2K pro.

There is no idle time out configurred at the server (not at the user properties nor at the RDP protocol.

Again, when the users are disconnected, the server is NOT aware of it and is still considering the session as active.

The server does not have SP2 installed - it caused some compatiblity problems with a program we run on it.
I will later try installing SP2 again but I don't know if it is related to the disconnection problem.

Any tips are welcome.
Thanks,






Yizhar Hurwitz
 
RDP Client Can Lose Connection to Terminal Server If Terminal Server Initiates a RAS Session to a Remote Server (Q242051)



RESOLUTION
To resolve this issue, use either of the following methods:

Click to clear the Use default gateway on remote network check box in each dial-up and PPTP phone book entry. The Use default gateway on remote network check box is located on the Server \ TCP/IP Settings tab in the Phonebook entry for the dial-up or PPTP connection.


Configure the RAS server to assign an IP address from a different subnet.

search my dear its always there somewhere u see LOL

Kapil Aggarwal

Technical Director
Infovalley Interweb Pvt. Ltd.
Microsoft Certified System Engineer
visit
If u find the information provided here useful to u then let me know by clicking on the link below s-)
 
SYMPTOMS
After a Terminal Server client loses the connection to a Terminal Server, the session on the Terminal Server may not transition to a disconnected state, instead, it may remain active even though the client is physically disconnected from the Terminal Server. If the client logs back in to the same Terminal Server, a totally new session may be established, and the original session may still remain active.



CAUSE
This issue can occur because Terminal Server implements a Keep Alive mechanism.



RESOLUTION

For Windows 2000 Terminal Server

1)Use Registry Editor to add a DWORD value, KeepAliveEnable , with a positive numeric value of 1 (which represents 1 minute) to the following registry key:


2)HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server
Open Terminal Services Configuration in Administrative Tools , double-click RDP-Tcp in the Connections folder and click the Sessions tab.


3)Click to select Override user settings and make sure that Disconnect from session is selected and then click OK .

Kapil Aggarwal

Technical Director
Infovalley Interweb Pvt. Ltd.
Microsoft Certified System Engineer
visit
If u find the information provided here useful to u then let me know by clicking on the link below s-)
 

cut and paste the whole thing in ur browser
well i would strongly suggest to backup ur registry as sometimes microsoft's advice can also turn up the things upside-down. i have faced this my self so..... Kapil Aggarwal

Technical Director
Infovalley Interweb Pvt. Ltd.
Microsoft Certified System Engineer
visit
If u find the information provided here useful to u then let me know by clicking on the link below s-)
 
Thanks.

I have configured with a 5 minute value and will see how it goes.
I've also rebooted the server just to be sure..

Do you know what is the default for keep alive?
Was it disabled before I added the value, or was is it enabled using a default value?

Bye
Yizhar Hurwitz
 
well

A "keep-alive" mechanism is used to differentiate tunnel outages from extended periods of no control or data activity. This is accomplished by injecting "Hello" control messages into the control stream every 60 seconds.
maybe a default of 2 min i think
Kapil Aggarwal

Technical Director
Infovalley Interweb Pvt. Ltd.
Microsoft Certified System Engineer
visit
If u find the information provided here useful to u then let me know by clicking on the link below s-)
 
I have done all of the above and am still getting disconnected. My server is sitting in a DMZ along with a XP Pro machine. I can connect and stay connected to the XP machine but every 15 minutes or so the 2000 server connection gets disconnected.
Do you know of anything else that I might try?

Jeff Bulick
 
HI.

There are some session timeout settings on the W2K server that might cause this.

The per user server are part of the user account - simply double click it in AD Users and Computers or Computer Management (for stand-alone server without AD).

There are also per-server settings -
Look for the RDP configuration in "Administrative Tools".

Check also the W2K event viewer.

Bye
Yizhar Hurwitz
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top