If the client has the "modem" icon on the tool-bar then they have release 1
and
need to download Service Pack 1 for Win-95 (fixed a good deal of TCP stack
problems (ala-MicroSoft)...then setup as follows...
If the client has the "Two-computer" icon on the tool-bar then they have
release #2:
Set dial-up Networking connection properties as follows:
In the Server Types section:
Advanced options:
Logon to network - disabled
Enable Software Compression - enabled
Require encrypted password - disabled
Allowed Network Protocols
NetBEUI - disabled
IPX/SPX - disabled
TCP/IP - enabled
For the TCP/IP settings:
server assigned IP address,
server assigned DNS,
use default gateway
use header compression.
The network section in control panel:
The Dialup adapter properties seems to have an interesting setting:
In the Advanced Setting section:
Set the "Use IPX header compression" = NO.
(don't know why but this setting can cause some random disconnects if
the setting is YES!!! )
The TCP/IP protocol is the ONLY one and
should be setup as follows:
IP section - Obtain an IP address automatically
NetBIOS - disabled
WINS Configuration - disabled
Advanced - nothing
Gateway - nothing
DNS - disabled
Bindings - none
I'm sure there will be some others who will most likely flame this response
but at least the info is out...<grin>...
gm
----------
> From: Gabriel Emerson <geme@baraboo.com>
> To: 'Craig Brown' <craig@blueriver.net>
> Cc: 'portmaster-users@livingston.com'
> Subject: RE: DUN could not negotiate compatible protocols
> Date: Friday, August 29, 1997 3:28 PM
>
> Craig,
> We had a similar problem. The solution came in stages. Each stage
> worked for a bit, then
> didn't, requiring the next step. Unfortunately, I can't tell you which
was
> the true solution. Maybe this will help, though.
>
> 1) Remove then re-add TCP/IP and Dialup Networking. Remove any unused
> network components, including NetBEUI.
> 2) Go to the Network control panel under TCP/IP and disable WINS. Add
> DNS entries.
> 3) Under DUN connectoid, disable NetBEUI and IPX/SPX. Be sure Login to
> Network is not checked. Make sure that Use Default Gateway on Remote
Host
> is checked.
>
> These three steps cured 90% of the problems. We found a modem that
> wasn't set for Login/Network, which brought it up to 95%.
>
> 4) If none of this helps, disable DNS under the control panel, and set
> Server Assigned Domain Name Servers under the connectoid. This cleared
up
> the last of the complaints.
> ----
> 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.