When we occasionally have a machine do this, it is only windows95
having the problem. If the case is that it was working sometime
recently and nothing has been changed, I ask them if they have rebooted
their machine since it began occuring.
> > > Usually the solution is to reinstall the Dial Up Scripting
> > Tool Software or Confirm that the tool is pointing to the
> > script correctly. Installing Dunce does seem to help some
> > of these problems at times.
>
> Why use scripts for portmasters? The ease of win95 dun not needing a
> script is what prompted us to buy livingston in the first place.
You don't need scripts with Windows95 dialup networking.
> I have an ISP and lately we've been getting an unusually large number of
> reports of the Win95 error message:
>
> Dial-up networking was unable to negotiate a compatible set of network
> protocols specified in the server type settings. Check your network
> configuration in the control panel and try again.
>
> It only seems to happen to certain people, some intermittently and some
> persistently. All their settings seem correct, and we've ruled out the
> usual things. We've only been seeing this problem recently, sometimes with
> people who've had flawless connections for months. We're running Radius
> 1.16 on Linux Redhat 4.0 with a standard PPP connection.
>
> Does anyone have any ideas what we might look for on our end?
I believe this is another bug in the OS that is the market leader
(why!? why!?) of our time. In my experience, ask if they have rebooted,
if all settings are correct, possibly compuserve or AOL installed
drivers and/or browsers can cause unpredictable results.
This topic appears to be off-topic, sorry.
-- /* Chuck Rouzer - rouzer@spyder.net - http://www.spyder.net */