To resolve your Quake problem do the following, if you have not tried this
already.
1. From the Netserver do a sh mem.
2. Get the memory on the Netserver upgraded to at least 16MB DRAM and 8MB
Flash RAM.
3. Upgrade to Netserver code 3.7.24 or later.
I had this problem and eliminated it by doing the above. I have heard of
another problem related to IP address pools on the Netserver, which can
cause this. For example in a typical class C address space using the older
1706 chassis bundles I would configure my machines as follows:
NSR1 xxx.xxx.xxx.3 IP Pool Start xxx.xxx.xxx.25 limt 46
NMC1 xxx.xxx.xxx.2
NSR2 xxx.xxx.xxx.5 IP Pool Start xxx.xxx.xxx.71 limt 46
NMC2 xxx.xxx.xxx.4
NSR3 xxx.xxx.xxx.7 IP Pool Start xxx.xxx.xxx.117 limt 46
NMC3 xxx.xxx.xxx.6
NSR4 xxx.xxx.xxx.9 IP Pool Start xxx.xxx.xxx.163 limt 46
NMC4 xxx.xxx.xxx.10
NSR5 xxx.xxx.xxx.11 IP Pool Start xxx.xxx.xxx.209 limt 46
NMC5 xxx.xxx.xxx.12
I use .1 as the router and have static addresses available from .13 to .24
per class C for servers locally, etc....
At 04:43 PM 3/30/98 -0600, you wrote:
>I am about to lose my entire Quake group who were the first to jump onto the
>bandwagon in support of 56K.
>
>I was using a Modem Pool plugged into a Portmaster and all was well. I
>stepped up to a Netserver and several unexpected things occurred. One of
>them affects the Quake players so much (100% packet loss for 1-5 seconds)
>that they can no longer play on our server.
>
>I have put in trouble tickets in to USR but they have been 3 weeks "looking
>into it". (The feeling is that this cant be a serious problem if it is
>affecting gamers, maybe I am taking it personally ... who knows).
>
>A second problem is that some modems simply cut out on the X2 modems, they
>cant make a connection. The biggest culprits are Sportsters.
>
>Has anyone run into routing problems or packet loss problems with the
>Netservers?
>
>David Payer
>OMNI Internet
>
>
> ----------------------------------------------------------
> NTISP Mailing List listserver@emerald.iea.com
>