> If you have a lockup on ftp transfer from a Unix box to
> a Win NT server or Win 95 client, check the STRMAXBLK
> setting in Unix. It may be set to high to function
> properly.
> Our setting was "524288" and when switched to "4096" FTP
> worked without any problems.
This is an extremely simplistic rendition of a complex problem.
STRMAXBLK should be tuned down only if your network card driver has a
problem with it. That should be true only if you are using an old ODT
3.0 LLI driver; and in fact, not even all LLI drivers have problems with
STRMAXBLK being larger than 4096. If you're using an OSR5 MDI driver,
you should not reduce STRMAXLBK as you will be impairing the maximum
network performance of your system. The presence of an old LLI driver
is the *only* reason I know of to reduce STRMAXBLK.
SCO Technical Article http://www.sco.com/cgi-bin/ssl_reference?640379
discusses a different problem with STRMAXBLK, and in passing, describes
the parameter in more detail. Note that the problem discussed in
article 640379 is corrected by the Networking Supplement 1.0.0,
ftp://ftp.sco.com/Supplements/net100/. net100 also corrects other
problems, some of which could have caused exactly the behavior you
describe. So if you did not have net100 applied (and its prerequisite
rs500d and its successor oss449a), you should apply them, put STRMAXBLK
back to its original value, and see what happens.
Quote:>Bela<