RAS Clients Run Winsock and RPC Applications Slowly

 Last reviewed: December 31, 1997
Article ID: Q167038
The information in this article applies to:
  • Microsoft Windows NT Server version 4.0
  • Microsoft Routing and Remote Access Service Update for Windows NT Server version 4.0

SYMPTOMS

Remote Access Server (RAS) clients experience delays when Winsock or RPC applications attempt to connect to remote resources.

CAUSE

The RAS Server or Routing and Remote Access Service (RRAS) Server has provided a Domain Name Service (DNS) IP address to the client that is unreachable. This causes Winsock and RPC applications (over TCP/IP) to fail DNS name lookups.

By default, RAS or RRAS Servers project any DNS IP addresses they are configured with to RAS clients using TCP/IP. If the RAS or RRAS Server has a DNS IP address that cannot be reached by the RAS client, the RAS client experiences delays whenever an application attempts to query the DNS name servers. The RAS or RRAS Server may be unreachable because the DNS server is not responding or because the RAS or RRAS Server is multihomed and the DNS server is on a network not accessible to the RAS client.

RESOLUTION

Perform one of the following steps to resolve this problem:

Windows NT RAS Server

Install the latest Windows NT Service Pack for version 4.0.

Windows NT RRAS Server

Obtain the Routing & Remote Access Service Hotfix Update mentioned below.

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was corrected in the latest Microsoft Windows NT 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K
Microsoft has confirmed this to be a problem in Routing and Remote Access Update for Windows NT Server version 4.0. This problem was corrected in the Routing & Remote Access Service Hotfix Update. You can obtain this update from Microsoft's World Wide Web Site on the Internet at the following location: 

   http://www.microsoft.com/communications/routing&ras.htm
NOTE: Because the Microsoft Web site is constantly updated, the site address may change without notice. If this occurs, link to the Microsoft home page at the following address: 

   http://www.microsoft.com/

MORE INFORMATION

Microsoft has added a new registry value to the RAS service that allows an administrator the option of preventing all DNS IP addresses from being projected to RAS clients.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

To enable this feature to prevent the RAS or RRAS Server from sending DNS Server IP address(es) to RAS clients, perform the following steps:

  1. Run Registry Editor (Regedt32.exe).

  2. Go to the following key in the registry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RemoteAccess\ Parameters\IP

  3. On the Edit menu, click Add Value and use the following entry: 

          Value Name: SuppressDNSNameServers
      Data Type:  REG_DWORD

          Value:      1 or 0 (default=0, value of 1 prevents RAS Server from
                  sending the DNS Server address(es) to RAS clients)


  4. Exit the Registry Editor and restart the computer for the change to
   take effect.



	
			
	















	






Additional query words: slow delayed Exchange client socket application

RPC Remote Procedure Call DNS RAS Remote Access Service ntrouter rras

Keywords          : kbbug4.00 kbfix4.00 kbfix4.00.sp2 NTSrv nttcp kbnetwork kbbuglist kbfixlist

Version           : 4.00

Platform          : winnt

Issue type        : kbbug

Solution Type     : kbservicepack








THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND.  MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES.  SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.






	
	Last reviewed:  December 31, 1997
	

	© 1998 Microsoft Corporation. All rights reserved. Terms of Use.