drubin@prism.poly.edu (Dave Rubin) (03/21/91)
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