TCP\IP-32B Using DHCP and M-Node Does Not Register All Names (151472)


The information in this article applies to:

  • Microsoft Windows NT Server 3.5
  • Microsoft Windows NT Server 3.51
  • Microsoft Windows for Workgroups
  • Microsoft TCP/IP-32 for Windows for Workgroups 3.11
  • Microsoft TCP/IP-32 for Windows for Workgroups 3.11a
  • Microsoft TCP/IP-32 for Windows for Workgroups 3.11b
This article was previously published under Q151472

SYMPTOMS

A Windows for Workgroups 3.11 Client running Microsoft TCP/IP-32B that gets its IP information from DHCP will not register its Server Service with the Secondary WINS Server if the Primary WINS Server is down.

CAUSE

A Windows for Workgroups client running TCP\IP-32B will not register its Server Service in WINS when -

  • It receives its IP information through DHCP, including Primary and Secondary WINS Servers and Node Type

    - AND -
  • A Node Type of M-Node is defined through DHCP

    - AND -
  • The Primary WINS Server is down

STATUS

Microsoft has confirmed this to be a problem in Microsoft TCP/IP-32 for Windows for Workgroups, versions 3.11B. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
Modification Type:MajorLast Reviewed:12/6/2003
Keywords:kbnetwork KB151472
©2003 Microsoft Corporation. All rights reserved.