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
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