The information in this article applies to:
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).
Cannot Dial with RAS
When you attempt to dial with Dial-Up Networking, the following error message may appear:
If you receive this or another error message that indicates that the modem is not working properly, refer to the following articles in the Microsoft Knowledge Base:
If you have upgraded from Windows NT 3.51 and you are running a program that monitors the phone line (for example, a fax program), you may receive an error message that indicates the port is busy when you try to dial out with Dial-Up Networking. For example:
If you installed RAS in Windows NT 3.51 before upgrading to
Windows NT 4.0, the kernel-mode telephony driver that is used
in Windows NT 3.51 is retained and RAS uses non-Unimodem drivers.
If another program uses the Unimodem driver and is set answer
the line automatically, that program causes TAPI 2.0 to control
the communications port. When this occurs, the communications
port is not available to the non-Unimodem version of RAS.
Cannot Connect After Dialing with RAS
If the telephone line is unusually noisy, you may receive an error message such as:
This message indicates that the modem may not be able to negotiate a connection at a higher speed. Try setting the modem speed on the client computer down to a lower speed such as 9600 bps. To do so, follow these steps:
If the RAS server does not answer or you cannot connect, test
the connection from another computer. If you cannot connect using
another computer, there may be a problem with the RAS server.
Contact your network administrator for assistance.
If your modem is not listed, contact the modem's manufacturer or consider trying a supported modem.
Additional query words:
Keywords : kbnetwork ntras kbRAS NTSrvWkst