DOCUMENT:Q178205
TITLE   :Connecting to a Server is Slow over RAS Using LMHOSTS File
PRODUCT :Microsoft Windows NT
PROD/VER:4.00
OPER/SYS:WINDOWS
KEYWORDS:kbbug4.00 kbfix4.00 kbfile kbbug kbfix

-----------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Windows NT Workstation version 4.0
 - Microsoft Windows NT Server version 4.0
-----------------------------------------------------------------------

SYMPTOMS
========

When you dial into a remote site, the initial attempt to connect to a
server share point can take up to 90 seconds to complete.

CAUSE
=====

If the name of the server being connected to is resolved by using the local
LMHOSTS file, when attempting to connect, Windows NT must wait for the
connection attempt over the local LAN to timeout before the connection over
RAS is accepted. If you use the normal default TCP/IP values for
TcpMaxConnectRetransmissions, it will take 90 seconds to time out.

This problem is not experienced if WINS or broadcast name resolution is
used to locate the computer being connected to.

RESOLUTION
==========

You can work around this problem by lowering the value of
TcpMaxConnectRetransmissions. Setting this to a value of 1 reduces the
delay to 18 seconds. However, lowering this value may cause problems when
establishing a connection to a server over a slow link.

To resolve this problem, obtain the following fix or wait for the next
Windows NT service pack.

This fix should have the following time stamp:

   12/18/97  08:43p               119,856 Netbt.sys (Intel)
   12/18/97  08:40p               220,048 Netbt.sys (Alpha)

This hotfix has been posted to the following Internet location:

   ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/
   hotfixes-postSP3/netbt-fix/

NOTE: The above link is one path; it has been wrapped for readability.

STATUS
======

Microsoft has confirmed this to be a problem in Windows NT version 4.0.
A supported fix is now available, but has not been fully regression tested
and should be applied only to systems experiencing this specific problem.
Unless you are severely impacted by this specific problem, Microsoft
recommends that you wait for the next Service Pack that contains this fix.
Contact Microsoft Technical Support for more information.

Additional query words: 4.00 
============================================================================

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.