Terminal Server over VPN

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

Have 3 offices.

A (hosts database system, character based uses terminal emulation
package on pc) connected to B (hosts exchange and file servers) by
leased line. B has a leased line to the internet and netscreen 25 with
vpn tunnels. C is a remote office with 2mb adsl netscreen5 gt and
vpn.

Users at C can use the database via terminal emulation at A with no
problem

Installed a W2K Terminal server at B for users at C to use for email
and files. Accessed it via terminal server client and via rdp. It
worked fine for 2.5 hours then just black screen. But the database
system still worked. Black screen was followed by "remote server has
disconnected".

Remote home users over netscreen vpn client could use the TS fine.

Rebooted everything still the same problem from C.

Installed 2003 terminal server on different hardware. Worked from C
for 3 hours. Now C receives login screen but cannot add password or
anything. Eventually times out.

w2k and 2003 still work fine for home users.


Has anyone any ideas? The logs on the servers and firewalls point to
no partcular difficulties.

Why work for 2 hours and stop ?

Archived from groups: microsoft.public.windowsnt.terminalserver.connectivity (More info?)

Thanks for ideas.

On Sat, 31 Jul 2004 08:10:45 -0400, "Unknown" <me@nospam.com> wrote:

>It sounds like it could be a timer issue. Not sure on software based VPN
>setups, but we ran into something similar when connecting our offices via
>VPN routers. There is a timer in there for how often it resyncs the
>security. The maximum was 8 hours of I remember correctly, but there was
>some way you could set up the timers where it seemelessly updated the
>security. I don't remember it all, its been a while since I set it up, but
>you may want to check the website for whichever company made the software or
>router you are using. Someone else here may have some clearer information to
>share with you.
>
>
>"Andrew Lee" <andrew@leecal.com> wrote in message
>news:421ng0pbnjbttefmr46o2kecf29tjd13l4@4ax.com...
>> Have 3 offices.
>>
>> A (hosts database system, character based uses terminal emulation
>> package on pc) connected to B (hosts exchange and file servers) by
>> leased line. B has a leased line to the internet and netscreen 25 with
>> vpn tunnels. C is a remote office with 2mb adsl netscreen5 gt and
>> vpn.
>>
>> Users at C can use the database via terminal emulation at A with no
>> problem
>>
>> Installed a W2K Terminal server at B for users at C to use for email
>> and files. Accessed it via terminal server client and via rdp. It
>> worked fine for 2.5 hours then just black screen. But the database
>> system still worked. Black screen was followed by "remote server has
>> disconnected".
>>
>> Remote home users over netscreen vpn client could use the TS fine.
>>
>> Rebooted everything still the same problem from C.
>>
>> Installed 2003 terminal server on different hardware. Worked from C
>> for 3 hours. Now C receives login screen but cannot add password or
>> anything. Eventually times out.
>>
>> w2k and 2003 still work fine for home users.
>>
>>
>> Has anyone any ideas? The logs on the servers and firewalls point to
>> no partcular difficulties.
>>
>> Why work for 2 hours and stop ?
>