Real Mode DHCP Client Sets Parameters Incorrectly on Token Ring

ID: Q159609

The information in this article applies to:

• Microsoft LAN Manager version 2.2c
• Microsoft Network Client version 3.0 for MS-DOS

SYMPTOMS

Microsoft Lan Manager 2.2C clients and Microsoft Network Clients, using TCP/IP with Dynamic Host Configuration Protocol (DHCP) on Token Ring networks, may experience one of the following:

• The client is unable to obtain an IP address by means of a DHCP Relay Agent.

  -or-

• When using TCP/IP with a UNIX DHCP server on a Token Ring network, clients will obtain two TCP/IP leases.

CAUSE

The DHCP client for the real mode (16-bit) TCP/IP stack incorrectly sets the DHCP htype field to "ethernet" regardless of the media type to which the client is attached. This can cause the packet to be dropped when traversing some DHCP relay agents, resulting in failure to obtain an IP address and other parameters.

Also, the DHCP client for the real mode (16-bit) TCP/IP stack incorrectly sets the DHCP client-identifier in the DHCP Option field to "ethernet" regardless of the media type to which the client is attached.

STATUS

Microsoft has confirmed this to be a problem in the LAN Manager 2.2C client, and the MS Networks 3.0 client, using the real-mode 16 bit TCP/IP stack. A supported fix is now available, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Additional query words: source routing tokenring

Keywords          : nttcp prodlm 
Version           : 2.2c,3.0
Issue type        : kbbug
Solution Type     : kbfix

Last Reviewed: August 11, 1998