Addname Corrupts the Lmhosts File and Cache

• Microsoft LAN Manager, versions 2.0, 2.0a, 2.2, 2.2b
• Microsoft Windows for Workgroups version 3.11

SYMPTOMS

A build of the Addname utility that was initially released with Windows for Workgroups version 3.11 causes problems when used. The "addname /save" command generates strange characters in the LMhosts file.

When you start the machine with a correct Lmhosts file, the machine boots and the Lmhosts entries get loaded properly. But "addname /save" (which saves the Lmhosts cache entries to the Lmhosts file) corrupts the Lmhosts file with strange characters. In the example below, the characters on the left are IP addresses; the characters on the right are meaningless:

137.61.97.229       "39FC10x1B\0xFFB\ 1\0xFF"     #DOM:
57.51.50.65         "          Qa=\0xFFA6"     #PRE
32.32.52.48         "      \0xFF\0x01;\0xFF \0x1B\0xFFB\0x00\0x00"
58.67.66.0
RO\0xFF\0xFF\0xFF\0xFF\0xFF\0x0A\0xFFQ\0xFF*\0xFF!\0xFF\0xFF 

CAUSE

One of the Addname builds initially released with the WFWG 3.11 TCP/IP stack (1.0a) was corrupt, causing problems.

RESOLUTION

For a workaround, use the Addname utility that comes with either LAN Manager 2.2 TCPstack or WFWG 3.1 TCP connections pack.

To resolve the problem, obtain the updated Addname build from the Internet.

MORE INFORMATION

The Addname utility shipped with every Microsoft TCP/IP stack. You use it to add a NetBIOS name and its IP address to the cache used for remote NetBIOS name resolution in TCP/IP-based networks.

Format of Addname command

• addname computername ipaddress



• addname computername /delete



• addname /load (to load an LMhosts file to cache)



• addname /save (to save the cache contents to a file--usually LMhosts).

Additional query words: wfw wfwg 3.11 garbage

Keywords : ntprotocol
Version : :2.0,2.0a,2.2,2.2b; WINDOWS:3.11
Platform : WINDOWS
Issue type :