US Robotics has a file available containing updated MODEM.INF settings for use
with all of their modems. These MODEM.INF settings have been tested with the
Remote Access Service (RAS) software included with Windows for Workgroups 3.11,
Windows NT version. 3.1, and Windows NT version 3.5. The file, MDMUSR.INF,
can be downloaded from the US Robotics BBS at (847) 982- 5092.
The Microsoft Windows NT Hardware Compatibility List (HCL) lists a number of
modems supported for use with Windows NT Remote Access Services (RAS). Modems
not listed on the HCL, however, work with RAS if you supply RAS with the
command strings required by the modem. You can supply RAS with these command
strings by appending a new section for your modem to the
%SystemRoot%\SYSTEM32\RAS\MODEM.INF file. Some modem vendors have created
MODEM.INF sections for their unsupported modems to operate with RAS or to
update the MODEM.INF for their supported modems. The table below lists third-
party vendors, their phone numbers, and the names of files containing MODEM.INF
If you use Windows NT Remote Access Service (RAS) and a Megahertz modem, you
can obtain a software support release from Megahertz Corporation that contains
a new MODEM.INF file with updated drivers for all Windows NT supported
On your computer running Windows NT or Windows 95, when you use Remote Access
(RAS) or Dial-up networking with the PPP and TCP/IP protocols enabled, you
cannot connect to computers on the Internet that are running the World Wide
Web (WWW), FTP, Telnet, or other software that relies on TCP/IP packets to
exchange information. PING.EXE and TRACERT.EXE, however, still function
When you attempt to dial out from a Windows NT Remote Access Service (RAS)
client using the Remote Access protocol Serial Line Internet Protocol (SLIP)
or Point to Point Protocol (PPP) to a TCP/IP server, one of the following
error messages appears: ...
This article contains steps to help you troubleshoot issues with the Remote
Access Service (RAS) in Windows NT 4.0. This article focuses on issues that
can occur when you use RAS to dial into another computer or an Internet
service provider (ISP).
Potential causes: FreePPP not selected in MacTCP or TCP/IP, FreePPP not enabled
in Extensions Manager, Other PPP extensions in the Extensions folder, MacTCP or
TCP/IP preferences are corrupt, Corrupt Finder Preferences, "Greg's Buttons"
Potential Causes: Fax or other communication software is running in the
background, A communication application may be loading at startup, Modem
may not have released the previous port, A communications extensions
Potential Causes: Incorrect spelling of the URL or it is
outdated, Incorrect Usrname or Password, Wrong or missing DNS entries in
the MacTCP or TCP/IP when trying to access server, Corrupt MacTCP or
TCP/IP Preferences, MacTCP or Open Transport (TCP/IP) Extensions not
enabled, Extension conflict, Corrupt files in the Netscape Cache
folder, Networking software is corrupt.
If you are running System 7.6 or 7.6.1 on any PowerMac and you have disabled
the ObjectSupportLib by de-selecting it in Extensions Manager, removing it
from the Extensions folder, selecting "All Off" in the Extensions Manager, or
removing it from the Mac entirely you will receive the error message.
Potential Causes: Incorrect spelling of the URL, or URL is
outdated, Incorrect username or password, Incorrect DNS entries in the
MacTCP or TCP/IP, Corrupt MacTCP or TCP/IP Preferences, MacTCP or TCP/IP
Extensions disabled, Extensions Conflict, Memory conflict, Corrupt files
in the Explorer Cache.
Potential Causes: Modem port speed is set to high, If the system has a
Global Village modem, the Global Village Toolbox may not be running, A
communications extensions conflict, Modem is not connected properly.