The path we take for this problem:
1. Remove all protocols from the network config except TCP/IP, Dial-up
Adapter, and Client for Microsoft Networks (assuming the client does not
need them for other reasons).
2. Take a look at the DNS entry dialog under TCP/IP - 99% of the time this
is disabled, although it was set previously. Plug in the DNS IP's and set
the host (to whatever) and domain (to the domain name of the ISP).
3. Make sure WINS is disabled.
4. Install Microsoft DUN version 1.2, which was recently released. This
seems to help in most cases.
We have been told (maybe it was just a rumor...) that the older versions of
DUN from Microsoft (including ones shipped with Win95) had a bug/feature
that caused this to happen after a number of connects through DUN within one
session (i.e. the computer is left on for days and the user uses DUN a large
number of times without restarting the computer). Dunno if that's true or
not (hehehehh: DUNno...), but it seems to fit in many cases we have seen.
Hope that helps.
Greg Hughes
CyberPort Station
greg@cyberport.com
-----Original Message-----
From: Craig Brown <craig@blueriver.net>
To: portmaster-users@livingston.com <portmaster-users@livingston.com>
Date: Friday, August 29, 1997 1:09 PM
Subject: DUN could not negotiate compatible protocols
>I just noticed something intersting re: Windoze 95 DUN. I have had several
>customers experiencing the "could not negotiate compatible protocols"
>error. We have a PM3 with the 33.6 cards running ComOS 3.7 and just added
>an additional 16MB of memory. To accomodate our 3.1 and other customers,
>we have a menu option setup to start PPP.
>
>With 95, if the customer dials in with the "terminal window after dialing"
>option turned on, logs in with their ID, password and sends the PPP option
>from the menu, then tells windows to continue, we have nearly a 100%
>success rate (I saw 1 failed attempt out of the 50 or so that I personally
>tried and I think it was a modem compression hiccup) with connections. The
>same customers, using the regular 95 authentication, seem to have less than
>50% success rate, getting the "couldn't negotiate protocols" error a very
>high percentage of the time.
>
>Has this been mentioned here before? If not, does anyone have any ideas
>why this would be happening?
>
>Just thought I'd mention it. Thanks in advance for any insights given.
>
>Craig Brown
>Blueriver Networking Services Inc.
>
>