|
Member FAQ and Help page
Use the links below to help navigate this page.

why is win 95/98 so slow to log in?
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 unneeded network
clients is normally harmless and the only effect is to slow 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 computer configuration,
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 inadvertently 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"?
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 the PPP 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 protocols that are used by default for a Dial-Up Networking
"connectoid". (Hey, we don't name these things...
"connectoid" is Microsoft's name for the 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 occasionally 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, occasionally
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 configuration, modem type, connection data rate, telephone
line quality and load on our communications servers can all play a part.
Since Internet Service Providers only support the TCP/IP protocol, we
suggest removing the NetBEUI and IPX/SPX protocols so that Dial-Up Networking
cannot un-intentionally bind to them.
To change your Win95 settings to be compatible with Internet Service
providers, make certain the NetBEUI and IPX/SPX protocols from the Control Panel
folder - Network section have been removed. We also suggest the additional step
of removing the Microsoft TCP/IP protocol, even though it will be added again
later.
Once the protocols have been removed, restart Win95 and follow our
instructions for configuring Win95 to connect. When configuration is complete
open the "Dial-Up Networking" window, 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.
If the "Dial up networking could not negotiate a compatible set of
network protocols you specified in the server type setting" error continues
to appear, examine your modem type setting in the modems icon of the control
panel. The error may occur if Windows 95 was unable to correctly identify your
modem brand and model or it was otherwise set incorrectly.
We suggest contacting the manufacturer of the modem for advice on how
best to configure Win95 and the modem to interoperate. If unable to contact the
manufacturer or you don't know who the manufacturer of the modem is, we have had
good luck with just setting the modem type to be one of the appropriate
"(Standard Modem Types)" choices in the modems icon of the control
panel.
|

how do I setup my e-mail?

what is my mail server incoming (pop3) and outgoing
(smtp) addresses?
Some examples show the mail server addresses as being pop3.yourdomain.com
and smtp.yourdomain.com or to the like. These examples are not
correct. The correct addresses for your incoming (pop3) and outgoing
(smtp) mail servers should be mail.uSurfer.net
for both entries.
|

what should my email logon or pop3 account name be?
The email logon or pop3 account name should be (your username)@uSurfer.net.
If your email program asks for a SMTP (outgoing) server account name,
this would be the same - (your username)@uSurfer.net.
|
my dialup logon and email usernames are different, is
my password too?
Your dialup logon username is assigned by uSurfer,
but you choose your own email username. You also choose your own
password which is used with both your logon username and your email
username.
|
"invalid password- enter password", when
trying to get mail in netscape?
If after verifying you have all the proper Netscape mail server
settings correct, you receive this message, you may have to change your
email username format to appear like this - (your username)%uSurfer.net
instead of (your username)@uSurfer.net, thus taking out the @ sign and
replacing it with the % sign.
|

|