OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Bill Walsh (bwalshWYNTRAC.COM)
Date: Wed Apr 04 2001 - 17:48:36 CDT

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    This KB article is the exact text that I read in the Netmeeting Resource Kit
    posting.. If you read down through what you posted, you will see that it
    claims those ports for outbound calls.. my question was regarding inbound
    calls only, specifically inbound for program sharing/whiteboard etc only...

    I appreciate that though..

    regards,
    bill

    -----Original Message-----
    From: Free, Bob [mailto:RWF4pge.com]
    Sent: Wednesday, April 04, 2001 5:23 PM
    To: 'Focus on Microsoft Mailing List'
    Cc: 'bwalshWYNTRAC.COM'
    Subject: RE: [FOCUS-MS] Ports used for inbound Netmeeting 3.0

    From How to Establish NetMeeting Connections Through a Firewall [Q158623]

    NetMeeting uses the following Internet Protocol (IP) ports:

       Port Purpose
      -------------------------------------
      389 Internet Locator Server [Transmission Control Protocol (TCP)]
      522 User Location Server (TCP)
      1503 T.120 (TCP)
      1720 H.323 call setup (TCP)
      1731 Audio call control (TCP)
      Dynamic H.323 call control (TCP)
      Dynamic H.323 streaming [Realtime Transport Protocol (RTP) over User
    Datagram Protocol (UDP)]

    To establish outbound NetMeeting connections through a firewall, the
    firewall
    must be configured to do the following:

     - Pass through primary TCP connections on ports 522, 389, 1503, 1720 and
    1731.

     - Pass through secondary UDP connections on dynamically assigned ports
      (1024-65535).