 | Actiontec 701 Port Forwarding I've been trying for several weeks now to get some ports to forward on my Actiontec GT701-WG, specifically ports 2300-2310 for some streaming music and remote control apps.
Well, I go into the config, and put these ports into port forwarding on both TCP and UDB, and put my machine in the DMZ, and it still won't work. I took down my software firewall, which was already configured for these ports, and a port scan showed all TCP ports open.
So why isn't this working? Can anyone lend me a hand?
Qwest is my ISP BTW. |
|
 | Is there a firewall running on the system you are using? |
|
 | reply to dumberdrummer Yes. I've tried it with it down and with it up and configured to allow those ports. |
|
 | reply to dumberdrummer I don't have it in front of me but there are 2 places to add for port forwarding in the advanced configuration, make sure those are set. -- Out the 100Base-T, through the router, down the T1's, over the leased line, off the bridge, past the firewall... nothing but Net. |
|
 | reply to dumberdrummer All settings are correct in both port forwarding and advanced port forwarding. |
|
 | reply to dumberdrummer Try it without setting the machine in the DMZ, that is how mine is setup, I forward to the IP, but I don't put it in the DMZ. |
|
 | reply to dumberdrummer No dice.
 |
|
 RevMortisI Hear Dead SiliconPremium join:2005-05-10 Saint Paul, MN | reply to dumberdrummer I'm now on a 701WG. The first modem I had was a 1524. It had hangups with port forwarding. I never got a connection through from the outside unless I did DMZ. Nothing. Zip Zilch Nada. When it had the infamous critical failure with 100b channel and Qwest replaced it, I became happy very quickly.... >8)
I suspect its a bum chip on the Actiontec products. Try an RMA. |
|
|
|
 | reply to dumberdrummer Alright I will do that. Thank you both. |
|
 msjPremium join:2004-05-21 Fort Collins, CO kudos:1 | reply to RevMortis said by RevMortis:I suspect its a bum chip on the Actiontec products. Try an RMA. Bum chip? Not unless you are seeing all kinds of other intermittent failures. There isn't a "port forwarding" chip that can go bad. Just about everything is handled by software running on the AR7 cpu. If the AR7 is faulty you will see all kinds of intermittent problems, not just a problem with setting up port forwarding. Most likely if the AR7 is bad (or overheats, which has been known to happen with the Actiontec modems) the modem will just lock up.
Configuring the actiontec can be somewhat finicky. It seems that sometimes when you only try to change a particular parameter the actiontec winds up setting other parameters back to default. This can be avoided by going through all the pages again to make sure that they are set the way you want.
You don't want to use the DMZ feature and the port forwarding feature for the same machine. That makes no sense. Putting a machine in the "DMZ" basically says forward EVERY port that isn't already being forwarded somewhere else to the DMZ machine. Its kind of like a default route for ports.
Also, port forwarding won't work real well if you are having the actiontec assign you a dynamic IP address. You may wind up forwarding ports for the IP address you currently have and then the actiontec might assign you a different IP address later. So, if you are going to do port forwarding you either need to turn off dhcp, or you need to restrict the range of IP addresses that dhcp can use so that you have some addresses to use for static assignment. Any machine that is going to have ports forwarded to it (or put in the DMZ) should have a statically assigned IP address.
After you "Save and Restart", go back to the port forwarding page and make sure the ports you set up for forwarding are listed in the "List of Forwarded Ports" window.
So, give us more details about your configuration. In particular, click on the following links in order from the Main Menu page:
1) Setup / Configuration 2) Advanced Setup 3) Begin Advanced Setup 4) Port Forwarding
And then tell us exactly what is listed in the "List of Forwarded Ports" box. If you set it up according to what you mentioned in your first post you should see something like this in the box:
2300-2310 tcp 192.168.0.2 2300-2310 udp 192.168.0.2
Where 192.168.0.2 is the static address you assigned to your machine. |
|
 | this is my problem as well.
i log into the modem 1) Setup / Configuration 2) Advanced Setup 3) Begin Advanced Setup 4) Port Forwarding.
i fill out IP Port Range Protocol IP Address #### to #### udp/tcp Internal IP#
Yet it does not forward. so i click advanced. And i fill out
Remote IP Port Range Remote IP Address #### #### anyIP
Using the above #### as the same port number, [I only want 1 port forwarded], Why would there be no connectivity in the forwarding?
thanks |
|
 msjPremium join:2004-05-21 Fort Collins, CO kudos:1 | You don't want the advanced forwarding, so don't go to that page. Have you clicked "save and restart" after entering the port forwarding information? Did you check to make sure that the port forwarding was still showing up in the "List of Forwarded Ports"? |
|
 | ok, so i'll remove the advanced information. and yes the basic information was still showing in "List of Forwarded Ports". |
|
 msjPremium join:2004-05-21 Fort Collins, CO kudos:1 | What kind of machine are you forwarding the port to? If its Windows XP, do you have Windows Firewall enabled (its on by default starting with SP2). You need to open the port in the Windows Firewall also.
