> well, its finally hit us. we run pm2e-30 portmasters using comOS 3.1.4 (i
> just about everyone could login but were disconnected from 2-30 minutes.
> questions:
> 1. is it time to upgrade comOS?
Yes. <G> I had a similar problem with disconnects, and we're well known
for not having ANY problems like that. It started driving me crazy when I
looked at the logs and noticed that people were being assigned 0.0.0.0,
and 2 real IPs that were above the normal block of 30 that are used. I
reset the Portmaster and everything worked fine again, but I upgraded to
the latest ComOS about a week later. Since then we haven't had any
problems on our end.
> 2. is there a modem init string for modems a little more robust than the
> "ISP Recommendation" ?
We use USR Couriers, so I'm not sure I can help you there.
> 3. is there a patch for these win95 users ? some sort of timing issue?
> there are a wide variety of user modems, so can't blame it there except for
> sportsters of about 1 yr old or the winrpi stuff.
We've had many many different Win95 problems and I've managed to solve
most of them with a few tricks. First of all, Win95 tends to break
itself. (I know this is hard to believe. <G>) Sometimes a simple reboot
will fix the problem. If not, the best thing I've found to do is remove
Dial-Up Networking (From the Add/Remove Programs Control Panel) and then
run the Internet Setup Wizard again. We've had a lot of success doing
this. After you have the customer up and running again, make sure they've
patched their Win95 with at LEAST the Service Pack I, and then the
Kernel32 Patch (This is the important one) ... Once these patches are
installed, we've noticed less of a problem with Win95 complaining about
not being able to connect, disconnects, and the "Cannot negotiate a set of
compatible protocols" that seems to happen a lot.
Jaime Bozza
Nucleus Communications, Inc.