Microsoft KB Archive/169455: Difference between revisions

From BetaArchive Wiki
(importing KB archive)
 
m (Text replacement - """ to """)
 
Line 15: Line 15:
== SYMPTOMS ==
== SYMPTOMS ==


Documentation from Chapter 10 of the "Microsoft Windows NT Server Networking Supplement" includes an example for using the #MH keyword in the LMHOSTS file. But the #MH symbol itself is missing from the example.
Documentation from Chapter 10 of the "Microsoft Windows NT Server Networking Supplement" includes an example for using the #MH keyword in the LMHOSTS file. But the #MH symbol itself is missing from the example.


In Chapter 10, page 517, under the heading, "Adding Multihomed Devices by Using #MH," it states:
In Chapter 10, page 517, under the heading, "Adding Multihomed Devices by Using #MH," it states:


<pre>  For example, the entries required to map name to IP address for a
<pre>  For example, the entries required to map name to IP address for a
Line 62: Line 62:
</span><br />
</span><br />
<br />
<br />
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED &quot;AS IS&quot; 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.</blockquote>
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.</blockquote>
Last reviewed: July 17, 1997<br />
Last reviewed: July 17, 1997<br />
<span>© 1998 Microsoft Corporation. All rights reserved. Terms of Use.</span><br />
<span>© 1998 Microsoft Corporation. All rights reserved. Terms of Use.</span><br />
|}
|}

Latest revision as of 10:04, 21 July 2020


DocErr: #MH Switch LMHOSTS Missing in Resource Kit 4.0 Example

Last reviewed: July 17, 1997
Article ID: Q169455

The information in this article applies to:

  • Microsoft Windows NT Workstation version 4.0
  • Microsoft Windows NT Server version 4.0

SYMPTOMS

Documentation from Chapter 10 of the "Microsoft Windows NT Server Networking Supplement" includes an example for using the #MH keyword in the LMHOSTS file. But the #MH symbol itself is missing from the example.

In Chapter 10, page 517, under the heading, "Adding Multihomed Devices by Using #MH," it states:

   For example, the entries required to map name to IP address for a
   multihomed device with two NICs are:

   102.54.94.91  accounting     #accounting server NIC 1
   102.54.94.91  accounting     #accounting server NIC 2

Note that the #MH keyword does not appear in this example.

CAUSE

This is a documentation error.

RESOLUTION

The correct syntax for the above example is as follows:

   102.54.94.91  accounting  #MH   #accounting server NIC 1
   102.54.95.91  accounting  #MH   #accounting server NIC 2

Note also that you should have different IP addresses for the two network adapters. MORE INFORMATION

The correct implementation of the #MH switch for the LMHOSTS file is illustrated on pages 21 and 22 of the following Microsoft Windows NT white paper:

   Microsoft Windows NT Server 4.0, Windows Internet Naming Server (WINS),
   Architecture and Capacity Planning

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: lmhost lm host multi-homed multi homed

Keywords : kbnetwork ntdocerr ntreskit NTSrvWkst nttcp
Version : 4.0
Platform : WinNT
Issue type : kbdocerr


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: July 17, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.