Why is win 95/98 so slow to log in?
A. Some Win95 users seem to have very slow logon times,as long as two or three minutes.
The symptom is that Windows 95 will dial the number,successfully verify username
and password,and then seem to hang for a very long time at the'Logging on to
Network'phase before completing the connection.The cause is Win95 is attempting
to negotiate a connection with several network clients and protocols that are
enabled by default for Dial-Up Networking.However, for use with Internet Service
Providers,no network clients and protocols are required except the standard
Internet TCP/IP protocol.The presence of unneedednetwork clients is normally
harmless and the only effect is toslow down the login process as Win95 has to
negotiate each of the network clients and protocols.Since Internet Service
Providers only support the TCP/IP protocol,we suggest disabling Win95's attempt
to negotiate these network clients and protocols.To do so, open the
"Dial-Up Networking" window in the "My Computer" folder, RIGHT click on the
connection icon then select "Properties".In the properties configuration window
that appears click the "Server Type" button and make certain that the
"Log on to network", "NetBEUI" and "IPX/SPX Compatible" boxes are NOT checked.
Click OK to save any changes required and close the properties configuration
window. Your login should now take only a few seconds.
Your connection may have only recently began exhibiting the
'Win95 slow logon' problem.
We are not sure what affects the normal negotiation timeout process.
There are several different references to favors of the problem in the Microsoft
technical support knowledge base.
Our guess is that variable timing delays (called 'race' conditions) introduced
by a particular conputer comfiguration,
modem type, connection data rate, telephone line quality and load on our
communications servers can all play a part.
Finally, you may have installed software or otherwise inadvertantly changed
your Win95 configuration to cause additional unneeded network clients or
protocols to be loaded.
Why can't Win95 "negotiate a compatible set of network protocols"?
A.We have observed that a small number of Win95 users seem to have occasional
problems connecting. The symptom is that Windows 95 will dial the number,
successfully login and then immediately fail during thePPP negotiation phase
with a message similar to: "Dial up networking could not negotiate a compatible
set of network protocols you specified in the server type setting".
Often rebooting the computer can clear the problem.Sometimes doing nothing but
waiting a few minutes and then redialing will cause the problem to disappear.
For some users, they must remove and then add back the "TCP/IP" networking
protocol to clear the problem.The primary cause for difficulty seems to be
related to the NetBEUI, IPX/SPX, and TCP/IP protocolsare used by default for
a Dial-Up Networking "connectoid". (Hey, we don't name these things...
"connectoid" is Microsoft's name forthe Dialup Networking configuration that
you created to connect).However, for use with Internet Service Providers,
nothing should be bound to the Dial-Up Networking Adapter but the standard
Internet TCP/IP protocol. Something will occassionally cause Win95 to bind other
protocols to the adapter as well.
This is normally harmless and the only effect is to slow down the login process
as Win95 has to timeout on the unsupported protocols.
Apparently, occassionally this process fails and the error message
"Dial up networking could not negotiate a compatible set of network protocols
you specified in the server type setting" error appears.
We are not sure what causes the normal timeout process to fail.
Our guess is that variable timing delays (called 'race' conditions) introduced
by a particular computer comfiguration, modem type, connection data rate,
telephone line quality and load on our
communications servers can all play a part.