Knowledge Base

LmHosts Cache is Set for 6 Despite PROTOCOL.INI Setting

Article ID: 113408

Article Last Modified on 11/17/2003

Microsoft LAN Manager 2.2b, when used with:
- Microsoft MS-DOS 6.22 Standard Edition
Microsoft Windows for Workgroups 3.11

This article was previously published under Q113408

SYMPTOMS

The TCP/IP that ships with the Microsoft LAN Manager 2.2b MS-DOS Client and Windows for Workgroups 3.11 allows you to add MaxLmHosts=<number> to PROTOCOL.INI to specify the number of entries from the LMHOSTS file that should be loaded into the LM Hosts cache when the workstation is booted. This may not work, however, if you add entries with the Addname utility and the local LMHosts file either does not exist or contains fewer entries than you are adding.

CAUSE

Addname compares the number of entries in the local LmHosts file with the LmMaxHosts entry in PROTOCOL.INI and uses the lower number.

WORKAROUND

Create a local LmHosts file that is always larger than the centralized LmHosts files.

STATUS

Microsoft has confirmed this to be a problem in LAN Manager 2.2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: wfw wfwg 3.10 TCPIP LmHosts Hosts

Keywords: KB113408