OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Stephen Burns (sburnsWAVE3COM.COM)
Date: Wed Apr 04 2001 - 17:16:31 CDT

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

    I don't have a lot of experience with this, but I do know a couple of
    things. Last time I checked, NetMeeting (this would be 2.0) uses H.323 for
    it's streaming capabilities. So if you are wondering how you are going to
    allow this in through a NAT scheme, you may not be able to. I know that
    most NAT implementations were boasting the "H.323 support soon" thing, so I
    might be out of date on my observations. If you arent attempting to do
    address translations, and you're just wondering, then yes you're right
    regarding the ports. 

    --
Stephen C Burns
MCSE, CCNA
Network Administrator
sburnswave3com.com
--

    -----Original Message-----
From: Focus on Microsoft Mailing List
[mailto:FOCUS-MSSECURITYFOCUS.COM]On Behalf Of Bill Walsh
Sent: Wednesday, April 04, 2001 4:03 PM
To: FOCUS-MSSECURITYFOCUS.COM
Subject: 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