OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: .sozni (sozniXATO.NET)
Date: Thu Apr 05 2001 - 01:25:19 CDT

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

    These KB's might be helpful:
    Q281078 - XCCC: Unable to Receive Other H.323 Participants' Audio or Video
    Through a Packet or Port Filter Device
    Q158623 - How to Establish NetMeeting Connections Through a Firewall
    Q187596 - INFO: Port Number Allocation When Passing over TCP/IP
    Q281078 - XCCC: Unable to Receive Other H.323 Participants' Audio or Video
    Through a Packet or Port Filter Device

    Essentially, you will need T.120 (TCP 1503) for application sharing. You
    will also probably need ULS (TCP 522), the User Locater Service unless you
    are using Exchange Server to locate users.

    But you should carefully consider the security implications of using the
    T.120 protocol. You may want to check out this site:
    http://www.shenton.org/~chris/nasa-hq/netmeeting/

    .sozni

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