I do not think it is possible to successfully enable all the features of Microsoft Netmeeting w/o completely disabling any firewalling features - as it requires "dynamically assigned" ports, (several of them), in the range of 1024 - 65536 I have -NOT- been able to get it to work, without "hot-wiring" around the gateway (i.e. the computer doing the netmeeting call is connected directly to my cable modem...) Jim p.s. The following extract is taken from the April 2001 Microsoft Technet CD set. ==================================== Establishing a NetMeeting Connection with a Firewall When you use NetMeeting to call other users over the Internet, several IP ports are required to establish the outbound connection. The following table shows the ports, their functions, and the resulting connection. Port Function Outbound Connection 389 Internet Locator Service (ILS) TCP 522 User Location Service TCP 1503 T.120 TCP 1720 H.323 call setup TCP 1731 Audio call control TCP Dynamic H.323 call control TCP Dynamic H.323 streaming Real-Time Transfer Protocol (RTP) over UDP If you use a firewall to connect to the Internet, it must be configured so that the IP ports are not blocked. 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). The H.323 call setup protocol dynamically negotiates a TCP port for use by the H.323 call control protocol. Also, both the audio call control protocol and the H.323 call setup protocol dynamically negotiate UDP ports for use by the H.323 streaming protocol, called the Real-Time Transfer Protocol (RTP). In NetMeeting, two UDP ports are determined on each side of the firewall for audio and video streaming, for a total of four ports for inbound and outbound audio and video. These dynamically negotiated ports are selected arbitrarily from all ports that can be assigned dynamically. NetMeeting directory services requires port 389. Microsoft Internet Locator Service (ILS) servers, which support the Lightweight Directory Access Protocol (LDAP) for NetMeeting, also require port 389. =========================================== Gavin Delaney wrote: > How the heck do I get netmeeting working properly? I have no idea what > ports > to be using and the m$ info is no help. > > Thx. > Gavin > ============================================================ Half.com is the Smartest Place to Buy & Sell your CDs, DVDs Books, & Games! Get killer deals on over 10 million items priced up to 50-90% off. Plus get $5 off your 1st purchase. http://click.topica.com/caaacuMbz8Rp2bAfyICf/half ============================================================ -- Visit http://www.ShareTheNet.com for info about ShareTheNet Visit http://www.topica.com/lists/sharethenet for info about this list To Unsubscribe send email to: [EMAIL PROTECTED] ==^================================================================ EASY UNSUBSCRIBE click here: http://topica.com/u/?bz8Rp2.bAfyIC Or send an email To: [EMAIL PROTECTED] This email was sent to: [email protected] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
