> We run 3 PM2Er's here. Our users are intermittently receiving "Dialup
> Networking Could Not Negotiate..." errors. It is taking them 6 or 7 tries
> to get in.
This is almost ALWAYS the client side (win 95), BUT, if the user is set up
wrong in radius, e.g. bad netmask, it can ALSO give this error.
> This only started happening a few weeks ago. I have had some success
What has changed on YOUR end over the past few weeks?
> having our users re-install TCP/IP and Dialup Networking, upgrading DUN to
> 1.2, getting rid of extraneous protocols, and making sure that the
> connectoid was only using TCP/IP, and not using Login to Network.
Did you have them download the Service Pack from Microsoft which FIXES the
error in Windows DUN? The PRIMARY bug I know of is that after 100 times of
establishing a connection during a single Win 95 session, it will no
longer establish a compatible set of Network Protocols...
> Adding our DNS servers to their global DNS configuration is often necessary
> to connect.
DNS entries have NOTHING WHATSOEVER to do with whether they can connect or
not. It must just be a coincidence. DNS, as Im sure you know, just
resolves ip addresses to names and vice versa, but in Windows, you
specify all IP addresses for tcpip settings, so I dont see HOW the DNS
change can affect anything connect-wise.
> This clears up the problem for some users, but there is a large percentage
> still having trouble.
Go check out this URL: http://web.aimnet.com/~jnavas/win95/aimnet.html
It explains MANY of the DUN probs and how to fix them.
>
> Am I missing something somewhere?
>
> -Gabriel Emerson
> Micro Solutions Consulting
> <geme@baraboo.com>
>
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~
Jake Messinger 713-772-6690 jake@ams.com
Advanced Medical Systems, Inc. jake@uh.edu
8300 Bissonnet #400
Houston, Texas 77074 http://www.ams.com/~jake
~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~'`^`'~*-,._.,-*~