At 10:18 AM 2/15/01, Joe Rice wrote:
>Hi,
> I have to get my firewall to allow Microsoft
>Net Meeting to work. I've searched Microsoft's page
>for port listings but i can't find any thing.
>
>Can anyone tell me the port (or range) that i need
>to allow out.
That's an easy one. According to Microsoft:
http://www.microsoft.com/Windows/Netmeeting/Corp/ResKit/Chapter4/default.asp
"To establish outbound NetMeeting connections through a firewall, the
firewall must be configured to do the following:
Pass through primary TCP connections on ports 389, 522, 1503, 1720,
and 1731.
Pass through secondary TCP and UDP connections on dynamically
assigned ports (1024-65535)."
Now the important thing to do is to make sure you close all your other
ports in order to have a secure firewall!
I'm being facetious. Opening all these ports would be a Bad Thing (TM) to
do. You may want to rethink about if NetMeeting is really mission critical
to your organization. I know of folks doing it "relatively secure" through
a firewall by hosting a hardened NetMeeting server outside their
firewall. Then all hosts outside the firewall would connect to a meeting
room on the outside server and would not have access inbound through the
firewall. Internal clients trying to connect to a meeting would only have
connections outbound through the firewall to the external server. But
opening up all these ports inbound through the firewall to the outside
world (as Microsoft suggests) would not be very secure. Remember one
thing, your internal users can configure their PCs to accept NetMeeting
calls from anyone and have that connection share their applications, sort
of like Back Orifice.
Hope this helps....
-- Joe
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
