> Yep ... We use the following for the client setups and it has proven
> to work very well (less than 1% still have problems and they are
> traced to bad lines...
>
> 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>...
>
No flames, just curiosity...
> gm
>
>
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.
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?
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.
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.
Curiously,
Christopher Ostmo
a.k.a. costmo@rosenet.net
Rosenet, Inc.
For a good time,
http://www.rosenet.net./~costmo