You can take a look at Microsoft's Web-Site and do a search on
'increasing tcp/ip timeout' or something similar - it should bring up
an article on their TechNet titled:
"Configuring Windows NT Satellite Networking at Coho Winery"
You can adjust MTU, window sizes, etc. with regedt32. The article
suggests the following registry entry to help deal with satellite link
latency:
HKEY_LOCAL_MACHINE \System \CurrentControlSet \Services \NetBT \Parameters
\BcastQueryTimeout
I recommend using PCAnywhere32 Version 9.0 with the latest updates and
Microsoft's recommended
registry entries to deal with satellite delay. I currently use PCAnywhere32
successfully on remote satellite
sites with NT.
Regards,
John W.
>> I use SSH and have no problems.
>
>unless this is a different ssh (secure-shell www.ssh.fi), than i'm
thinking,
>the original message effectively controlling remote desktops.
>
>this is more of a VNC type application.
>
>check out http://www.uk.research.att.com/vnc/
>
>it may be more resilient to latency and packet loss.
>
>> jan> We are currently using Windows NT 4.0 (SP3) servers with TCP.
>> jan> Currently our Helpdesk is using PC Anywhere from Symantec to take
over
>> jan> the NT screens.
>> jan> This software is working as long as the RTT are around 1.5 to 2.5 s
>> jan> (typ for our VSAT setup).
>> jan> Above these values the application starts having problems (very very
>> jan> slow or the application hangs up).
>>
>> jan> Does anyone has experience with other remote tools that are
performing
>> jan> good over the Satellite link ?
>
>
>--
>[ Jim Mercer Reptilian Research [email protected] +1 416
410-5633 ]
>[ The telephone, for those of you who have forgotten, was a commonly
used ]
>[ communications technology in the days before electronic
]
>[ They're still easy to find in most large cities. -- Nathaniel
Borenstein ]
>
This archive was generated by hypermail 2b29 : Mon Feb 14 2000 - 16:14:57 EST