How to Configure Netmeeting 2.0 with Proxy Server 1.0

 Last reviewed: October 30, 1997
Article ID: Q164038
The information in this article applies to:
  • Microsoft Proxy Server version 1.0

SUMMARY

This article describes how to get Microsoft NetMeeting 2.0 to work through Microsoft Proxy Server.

MORE INFORMATION

Microsoft NetMeeting 2.0 uses several secondary TCP and UDP ports to communicate. To allow NetMeeting to communicate fully, the following ports need to be enabled on the WinSock portion of the Proxy Server: 

   389       Internet Locator Server
   522       User Location Server
   1503      T.120 Protocol
   1720      H.323 call setup (TCP)
   1731      Audio call control (TCP)
   Dynamic   H.323 Call Control (TCP)
   Dynamic   H.323 streaming (RTP over UDP)
To configure these ports, perform the following steps:

  1. Go to the properties for the WinSock Proxy Server in the Internet Service Manager.

  2. Click the Protocols tab.

  3. Click Add.

  4. Assign the new protocol the name "NetMeeting".

  5. For the initial connection, assign the value of 1720 to the port.

  6. Set the port type to TCP and the direction to Outbound.

  7. Use the Add button to add all of the following ports: 

          Port or Range       Type      Direction
      -------------       ----      ---------

      389                 TCP       Inbound
      389                 TCP       OutBound
      522                 TCP       Inbound
      522                 TCP       Outbound
      1025-65535          TCP       Inbound
      1025-65535          TCP       Outbound
      1025-65535          UDP       Inbound
      1025-65535          UDP       Outbound
The H.323 call setup protocol (over port 1720) dynamically negotiates a TCP port for use by the H.323 call control protocol. Also, both the audio call control protocol (over port 1731) and the H.323 call setup protocol (over port 1720) dynamically negotiate UDP ports for use by the H.323 streaming protocol, called the real time protocol (RTP). In NetMeeting 2.0, two ports are determined on each side of the Proxy server for audio and video streaming. These dynamically negotiated ports are selected arbitrarily from all ports that can be assigned dynamically.

NetMeeting directory services require either port 389 or port 522, depending on the type of server you are using. Internet Locator Servers (ILSs), which support the lightweight directory access protocol (LDAP) for NetMeeting 2.0, require port 389. User Location Servers (ULSs), developed for NetMeeting 1.0, require port 522. 

Keywords          : kbenv kbinterop pxsconfig pxshowto pxsinterop
Version           : 1.0
Platform          : WINDOWS
Hardware          : ALPHA x86
Issue type        : kbhowto

================================================================================

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.