Re: DUN could not negotiate compatible protocols

Sherwood Portmaster-List (livingston@iav.com)
Sat, 30 Aug 1997 21:55:27 -1000 (HST)

> Just a question...
>
> You have specified above "Server assigned DNS" for the DUN connectoid
> properties AND you have "disable DNS" in the network (TCP/IP) control
> panel.

DUN takes it from the termserver so no need for it in the network panel,
having DNS enabled in the network panel seems to override DUN so makes it
'break.'

> Where does the customer supply the DNS settings? All of our settings
> and my experience have required that they be supplied in one place or
> the other (preferably in the DUN connectoid properties). Am I
> missing something or have you uncovered some server-side setting that
> I am not aware of?

Livingston products using PAP allow the termserver to pass the gateway and
DNS information along.

> By the way, we have found that 90%+ of the "could not negotiate a
> compatible set of network protocols..." messages are fixed by messing
> with the modem settings.

?? what did you change? Most times it's a timeout because DUN is looking
for NetBEUI or IPX/SPX, removing these eliminates this difficulty.

> And finally... those who are using Windows 95B, Service Pack upgrades
> and the updated winsock stack should watch there System Resources
> very carefully. The later version winsock (which comes with the
> above mentioned items) has a nasty habit of leaking 1-5% of the
> system resources for every web page hit. A lot of our heavy surfers
> with new computers are having many crashes.

Hmm, OSR2? That should have the kernel32 fix built in...

--
Aloha from Paradise,

Sherwood