Microsoft KB Archive/278908

= NetBT query is unsuccessful after you import the LMHOSTS file =

PSS ID Number: 278908

Article Last Modified on 4/26/2004

-

The information in this article applies to:


 * Microsoft Windows Server 2003, Standard Edition
 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Datacenter Edition
 * Microsoft Windows Server 2003, 64-Bit Enterprise Edition
 * Microsoft Windows Server 2003, 64-Bit Datacenter Edition

-



This article was previously published under Q278908





SYMPTOMS
After you import an LMHOSTS file that contains any &quot;as-is&quot; name (a name in quotation marks) to a WINS database on a Windows Server 2003 Datacenter Edition computer, when you perform an NetBT query, you receive a &quot;Name doesn't exist&quot; message.

For example, if you run the following query:

1.1.1.1 &quot;AA&quot;

you can import the LMHOSTS file, but subsequent queries for this quoted name are unsuccessful.



CAUSE
This issue occurs because Windows Server 2003 Datacenter Edition has changed the way WINS parses the LMHOSTS file.



WORKAROUND
To work around this issue, use the Netsh.exe command-line tool to manually add group names and unique names instead of using the Import function in WINS. To use this method, follow these steps:
 * 1) At a command prompt, type netsh.
 * 2) At the netsh prompt, type wins server , where   is the IP address of the WINS server.
 * 3) At the netsh wins server prompt, type add name Name=  endchar=1b IP=, where   is the name of the domain, and   is the IP address of the primary domain controller in the domain.

For example, at the c:\>netsh wins server prompt, type add name Name= endchar=1b IP=.



RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;%5BLN%5D;CNTACTMS

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.   Date         Time   Version       Size     File name  Platform --  08-Mar-2004  17:19  5.2.3790.139  144,384  Wins.exe        x86 08-Mar-2004 16:29  5.2.3790.139  467,968  Wins.exe      IA-64



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

Keywords: kberrmsg kbprb KB278908

Technology: kbWinServ2003Data kbWinServ2003Data64bit kbWinServ2003Data64bitSearch kbWinServ2003DataSearch kbWinServ2003Ent kbWinServ2003Ent64bit kbWinServ2003Ent64bitSearch kbWinServ2003EntSearch kbWinServ2003Search kbWinServ2003St

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.