I work for an ISp, and this use to be a big problem, when we switched
our radius it eliminated this problem, but there was more to it than that.
Actually, the problem was more ofthe Pm2e than the Pm3/Ascend.
>From what we have found out, is that, for
some reason windows 95 is timing out your authentification process. It is
really weird, but 99% of the time, if a user does a Hard boot on the
machine, it puts them right on line the next time they dial up. Well, This
is where my theroy comes in. I think on some modems the PM3's doesn't
completely Disconnect, or windows 95 is having problems cycleing the
modem after the carrier is dropped. I think of it more as a Windows 95
problem, but we all like to blame Microsoft.
Other than what your doing, you can un-check "Log on to Network", and also
try the hard/cold boot.
.
\ ; /
- - (|) ----- - - -
/ | \ miker@anaconda.flinet.com
|
: --> Where there is a will there is a way,
. When there is a way, there is somone
: trying to rip you off!
|____ __ _ _
On Wed, 7 May 1997, Jon Rust wrote:
> Since upgrading to PM-3's, the number of W95 users complaining of "could
> not negotiate a compatibile protocol" messages has escalated. Folks dialing
> into my old, trusty, PM-2's never have a problem. They switch to the PM-3,
> and they immediately have this problem. Is there something new on the PM-3
> that really, really wants to run IPX???? Is there a way to turn it off? Any
> other ideas?
>
> jon
>
> PS -- Yes, we have each uyser that calls disable IPX/SPX and NetBEUI in the
> dial-up adapter. Usually this helps, but not everytime. We then have them
> delete everything but TCP/IP and the dial-up adapter from the network
> control panel. Again, usually this catches it, but still not everytime.
>
>
>