Robert, When you say "it has no effect" do you mean that the window stays at
the default 8 kB? Has this been reported anywhere? I have read that the
machine needs to be re-booted before it takes effect. Here is a tcpsat post
from someone named Christophe Orlhac and he doesn't mention a problem:
http://tcpsat.grc.nasa.gov/list/archive/0588.html
I am interested if you have any more information. Thanks.
Bill Shvodian
> -----Original Message-----
> From: Robert Schellhase [SMTP:[email protected]]
> Sent: Thursday, February 10, 2000 2:18 PM
> To: [email protected]
> Cc: [email protected]
> Subject: RE: nt to nt tcpsat problems
>
> Hi Graham,
> I see you have found that Windows supports a registry key for
> TcpWindowSize.
> The sad news is that it has no effect, in spite of the fact that Microsoft
> has a white paper on its own TCP implementation that claims otherwise.
>
> You might try the NetManage OnNet kernel for Windows 95/98 at
> http://www.netmanage.com/products/onnetkernel4/index.asp
>
> I don't know what they charge for it, but I think it's affordable and they
> offer a free demo.
>
> Best regards,
> Robert Schellhase
> Senior Engineer
> INTELSAT
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]]On
> Behalf Of Graham Street
> Sent: Thursday, February 10, 2000 9:04 AM
> To: [email protected]
> Subject: nt to nt tcpsat problems
>
>
> Hi all,
>
> We're trying to run windows file sharing protocols over a tcp sat link
> and getting miserable performance, even after setting TcpWindowSize to
> 65536. We can get about 100-250k max. We are trying to get at least
> one megabit out of it. Is this even possible? We can get 1-2 megabits
> ftping from a sun box over satellite...
>
> does anyone know of any clever (cheap) solutions (spoofing nacks?,
> translating
> to udp?)
>
> Thanks,
> Graham Street
> [email protected]
This archive was generated by hypermail 2b29 : Mon Feb 14 2000 - 16:14:59 EST