CSSNET%NUSDISCS.BITNET@cunyvm.cuny.edu (10/10/89)
Wollongong Integrated Networking WIN/3B: Release 2.1
AT&T 10base5 Network Interface (NI) Package: Release 1.1
We are running the above on our AT&T 3B4000/15 and have been experienci
ng
frequent "crash" on the network. To bring the network up, we have been
using sysadm netstart. However there are times where we had to start an
d
shut several times before we establish the network correctly (able to
telnet). Also, we had taken the default configuration of 8 ttyp ports b
ut
sometimes when there's only 5 ports used, users are given the message
"All network ports in use" when they try to telnet or rlogin into the
system.
Usually when we are desperate, we just reboot the whole system...works
perfectly so far!!
I am just hoping that there are users who had this problem and if there
's
some better solutions to it.
Thanks.
> Sim Ser Ngarn (Jnet%"SIMSN@NUSDISCS")
> National University of Singapore
> Department of Information Systems and Computer Sciencelyndon@cs.AthabascaU.CA (Lyndon Nerenberg) (10/12/89)
In article <21092@adm.BRL.MIL> CSSNET%NUSDISCS.BITNET@cunyvm.cuny.edu writes: > Wollongong Integrated Networking WIN/3B: Release 2.1 > AT&T 10base5 Network Interface (NI) Package: Release 1.1 Release 2.1 contains a number of bugs -- enough to make it almost unuseable. About the only solution is to upgrade to WIN/TCP 3.0. You also need to do some heavy tuning of the kernel parameters. We run with the following parameters: master.d/tcp NTCP=64 master.d/ucp NUDP=128 You also need to crank up some of the streams stuff (TIMOD & TIRDWR) but I don't have the specific values handy. > We are running the above on our AT&T 3B4000/15 Pity. -- Lyndon Nerenberg VE6BBM / Computing Services / Athabasca University {alberta,decwrl,lsuc}!atha!lyndon || lyndon@cs.AthabascaU.CA "I think every man should have a wife. You can't blame everything on the government." -- Jed Clampett