Microsoft KB Archive/243076

= Using NetMeeting with Proxy Server 2.0 =

Article ID: 243076

Article Last Modified on 10/2/2002

-

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 Proxy Server 2.0 Standard Edition
 * Microsoft NetMeeting 3.01 Standard Edition
 * Microsoft NetMeeting 3.01 Standard Edition
 * Microsoft NetMeeting 3.01 Standard Edition
 * Microsoft NetMeeting 3.01 Standard Edition

-



This article was previously published under Q243076



SUMMARY
NetMeeting clients on an internal, private network behind a Microsoft Proxy server can connect to external NetMeeting hosts on the Internet. The Winsock Proxy Client software must be installed on the internal NetMeeting client computer and it must be configured to point to the appropriate Proxy server.

If the Access Control and Packet Filtering options are disabled on the Proxy server, no additional configuration is necessary. Microsoft recommends installing Service Pack 1 (SP1) for Microsoft Proxy Server 2.0, but it is not required.

For additional information about SP1, click the article number below to view the article in the Microsoft Knowledge Base:

238375 Proxy Server 2.0 Service Pack 1: List of Fixes



Configuring Proxy Access Control
If the Winsock Proxy service is configured to use Access Control, you must grant permission to use the ports needed by the NetMeeting H.323 protocol to the user who is logged on to the NetMeeting client computer.

The simplest way to grant the user access to the ports is to assign the user Unlimited Access rights on the Permissions tab in Winsock Proxy properties. If you cannot do this, you must add new protocol definitions first and then grant access to use the new protocols to the user.

You will need to add new protocol definitions for TCP outbound connections on ports 389, 522, 1503, 1720, and 1731. You must also add secondary TCP and UDP connections on dynamically assigned ports (1024-65535) inbound and outbound. For more detailed information about configuring the protocol definitions, please see the Microsoft NetMeeting Resource Kit, Chapter 4:

http://www.microsoft.com/windows/NetMeeting/Corp/ResKit/default.asp

Configuring Proxy Packet Filtering
If the Proxy server has Packet Filtering enabled, confirm that Dynamic Packet Filtering is also enabled. Because the NetMeeting H.323 protocol uses dynamic ports for communication, using dynamic packet filtering ensures that the appropriate ports are not blocked when the external host attempts to respond to the client. All dynamic ports used are closed by the Proxy server when the NetMeeting session ends.

NOTE: Microsoft does not support external clients connecting through the Proxy server to internal NetMeeting hosts. Because of the complexities involved in the H.323 protocol's use of dynamic ports for communication, it is not possible to "server proxy" NetMeeting.

