Terminal Server client disconnects

[Paul Ciura]

Quick overview of our setup:

We have a Cisco 1700 series router and a Sonicwall PRO200 running on
full T1 line (Sprint).

Cisco is opened up to let the Sonicwall do all the firewall stuff.
had a guy do the setup, since I'm not to familiar with Cisco.

Sonicwall does our NAT/firewall,etc,etc.

Terminal Server is setup with internal IP which is then One to One NA
over to external IP.

Sonicwall's Network Connection Inactivity Timeout is set to 24
minutes.

All TS ports for that machine are opened as necessary.

(I can post the Cisco config if needed).

The problem:

I have a Win2k Terminal Server that drops my clients (and myself) whe
we log in over the internet from home. Average connection is either o
a cable modem or DSL.

Drops happen when the client is left idle for just few minute
(minimizing the window or just letting it sit there).

On the other hand, server works perfect when I connect to it ove
internal network. Timeouts don't happen until the session limit is hi
(I have that set to 3 hours btw).

I have tried all the registry tweaks for the KeepAlive string and suc
still no luck.

Server connects fine to the license server, so I know it's not th
licenses.

Internally it works fine so my thought is that it has to be a router o
sonicwall config.

My next step is to call Sprint and ask them to check the T1 line.

Before I do that I wanted to see if any of you that use TS have com
across similar issues.

Any info would be great.

Thank You

Paul Ciur

 

[Mathew]

Hi Paul,

By any chance do you have individual users configured in your Sonicwall? If
so, there's a Global Users setting that times them out after 5 minutes (the
default setting). That setting is typically found on the "Users" tab in the
Access section.

Just a thought . . .

Mathew