Some Versions of NetMeeting Do Not Support Multihoming (236160)


The information in this article applies to:

  • Microsoft NetMeeting 2.11 for Windows NT 4.0
  • Microsoft NetMeeting 2.1 for Windows NT 4.0
  • Microsoft NetMeeting 2.11 for Windows 98
  • Microsoft NetMeeting 2.1 for Windows 98
  • Microsoft NetMeeting 3.01 for Windows 95
  • Microsoft NetMeeting 2.11 for Windows 95
  • Microsoft NetMeeting 2.1 for Windows 95
  • Microsoft NetMeeting 3.01 for Windows NT 4.0
  • Microsoft NetMeeting 3.01 for Windows 98
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.
Modification Type:MajorLast Reviewed:12/5/2003
Keywords:kbenv kbprb KB236160
©2003 Microsoft Corporation. All rights reserved.