From: syscrc@gsusgi1.gsu.edu (Randy Carpenter)
Newsgroups: comp.sys.sgi
Subject: Re: IRIX 4.0.1 telnet(1) problem.
Date: 6 Apr 92 18:06:23 GMT
Organization: Georgia State University

martin@knobi.munich.sgi.com (Martin Knoblauch) writes:

>In article <syscrc.702224748@gsusgi1.gsu.edu>, syscrc@gsusgi1.gsu.edu (Randy Carpenter) writes:
>|> 
>|> We recently upgraded to IRIX 4.0.1 and soon found that our PC-based
>|> telnet (Novell's LAN Workplace for DOS and the unsupported WIN/TCP)
>|> programs no longer worked with the SGI.  New programs for LAN Workplace
>|> for DOS were needed to fix the problem:
>|> 
>|>   1. tcpip.exe  (the TCP/IP protocol stack)
>|>   2. telapi.exe (the TELNET Appication Programming Interface)
>|> 
>|> Old:
>|>   tcpip.exe   37677  2-28-91  Version 4.0
>|>   telapi.exe  19721  2-28-91  Version 1.0
>|> 
>|> New:
>|>   tcpip.exe   37961  8-19-91  Version 4.0 Patch Release 1
>|>   telapi.exe  20867  1-02-92  Version 1.2
>|> 
>|> Unfortunately, WIN/TCP is no longer supported and we can't fix
>|> that program.
>|> 
>|> The only reason we can come up with as to why this happened is that
>|> the IRIX 4.0 telnet(1) is the September 1990 release from Dave Borman
>|> and the PC-based program are older (!?).
>|> 
>|> Has anyone else encountered this problem or can you offer another 
>|> explanation?
>|> 
>|> -- 
>|> ===========================================================================
>|> Randy Carpenter                rcarpent@gsu.edu         % Got a light?
>|> Georgia State University       (404) 651-2648           No match.
>|> Wells Computer Center                                   %
>
>  I believe the reason for the problems you encounter is that with
>IRIX 4.0.1 the TCP windowsize on SGI machines was (ABSOLTELY legal and
>standard conforming) increased to 60K instead of 30K for improved
>performance. A lot of older PC (and other 16bit) software cannot handle
>unsigned integers larger than 32K. So there is a mismatch.
>
>  A possible solutio is to go to /usr/sysgen/master.d/bsd and look for
>the lines:
>
>unsigned long tcp_sendspace = 60 * 1024;        /* must be < 64K */
>unsigned long tcp_recvspace = 60 * 1024;        /* must be < 64K */
>
>change them to 
>
>unsigned long tcp_sendspace = 30 * 1024;        /* must be < 64K */
>unsigned long tcp_recvspace = 30 * 1024;        /* must be < 64K */
>
>and rebuild the kernel and reboot. After that you have a fair chance that
>your old software will run again. I think this has been reported here
>before. Again, it is no fault of IRIX, it is just the inadequateness of
>some older software in a modern environment.
>
>Martin
>
>Standard comments on opinions and employers etc.

Ok...that works (thanks!).  Now that I've done this, does anyone know if
the IRIX telnetd will negotiate up from 30K to 60K for clients that are
able?  In other words, by changing the 60 to 30, have we locked ourselves
out of the possible performance benefits?

-- 
===========================================================================
Randy Carpenter                rcarpent@gsu.edu         % Got a light?
Georgia State University       (404) 651-2648           No match.
Wells Computer Center                                   %