Xref: utzoo comp.sys.att:12026 comp.protocols.tcp-ip:15337
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ncar!hsdndev!cmcl2!prism!drubin
From: drubin@prism.poly.edu (Dave Rubin)
Newsgroups: comp.sys.att,comp.protocols.tcp-ip
Subject: WIN-TCP 3.2 for AT&T 3B2s
Message-ID: <1991Mar20.180326.28408@prism.poly.edu>
Date: 20 Mar 91 18:03:26 GMT
Reply-To: drubin@prism.poly.edu (Dave Rubin)
Organization: Polytechnic University, New York
Lines: 17


After recommendations from various helpful netnews readers, I called AT&T and
upgraded my Wollongong 3.0.1 TCP/IP software for our 3B2/522 to version 3.2.  
Happily, this fixed the dreaded Kernel MMU fault and sendmail problems, 
but created another major problem:

The TCP timeout seems to be set very low.  When opening connections to remote
nodes, after less than 1 second, the response is "Connection timed out."
Does anyone know how to change this timeout value, and is AT&T aware of this
rather significant problem?

Please respond via E-mail. Thanks..

--
Dave Rubin
Polytechnic University, Brooklyn, NY
drubin@prism.poly.edu