An "Error 611" or "Error 720" error message occurs when you try to dial out from a Windows NT Remote Access Service (RAS) client and an event log error occurs when the Remote Access Service (RAS) server service fails to start (123298)
The information in this article applies to:
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Professional
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Workstation 3.51
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Server 4.0
This article was previously published under Q123298 IMPORTANT: This article contains information about modifying the registry.
Before you modify the registry, make sure to back it up and make sure that you
understand how to restore the registry if a problem occurs. For information
about how to back up, restore, and edit the registry, click the following
article number to view the article in the Microsoft Knowledge Base: 256986 Description of the Microsoft Windows Registry
SYMPTOMS 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,
you receive one of the following error messages: Using SLIP Error 611: Route is not available
Using PPP Error 720: No PPP control protocols
configured. Additionally,
when you start the Windows NT-based computer, the Remote Access Service does not start. You may receive the following error in the event log: Event ID: 20055
Source: RemoteAccess
Description: The Remote Access Service server could not be started
because it has been configured to access the network and
there are no network adapters available.
CAUSE This problem may have several different causes. Two known
causes are the NetBIOS interface not being installed or
removed and the NetBIOS binding being disabled. The
NetBIOS interface is required for establishing logical names and sessions on
the network for Windows NT.
RESOLUTIONWARNING: If you use Registry Editor incorrectly, you may cause serious
problems that may require you to reinstall your operating system. Microsoft
cannot guarantee that you can solve problems that result from using Registry
Editor incorrectly. Use Registry Editor at your own
risk. To correct this problem, select the Network
option from Control Panel and do the following:
- Verify that the NetBIOS interface is installed.
If necessary, use the following steps to install the NetBIOS interface:
- Click Start, point to
Settings, click Control Panel, and then
double-click the Network icon.
- Click Add Software.
- Click NetBIOS Interface in the
Network Software list, and then click
Continue.
- Type the location of your Windows NT files, and then
click Continue.
- Click Close, and then restart the
computer when you are prompted.
- Verify that the bindings of the NetBIOS interface are
enabled and properly established with the NDISWAN drivers. To do so:
- Start Registry Editor, and locate the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\00xx 00xx is the subkey that is
defined in "DriverDesc" as "WAN Miniport(IP)". - Click the LinKage subkey.
- In the detail pane, you should have a "RootDevice" of
"NdisWanIp". In addition, there will be an "UpperBind" key, which needs to have
a value of Tcpip.
Modification Type: | Major | Last Reviewed: | 7/15/2005 |
---|
Keywords: | kberrmsg kbtshoot kbnetwork KB123298 kbAudITPRO |
---|
|