Group Policy Settings Do Not Apply to a Client Computer That Is Multihomed (830513)



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

Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

Group Policy settings may not apply to a client computer that is multihomed. A multihomed computer is a computer that is configured to have more than one IP address.

WORKAROUND

To work around this issue, use any one of the following methods:

Method 1

Set the route table entry for the unreachable DNS server. To do this, follow these steps:
  1. Click Start, and then click Run.
  2. In the Run dialog box, type cmd, and then click OK.
  3. At the command prompt, type the following command, and then press ENTER:

    route ADD [DNS server IP address] MASK [dns Server Subnet Mask] [Client gateway IP] METRIC [cost for destination] IF [Interface index number] -p

    Example:

    route ADD 10.100.0.1 MASK 255.255.255.255 10.100.0.100 METRIC 1 IF 2 -p

    Note The -p switch makes the route persistent.

Method 2

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Set the NetBT DNS query timeout to match the maximum timeout for DNS (approximately 17 seconds). To do this, follow these steps:
  1. Click Start, and then click Run.
  2. In the Run dialog box, type regedit, and then click OK.
  3. In Registry Editor, locate the following key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\

  4. In the right pane, right-click the LmhostsTimeout DWORD, and then click Modify.
  5. In the Edit DWORD Value dialog box, click Decimal under Base. Under Value data, type 17000, and then click OK. Note the following infrmation about this registry value:
    • Entry name: LmhostsTimeout
    • Subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters
    • Value type: REG_DWORD
    • Valid range: Decimal: 1000 to 4294967295 (Hexadecimal: 3E8-0xFFFFFFFF)
    • Default: 6000 (time in milliseconds)
  6. On the File menu, click Exit.

Method 3

Change the priority of the network interface cards so that the card that has the highest priority is pointing to the network that you are logging on to. To do this, follow these steps:
  1. Click Start, and then click Control Panel.
  2. In Control Panel, click Network and Internet Connections, and then click Network Connections.
  3. On the Advanced menu, click Advanced Settings.
  4. Under Connections, select the network adaptor that points to the network that you want to log on to, and then click the up arrow to move the adaptor to the top of the list. Click OK.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.

Modification Type:MajorLast Reviewed:3/9/2005
Keywords:kberrmsg kbprb KB830513 kbAudITPRO kbAudEndUser