Microsoft KB Archive/236160

= Some Versions of NetMeeting Do Not Support Multihoming =

Article ID: 236160

Article Last Modified on 1/24/2007

-

APPLIES TO


 * Microsoft NetMeeting 2.11
 * Microsoft NetMeeting 2.1 Standard Edition
 * Microsoft NetMeeting 2.11
 * Microsoft NetMeeting 2.1 Standard Edition
 * Microsoft NetMeeting 3.01 Standard Edition
 * Microsoft NetMeeting 2.11
 * Microsoft NetMeeting 2.1 Standard Edition
 * Microsoft NetMeeting 3.01 Standard Edition
 * Microsoft NetMeeting 3.01 Standard Edition

-



This article was previously published under Q236160



SYMPTOMS
When NetMeeting connects to an Internet Locater Service (ILS) server, it uses an IP address. When you establish a call, this address is used by NetMeeting users to connect directly to the computer to which the IP address belongs. If a computer has multiple network adapters bound to TCP/IP (such as the Dial-Up Networking adapter and a network adapter), NetMeeting may register the incorrect IP address with the ILS server. This results in NetMeeting users being unable to communicate with that computer.



CAUSE
NetMeeting sends the IP address of the first network adapter that is bound to TCP/IP. When NetMeeting sends a request for the IP address, Wldapi32.dll (the component responsible for the support of multihoming in NetMeeting) sends the address of the first adapter that is bound to TCP/IP. The first adapter is not always the one being used to connect to the ILS server.



STATUS
This behavior is by design in NetMeeting 2.1 and 2.11.

When NetMeeting 3.01 is used on a multihomed computer running Microsoft Windows 98 or Microsoft Windows NT 4.0, it determines the correct adapter.

This feature is not available with NetMeeting 3.01 for Microsoft Windows 95.

Keywords: kbenv kbprb KB236160

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.