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).

-----Original Message-----
From: Bill Walsh [mailto:bwalshWYNTRAC.COM]
Sent: Wednesday, April 04, 2001 2:03 PM
To: FOCUS-MSSECURITYFOCUS.COM
Subject: [FOCUS-MS] Ports used for inbound Netmeeting 3.0

I plan on implementing Netmeeting 3.0 (the version including with Win2000)
to receive calls strictly for program sharing, not audio/video
conferencing.. I have to open up ports on the firewall to do so, but the
Netmeeting Resource Kit on MS's web site is not very specific regarding
inbound calls, they make reference mainly to outbound calls..

I suspect that it is simply ports 522 and 1503 via TCP, is this correct?
Does anyone have any experience with this?

regards,
bill

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