Off-topic Talk Where overpaid, underworked S2000 owners waste the worst part of their days before the drive home. This forum is for general chit chat and discussions not covered by the other off-topic forums.

Computer Help: Netmeeting and firewall!

Thread Tools
 
Old Jan 8, 2002 | 01:04 PM
  #1  
brandonb's Avatar
Thread Starter
Registered User
 
Joined: May 2001
Posts: 788
Likes: 0
From: Norman / Tulsa
Default Computer Help: Netmeeting and firewall!

Ok, I'm trying to recieve video with netmeeting. I have XP. I have a Linksys Router(hardware firewall) connected to my cable mode. I guess you cant recieve video on netmeeting with a firewall. So I have two questions, do any of you know a way around this? If not, what do I need to do to connect my cable modem directly to my computer(temporary)? I know how to physically do it, but I am not sure what setting I need to change. I tried it once, I had no connection so I know you must change some settings.
Thanks,
-Brandon
Reply
Old Jan 8, 2002 | 01:23 PM
  #2  
ltweintz's Avatar
Registered User
 
Joined: Jun 2001
Posts: 18,759
Likes: 0
From: Wheeler Army Airfield, HI
Default

You need to find out what port that netmeeting is using and open the port up in the linksys box. By default most of the ports are shutdown. I think there are also specific requirements about the DHCP settings in correlation to open ports in that specific box, but I can't remember if DHCP has to be enabled or disabled.
Reply
Old Jan 8, 2002 | 01:52 PM
  #3  
brandonb's Avatar
Thread Starter
Registered User
 
Joined: May 2001
Posts: 788
Likes: 0
From: Norman / Tulsa
Default

[QUOTE]Originally posted by ltweintz
[B]You need to find out what port that netmeeting is using and open the port up in the linksys box.
Reply
Old Jan 8, 2002 | 02:01 PM
  #4  
krazik's Avatar
Administrator
25 Year Member
Liked
Loved
 
Joined: Oct 2000
Posts: 17,004
Likes: 7
From: Santa Cruz, CA, US
Default

I suspect the netmeeting protocol doesn't work w/ NAT (Network Address Translation). Contact linksys, they should be able to help.
Reply
Old Jan 8, 2002 | 02:14 PM
  #5  
ltweintz's Avatar
Registered User
 
Joined: Jun 2001
Posts: 18,759
Likes: 0
From: Wheeler Army Airfield, HI
Default

Originally posted by brandonb


Do you know where I find this out and how to access the router setting from my computer?
Thanks,
-Brandon
I would look into the netmeeting documentation to find out the port number. It may also be configurable within Netmeeting and the setup area may provide your information.

Do you still have the setup sheet? It shows you how to access the configuration screen of the lynksys box. I belive the IP that the lynksys uses is 192.168.1.1 You will want to enter that IP into your browser. The default user name and password is "admin". In the user manula it tells you how to open up the ports.

BTW - I believe Lynksys has PDF files of their manuals if you don't have yours.
Reply
Old Jan 8, 2002 | 02:19 PM
  #6  
ltweintz's Avatar
Registered User
 
Joined: Jun 2001
Posts: 18,759
Likes: 0
From: Wheeler Army Airfield, HI
Default

[QUOTE]Originally posted by krazik
[B]I suspect the netmeeting protocol doesn't work w/ NAT (Network Address Translation).
Reply
Old Jan 9, 2002 | 01:19 AM
  #7  
brandonb's Avatar
Thread Starter
Registered User
 
Joined: May 2001
Posts: 788
Likes: 0
From: Norman / Tulsa
Default

I found this and tried it, but I am not sure if I did it properly. Could you explain how?

"When you use NetMeeting to establish a connection over the Internet, NetMeeting uses several IP ports to communicate with other meeting participants. If you use a firewall to connect to the Internet, the firewall must be configured so that the ports used by NetMeeting are not blocked.

NetMeeting uses the following Internet Protocol (IP) ports:

Port Purpose
-------------------------------------
389 Internet Locator Server [Transmission Control Protocol (TCP)]
522 User Location Server (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 [Realtime Transport Protocol (RTP) over User Datagram Protocol (UDP)]
To establish outbound NetMeeting connections through a firewall, the firewall must be configured to do the following:
Pass through primary TCP connections on ports 522, 389, 1503, 1720 and 1731.


Pass through secondary UDP connections on dynamically assigned ports (1024-65535).


NOTE : Some firewalls are capable of passing through TCP connections on specific ports, but are not capable of passing through secondary UDP connections on dynamically assigned ports. When you establish NetMeeting connections through these firewalls, you are unable to use the audio features of NetMeeting.

In addition, some firewalls are capable of passing through TCP connections on specific ports and secondary UDP connections on dynamically assigned ports, but are not capable of virtualizing an arbitrary number of internal IP addresses, or are not capable of doing so dynamically. With these firewalls, you are able to establish NetMeeting connections from computers inside the firewall to computers outside the firewall and you are able to use the audio features of NetMeeting, but you are unable to establish connections from computers outside the firewall to computers inside the firewall.

The H.323 call setup protocol (over port 1720) dynamically negotiates a TCP port for use by the H.323 call control protocol. Also, both the audio call control protocol (over port 1731) and the H.323 call setup protocol (over port 1720) dynamically negotiate User Datagram Protocol (UDP) ports for use by the H.323 streaming protocol, called the real time protocol (RTP). In NetMeeting, two ports are determined on each side of the firewall for audio and video streaming. These dynamically negotiated ports are selected arbitrarily from all ports that can be assigned dynamically.

NetMeeting directory services require either port 389 or port 522, depending on the type of server you are using. Internet Locator Servers (ILSs), which support the lightweight directory access protocol (LDAP) for NetMeeting 2.0 or later, require port 389. User Location Servers (ULSs), developed for NetMeeting 1.0, require port 522. "

THanks,
-Brandon
Reply
Old Jan 9, 2002 | 08:21 AM
  #8  
Stealthy_S2K's Avatar
Registered User
20 Year Member
 
Joined: Nov 2000
Posts: 763
Likes: 0
From: Ann Arbor
Default

I have linksys router and Windows XP.

Here is the steps you need to make your netmeeting work. But, only yours. If anyone behind the router uses NetMeeting, they will not be able to recieve anything from outside.

1. make sure you have the latest version firmware for your linksys router. (1.40 if you have an very old linksys router like mine).

2. here are two ways.
simple way,
when you need to use NetMeeting, turn on DMZ and put your computer IP address in it. When you are done with NetMeeting, disable DMZ. and, you are protected again.

the hardway, (I figure out how it works yet).
In advance ---> Forwarding setup screen, you will realize there is a new button called Port Triggering. Click that. Put Netmeeting as one of the application name. and fill out the incoming port range and trigger port range. Now, your router will be able to recieve calls from outside.
(I think you need to put trigger port range as 389-1731, incoming range as 1024-65535)

If the hardway don't help, you can always to go DMZ mode to get it working.

Hope this will help.
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
ProV1
Off-topic Talk
5
Apr 13, 2005 12:08 AM
VTEC_Junkie
Off-topic Talk
5
Mar 11, 2004 07:48 AM
-S2K-2K-
Off-topic Talk
6
Dec 8, 2003 04:28 AM
iLikeBeer
Off-topic Talk
16
Aug 30, 2002 03:23 PM
redleader
Off-topic Talk
5
Aug 26, 2002 04:42 PM




All times are GMT -8. The time now is 01:08 PM.