Let me preface this by saying I know nothing about Netmeeting, but I've had
to set up similar services through firewall devices. ;)
Are you a client connecting to the internet through a firewall and trying to
establish a netmeeting connection, or are you setting up a Netmeeting server
for other people to get to? The article seems to be aimed at an end-user
who is trying to configure a personal firewall to allow Netmeeting
connections out.
The big scary-looking range of ports (1024-65535) are outbound UDP ports,
which is a very common requirement. A lot of firewalls allow this by
default because it can be (sometimes incorrectly) assumed that a connection
originating from behind the firewall going out to the internet should be
allowed.
If you are trying to set up a server for other people to connect into,
though, your requirements will probably be different. I could be reading it
wrong, but it doesn't seem like the article from MS really adresses that.
-Jeff
> -----Original Message-----
> From: Sarbjit Singh Gill [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 11, 2002 2:37 PM
> To: [EMAIL PROTECTED]
> Subject: NetScreen XP and NetMeeting
>
>
> Greetings,
>
> As the subject goes, i need to get net meeting to work via
> NetScreen. I
> found a KB
> article(http://support.microsoft.com/default.aspx?scid=kb;en-u
> s;158623) but
> it seems to show, i had to open a whole range of ports. I am
> skeptical about
> that!
>
> e.g..
> Pass through primary TCP connections on ports 522, 389, 1503,
> 1720 and 1731.
> Pass through secondary UDP connections on dynamically assigned ports
> (1024-65535).
>
> the above shows a whole range of ports that i have to open.
> Is there a work
> around.
>
> Kind Regards
> Gill
>
