home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!swrinde!swrinde.nde.swri.edu!tennis
- From: tennis@swrinde.nde.swri.edu (Richard F. Tennis)
- Newsgroups: comp.os.os2.networking
- Subject: Re: TCP/IP CSD Problem
- Date: 22 Jan 1993 23:41:30 GMT
- Organization: Southwest Research Institute, San Antonio, Texas
- Lines: 50
- Message-ID: <1jq0naINN6vq@swrinde.nde.swri.edu>
- References: <1jmip3INNi2h@swrinde.nde.swri.edu> <1jmqlgINNab9@gap.caltech.edu>
- NNTP-Posting-Host: swrinde.nde.swri.edu
- Keywords: TCPIP, CSD
-
- Newsgroups: comp.os.os2.networking
- Subject: Re: TCP/IP CSD Problem
- Summary:
- Expires:
- References: <1jmip3INNi2h@swrinde.nde.swri.edu> <1jmqlgINNab9@gap.caltech.edu>
- Sender:
- Followup-To:
- Distribution:
- Organization: Southwest Research Institute, San Antonio, Texas
- Keywords: TCPIP, CSD
-
- In article <1jmqlgINNab9@gap.caltech.edu> hacker@cco.caltech.edu (Jonathan Bruce Hacker) writes:
- >tennis@swrinde.nde.swri.edu (Richard F. Tennis) writes:
- >
- >> I just installed the latest csds for TCP/IP 1.2.1 to my 2.0 GA + SP
- >>system. Now I am having problems with NFS and PMX. PMX crashes my
- >>machine with a TRAP D message somewhere in my etherlink16 ndis driver as
- >>soon as I try to open an xterm window. NFS starts hanging with
- >>periodic RETRY errors after a variable length of use. Everything was
- >>basically working before I installed these last csds except that PMX
- >>would die after a few hours so I would really like to make the new stuff
- >>work since it is suppose to fix this problem. My configuration is:
- >> 2.0 ga + SP on a 16 MB, 66 MHz 486
- >> Etherlink 16 on thicknet
- >> 1.2.1 TCPIP base + UN29511 csd
- >> NFS + UN32132 csd
- >> PMX + UN30680 csd
- >
- >> Anyone know if there are any newer csds or have any other solutions to
- >>suggest?
- >
- >The latest CSD for TCP/IP base is UN32131 and it is on hobbes in /pub/uploads.
- >
- >--
- >Jon Hacker
- >Caltech, Pasadena CA
- >hacker@tumbler-ridge.caltech.edu
-
- I found the UN32131 Base CSD as you suggested. PMX still hangs as soon
- as I start an xterm, but now it doesn't crash the system ... an
- improvement? I had to kill PMX before other net communications would
- work. I ran netstat while PMX was hung and was reporting a growing
- number of packet timeouts, a clue perhaps?
-
- I also discovered that vt220 is broken. It gets confussed about whether
- or not it should be in intensified mode or not. Fortunately, vt100 still
- works.
-
- I haven't tried NFS yet.
-
-