Here's from the MS website, showing that most of the ports NetMeeting
uses are on TCP. But the vast majority of applications use Both the TCP
and UDP ports of the same number. Even ftp..
http://www.good-stuff.co.uk/useful/portfull.html
And the url for getting NetMeeting up and running through your firewall:
http://support.microsoft.com/support/kb/articles/Q158/6/23.asp
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)]
Cavell McDermott
Domino Admin
APW Ltd. - Texas Campus
214-343-1400 - Main
214-355-2039 - Helpdesk
214-341-9950 - Fax
http://www.apw.com
"Sadler,
Connie J" To: [EMAIL PROTECTED]
<csadler@bnl. cc: James Paterson
<[EMAIL PROTECTED]>,
gov> [EMAIL PROTECTED]
Subject: RE: Firewall Friendly Video
Conferencing
11/12/2001
11:35 AM
But some forms of traffic are much worse than others - I'd rather have
inbound ftp, for example, which can be controlled, than UDP, which offers
up
a much bigger risk... that's the problem with Netmeeting, from what I
understand - it's the UDO protocol that is difficult to manage.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 12, 2001 10:59 AM
To: Sadler, Connie J
Cc: James Paterson; [EMAIL PROTECTED]
Subject: RE: Firewall Friendly Video Conferencing
Any application you use will potentially make you vulnerable to exploits
being sent to that application/port which is opened up in the firewall. So
that is why you need to be careful on exactly what applications get used on
your LAN. If you open up a certain port, you run the risk of unintended
traffic coming into your network through that port. Firewalls themselves
cannot distinguish between bad traffic and good traffic going through a
port you opened up. That's where getting some form of IDS on your network
will help you ensure only good traffic is coming/going through your LAN.
Cavell McDermott
Domino Admin
APW Ltd. - Texas Campus
214-343-1400 - Main
214-355-2039 - Helpdesk
214-341-9950 - Fax
http://www.apw.com
"Sadler,
Connie J" To: [EMAIL PROTECTED],
James Paterson
<csadler@bnl. <[EMAIL PROTECTED]>
gov> cc:
[EMAIL PROTECTED]
Subject: RE: Firewall Friendly
Video Conferencing
11/10/2001
06:43 PM
Doesn't Netmeeting behind firewalls still make the clients vulnerable to
exploits?
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 09, 2001 12:43 PM
To: James Paterson
Cc: [EMAIL PROTECTED]
Subject: Re: Firewall Friendly Video Conferencing
Lotus Sametime.. But you incur the expense of a Domino license. I've
also had good success with Netmeeting with both parties being behind
firewalls.
Cavell McDermott
Domino Admin
APW Ltd. - Texas Campus
214-343-1400 - Main
214-355-2039 - Helpdesk
214-341-9950 - Fax
http://www.apw.com
James Paterson
<jpaterson@datam To:
[EMAIL PROTECTED]
irror.com> cc:
Subject: Firewall Friendly
Video Conferencing
11/08/2001 03:55
PM
Does anyone know of a good firewall friendly desktop video conferencing
product?
Thanks
J.