You can check to see whether or not the port is being forwarded by the modem, but it's a little involved. Do you know how to telnet into the modem? If so, do you know how to capture (cut and paste for example) output for commands you type in? I'd like to see the output from typing "iptables -v -L" and "iptables -t nat -v -L". If you don't know how to do this, here are some more specific instructions for windows:
1) Start a cmd prompt window by clicking on "run" from the start menu. Then type "cmd" in the box and click OK.
2) Type "telnet 192.168.0.1" (use the internal IP address of your modem). Login using user name "admin" and password "admin" (the password will be different if you've changed the web admin password).
3) Then type "iptables -v -L" and then type "iptables -t nat -v -L" (hitting return after each command).
Now you need to cut and paste the output from the cmd prompt window. To do this:
1) Right Click on the title bar and click on properties. On the options tab make sure that "Insert Mode" is checked and "Quick Edit Mode" is not checked under "Edit Options".
2) Scroll back the cmd prompt window using the scroll bar until you can see the start of where the iptables output begins. Right click within the window and click on "Mark". Then left click and select the text starting at the first character and dragging down to the bottom right. Holding the mouse near the bottom of the window will cause the window to scroll automatically down to the bottom so you can select all the text in one operation.
3) The text should all be inverted now (by default it will be black text on white background). Hit return within the window and the text will no longer be selected but it will now be in the windows copy buffer.
4) start notepad and click on "paste" under the "edit" menu bar. Save the file.
5) Attach the file here so that we can hopefully diagnose the problem.
It would also be helpful to know 1) the internal IP address of your modem (by default it's 192.168.0.1), 2) the internal address of the machine you are trying to forward the port to, and 3) the port number you are trying to forward. |
|
 msjPremium join:2004-05-21 Fort Collins, CO kudos:1 | reply to dumberdrummer One of the other topics reminded me that there is also a "firewall" configuration option. Make sure that that is set to "off". You should only use the other settings if you have a block of static IPs that are forwarded to other machines. Turning this on can interfere with port forwarding.
They really shouldn't have called that setting "off". It should be labeled "NAT only" or something like that. "Off" makes it sound like you have no protection, which is completely wrong. Since most people have only private NAT'ed IP's behind the router ALL ports are blocked by default by the very nature of NAT. You have to explicitly forward ports for any inbound connections to work. |
|
 wd4075 join:2004-06-21 Nampa, ID | reply to dumberdrummer I go here »www.canyouseeme.org/ whenever I setup port forwarding to see if it's working or not. -- Visit »www.spazmatic.net for more DSL information. |
|
 msjPremium join:2004-05-21 Fort Collins, CO kudos:1 | Another option is to use "Shields Up!" at www.grc.com. It has the advantage of being able to scan ranges of ports, including a single button to scan all ports in the 1-1024 range. |
|
 | I'm in exactly the same boat. I've been fighting with port forwarding not working on multiple Actiontec modems all day at various locations. That link »www.canyouseeme.org/ would have been very helpful. I've narrowed the problem down to the Actiontec routers themselves. There has gotta be something I'm doing wrong but I've tried all the suggestions above to no avail. I'll be interested to hear the results on the iptables... If I can be of any assistance in tracking this issue down, by all means please let me know as I have about 3-4 Actiontec DSL modems I may just replace over this if the issue cannot be resolved. |
|
 msjPremium join:2004-05-21 Fort Collins, CO kudos:1 | Perhaps there is a common configuration problem that people are getting wrong. So, rather than try to go back and forth trying to figure it out, how about you send me your entire configuration and I'll figure out what you are doing wrong?
Here's how you can do this:
1) First, make sure you are running the latest Actiontec firmware. To check the version click on "status" from the Actiontec main page. Make sure the Firmware version is:
QW04-3.60.2.0.6.3-GT701-WG
If not, please upgrade your firmware. This most likely will not fix your problem, but your firmware needs to be compatible with mine, otherwise the rest of these instructions won't work. Go to this web page to get the latest firmware:
»www.qwest.com/dslhelp/modems/gt7···firmware
2. From the main menu click on "Setup/Configuration". Then click on "Alternate Setup". Record your username and password in case you don't have it written anywhere else. Now change both the username and password to "XXXX". Click on "Save and Restart" at the bottom. THIS WILL BREAK YOUR CONNECTION. The whole purpose of this step is to obscure your username and password so that you won't be sending it to me or anyone else. You will restore the username and password later. Meanwhile your internet connection will be down.
3. telnet to your modem (You can use a command prompt window to do this by typing "cmd" in the run box from the Windows start menu). In the command prompt window type "telnet 192.168.0.1" (substitute the IP address of your modem if it is different).
4. Log into the modem with account "admin" and password "admin".
5. Type the following commands:
cat /dev/mtdblock/4 >/var/mtd4 thttpd -d /var -p 1080 exit 6. Now from your web browser enter the following link (again substitute the IP address of your modem if it is not the default):
http://192.168.0.1:1080/mtd4 save the file to disk.
7. Now you can restore your connection by following step 2, but replace the "XXXX" with your real username and password. Once you restart your connection should come back up. You can monitor the status page to make sure you didn't type something incorrectly.
8. Give me access to the file. This file will contain the full xml configuration of your modem (which is why you want to obscure your account information). Either 1) place the file somewhere that I can get to it and post a link here, 2) attach the file here (not sure if non picture attachments work or not), or 3) attach it to an email and mail it to msjdsl@yahoo.com (note that this is a temporary email account that will go away eventually -- posting email addresses to public forums is a guaranteed way of getting lots of spam, and the spammer email harvesters are getting smarter about obscuring techniques).
If you do the above I can take that configuration file and install it on my modem, which will allow me to debug the problem you are having. If I can't reproduce the problem, i.e. the port forwarding works without me changing anything (other than replacing the XXXX with my username and password), that would indicate that the problem is not the Actiontec configuration but is caused by something else (port blocked by your ISP, another router between the modem and your machine, a software firewall on your machine, including Windows XP firewall, etc.)
Please note that I am not necessarily going to do this for every person who asks in the future. I am hoping that there are some common problems that people are having with this feature, and that by doing this once or twice I will be able to determine what they are so it will be easier for everyone to help others get port forwarding to work. |
|
 | reply to dumberdrummer Did anyone find an answer to this problem? |
|