Re: Terminal Services has ended your connection

Tech-Archive recommends: Fix windows errors by optimizing your registry

I mean the firewall that the users go through. Typically firewalls are setup to automatically disconnect sessions (not ts sessions but protocol sessions). for exmaple, http/https sessions are typically cutoff every 10 to 20 minutes depending on the firewall. This isn't noticed by users because users are typically never doing something for that long in either of those types of connections. Obviously TS is different. so talk to your firewall admin and make sure that there are no disconnects for port 3389.

Jeff Pitsch
Microsoft MVP - Terminal Server
Citrix Technology Professional
Provision Networks VIP

Forums not enough?
Get support from the experts at your business
http://jeffpitschconsulting.com



wardauto wrote:
Do you mean the firewall on the router?


"Jeff Pitsch" wrote:

Sounds exactly like a firewall timeout to me.

Jeff Pitsch
Microsoft MVP - Terminal Server
Citrix Technology Professional
Provision Networks VIP

Forums not enough?
Get support from the experts at your business
http://jeffpitschconsulting.com

wardauto wrote:
I have users that are able to connect to the network via the internet through terminal services and are able to stay connected for a short time (15 min) and then they are booted. They are able to log back on and pick up where they left off, but it is very frustrating to have to keep reconnecting. Any help would be appreciated.
.

Relevant Pages

  • Re: red hat firewall question
    ... This is part of the problem with 'sekuritee people' that don't actually understand the protocols. ... It is completely normal for a TCP session to be idle, and it is also completely normal for it to wake up hours later and send data, this is simply how stuff works in the IP world, and what it appears is happening is that your ssh sessions are idle for a few minutes and due to some sekuritee 'professional' deciding that this could NEVER happen, your user sessions are being disconnected. ... Changing these values on a firewall can have some VERY undesirable and difficult to fault-find consequences. ... The primary purpose of keep alives is to enable the host to not exhaust its resources by having 65500 dead yet open telnet/ssh/tcp sessions and being able to close these after a defined period., the firewall not working in sync with the host just compounds this problem, and depending on the number of users/types of processes, can actually cause the problem that keep alives are supposed to prevent. ...
    (RedHat)
  • RE: red hat firewall question
    ... Subject: red hat firewall question ... This is part of the problem with 'sekuritee people' that don't ... happening is that your ssh sessions are idle ... The primary purpose of keep alives is to enable the host to not ...
    (RedHat)
  • Re: IP Lease
    ... Not much to go on here, but this looks more like a keepalive setting somewhere, or some sort of a terminal or session timeout with a firewall or with your OpenVMS cluster. ... Sessions do not typically have IP addresses. ... You will also want to look at trying something other than Windows itsef, as Windows has been known to blow off idle connections all by itself. ...
    (comp.os.vms)
  • Re: Linksys router and AS/400-iSeries Client Access
    ... > 5250 sessions, and I have the same situation, even if I configure Mochasoft ... > connect to my network using VPN first, ... who responded asked why I was using a firewall if I'm ... I'm now connecting to a different business client ...
    (comp.security.firewalls)