usually requires the same modem driver to be installed
on the ModemServe Client as is installed on ModemServe
Server. For example if one end is using the manufactures
modem driver, the other end should not use a Windows
Standard 56k modem driver.
If you are unable to get Dial-Up networking to work,
and you are using matching modem drivers, the first
thing to do is check that you are able to sucessfully
dial the same phone number using Hyperterminal
that you intend to use for Dial-Up Networking.
Client is properly installed and configured.
is properly installed and configured.
are properly installed and configured.
number being dialed is correct, and the remote
location being dialed is answering.
Once you have
confirmed that that all these things have been tested,
it narrows down the cause to being a configurationissues
with Dial-Up Networking itself. Make sure the network
settings are correct, such as the username/password
being entered correctly (these are usually case sensitive).
If you get
strange network behavior when you attempt to use Dial-Up
Networking over ModemServe Client.
If some servers
on the LAN become inaccessible or you get messages
about being logged off the network, it could be due
to the fact that that Dial-Up Networking causes
a new "default route" to be added to the routing table
once a successful session is initiated. If the local
LAN contains multiple subnets, and the PC gains access
to those subnets using a default route in the routing
table, the new default route added by Dial-Up Networking
will supercede the original. This has the effect of
allowing access to only the local subnet, because
packets destined for the other subnets will be routed
to the modem rather than the network card.
is not specific to ModemServe Client and occurs on
any PC using a local modem as well. The Microsoft
KnowledgeBase contains the following articles concerning
only mention NT and RAS, but they are equally applicable
to Windows XP/2000/2003 running Dial-Up Networking.