Yes, that was what I meant. I guess the first step is to make a connection
to an outside NM system that is known to be working properly. (I am
assuming that you can make the connection, but no audio or video) and do a
netstat (open DOS box and type netstat -a :) to see what ports/connections
are made/not made. Do again just to make sure the same thing
happens.....what connections are made??? Where to go from there depends on
the results.
Paul Eftis
-----Original Message-----
From: Michiel van der Linden <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
<[EMAIL PROTECTED]>
Date: Monday, August 23, 1999 6:02 AM
Subject: Re: [NetMeeting] MS proxy server settings for Netmeeting
>
>I'm not sure what you mean by "opened": I have added subsequent connections
>for UDP, port range 0-65535 for all protocols concerning Netmeeting, is
that
>what you mean?
>
>>
>>Do have the UDP ports opened?? That would be my only other thought on the
>>issue. If yes, then a step by step would have to be done......i.e. can we
>>establish an outbound connection on TCP port whatever....(telnet is a
handy
>>cheap and dirty tool to do this type of testing)
>>
>>Paul Eftis
>>
>>-----Original Message-----
>>From: Michiel van der Linden <[EMAIL PROTECTED]>
>>To: [EMAIL PROTECTED]
>><[EMAIL PROTECTED]>
>>Date: Friday, August 20, 1999 7:50 AM
>>Subject: RE: [NetMeeting] MS proxy server settings for Netmeeting
>>
>>
>> >
>> >Thanks for your reply Paul. It was more reply than I had hoped for ;-).
I
>> >have added TCP outbound port range 1024-65535 as subsequent connection
>>for
>> >the 1720 protocol I added earlier. However still no audio and video.
>> >
>> >I also added this same TCP portrange inbound, also as subsequent
>>connection
>> >of the 1720 protocol, however i'm not online for the outer world. Am I
>> >misinterpreting your suggestions, or could something else be wrong?
>> >
>> >Regards, Michiel
>> >
>> >
>> >
>> >>From: Paul Eftis <[EMAIL PROTECTED]>
>> >>Reply-To: [EMAIL PROTECTED]
>> >>To: "'[EMAIL PROTECTED]'"
>> >><[EMAIL PROTECTED]>
>> >>Subject: RE: [NetMeeting] MS proxy server settings for Netmeeting
>> >>Date: Wed, 18 Aug 1999 14:36:28 -0400
>> >>
>> >>You also have to open TCP ports 1024-65535 Outbound (Dynamic) for the
>> >>negotiated H.323 Call Control (done as part of the negotiation over
port
>> >>1720). Although I have seen many concerned thoughts about this aspect
>>of
>> >>H.323, that it is a "huge security hole", it is not really an issue the
>>way
>> >>you have it setup (which is the way I recommend) since the ports are
>>only
>> >>opened for calls/packets initiated from within the network, which does
>>not
>> >>open you up to external packets being passed into the network (i.e. you
>> >>have it setup with reflexive access control).
>> >>
>> >>I would like to also add a second point concerning the H.323 security
>> >>issue:
>> >>Even if you opened up TCP ports 1024-65535 Inbound to receive inbound
NM
>> >>calls,
>> >
>> >
>> >______________________________________________________
>> >Get Your Private, Free Email at http://www.hotmail.com
>> >-----------------------------------------------------------------------
>> >http://www.meetingbywire.com/Mailinglist.htm for unsubscribe information
>> >-----------------------------------------------------------------------
>>
>>-----------------------------------------------------------------------
>>http://www.meetingbywire.com/Mailinglist.htm for unsubscribe information
>>-----------------------------------------------------------------------
>>
>
>
>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com
>-----------------------------------------------------------------------
>http://www.meetingbywire.com/Mailinglist.htm for unsubscribe information
>-----------------------------------------------------------------------
-----------------------------------------------------------------------
http://www.meetingbywire.com/Mailinglist.htm for unsubscribe information
-----------------------------------------------------------------------
