How to know if port forwarding is working?

i have 2 routers one netgear and the other linksys W4tg45 and i have port forwarding the same on both. now when i connect the netgear i am able to access the website from outside the LAN and when i connect the linksys it is not working anymore. is there a way to do diagnostics on the linksys to see that the port forwarding is working fine? charbel

Try to update firmware on linksys router, that might make it work. You can download latest version from www.linksys.com/download

Similar Messages

Port forwarding stops working several hours after reset

I have a WRT350N (fw v. 1.03.2). It's connected to an Alcatel ADSL modem (PPPoE configuration). I've configured port forwarding to allow HTTP and SSH into a linux box on my home network (static IP). I am able to get to the linux box from outside for the first few hours after I set up the configuration, but a few hours later I am no longer able to get to it from outside - port forwarding stops working though the settings remain as I'd left them. Over the course of various attempts I've had the external connections just die (404 errors, host not found, etc) and sometimes the connection went to the router - getting the WRT350N login prompt (remote management is turned on, but on port 8080, not 80, so this was unexpected).
The only way I've found to resolve this is to reset to factory defaults and reconfigure. Then it works again for a few hours and shortly is again not forwarding. I've tried other ports (VNC, RDC, telnet, SMTP) and the forwarding stops working on all ports at the same time. My home machines are able to get out to the internet with no problems.
I thought the router had a hardware flaw so i replaced it with an identical model yesterday, and sure enough, today I'm again stuck without external access to my home website.
Any thoughts or suggestions would be welcome.
Thanks,
Nick

I was able to trace the problem to torrent downloads. It seems the router wasn't handling all the concurrent connections when handling torrents. I haven't had problems since i stopped downloading torrent files. I did add a static port mapping and configured utorrent to run on a single port on a machine with a static address but haven't had cause to download any torrent files since then, so i don't know if that will fix the problem.
That being said, i've had no issues since i stopped the torrents.
HTH
Nick

Port Forwarding not working after 7.7.1 Firmware update

I bought the new 6th generation Airport Extreme today, and after I set it up, everything worked great. I have a VoIP phone that needs to have traffic on port 5060 forwarded to it, and that worked just fine as well.
However, I then updated to the 7.7.1 firmware, and the port forwarding stopped working. I tried a hard reset of the Airport and re-entered all the settings, but it still didn't work. I spent about 30 minutes on the phone with 2 Apple support people who tried hard, but couldn't help. They also couldn't find a way to download the 7.7 firmware, so there was no way to downgrade. They suggested I go back to the store and exchange it for another one, which I did, and now it all works again.
Has anyone else had issues with port forwarding on 7.7.1? I'm just wondering how I'll ever be able to update the firmware, since failure means having to get a new Airport.

Huh,
turns out the problem went away with another restart of the Mac Mini. I'm still uneasy about it though, as I do not understand how it went from working to not-working over night in the first place. But, at least for now, the problem seems gone.
Thanks for commenting.
Cheers
Niels Olof

How to set up port forwarding on extreme with NAS

I've purchased a NAS (Synology DS211j with 2 caviar HD) over a month ago. Setting up the NAS for wireless connection locally was easy. I've been trying for 3 weeks on how to set-up port forwarding on my airport extreme base. I''ve researched and read countless threads on port forwarding and still cannot grasp the concept and the step by step provided. I need somebody that's patient enough to hand hold and guide me through this frustrating problem.
Equipment:
Comcast cable modem connected into Airport Extreme Base
Synology DS211j connected to Airport Extreme Base
Problem:
Cannot connect to my DiskStation via internet from wherever
confused whether to use FTP or Personal file sharing or whatever is the most suitable for my needs
Just need to access files on my DiskStation view/upload/download from wherever I'm at, whether on PC or Macbook Pro
Thanks in advance!
Marcus

Here are the basic steps to configure your NAS for port mapping:
AEBSn - Port Mapping Setup
To setup port mapping on an 802.11n AirPort Extreme Base Station (AEBSn), either connect to the AEBSn's wireless network or temporarily connect directly, using an Ethernet cable, to one of the LAN port of the AEBSn, and then use the AirPort Utility, in Manual Setup, to make these settings:
1. Reserve a DHCP-provided IP address for the host device.
AirPort Utility > Select the AEBSn > Manual Setup > Internet > DHCP tab
On the DHCP tab, click the "+" (Add) button to enter DHCP Reservations.
Description: <enter the desired description of the host device>
Reserve address by: MAC Address
Click Continue.
MAC Address: <enter the MAC (what Apple calls Ethernet ID if you are using wired or AirPort ID if wireless) hardware address of the host computer>
IPv4 Address: <enter the desired IP address>
Click Done.
2. Setup Port Mapping on the AEBSn.
AirPort Utility > Select the AEBSn > Manual Setup >Advanced > Port Mapping tab
Click the "+" (Add) button
Service: <choose the appropriate service from the Service pop-up menu>
Public UDP Port(s): <enter the appropriate UDP port values>
Public TCP Port(s): <enter the appropriate TCP port values>
Private IP Address: <enter the IP address of the host server>
Private UDP Port(s): <enter the same as Public UDP Ports or your choice>
Private TCP Port(s): <enter the same as Public TCP Ports or your choice>
Click "Continue"
(ref: "Well Known" TCP and UDP ports used by Apple software products)

Port forward stopped working after update

i updated my software and the port forward stopped working and it will no longer allow access to my ip camera.

Hey Cab,
Yea, mine stopped working since the update to 10.8.2. It was working fine prior to the update cause I used it at work on a 50 inch Samsung. I undrstand that there was a driver update but I'm not sure why.

E2000 Port Forwarding Stops Working

I am using port forwarding for running a webserver. All is working fine. After a random number of hours or days, the port forwarding stops working. I can get in and look at the settings and they are correct. I can then change something on the port forwarding screen and resave it and it starts working again. Do I have a bad unit ?

Webserver might not be set to static IP. Try setting the webserver to static IP first, then make sure that static IP is enabled in the Port Forwarding screen of the router's web-based setup page. Also, protocol should be set to BOTH (TCP-UDP). You can also try having less firewall/AV restrictions on the web server (or none at all) and set MTU to 1400.

Airport Express G getting Port Forwarding to work from Airport Extreme N

I have an Airport Extreme N connected to a cable modem. I have an Airport Express G in another room, connected to a Local Ethernet Network. The AE G is setup as a WDS Remote to the AE N. Connectivity works and all is well.
What doesn't work is when I try to forward ports from the AE N to a device/system connected (via ethernet) to the AE G. The kicker is the port forwards work from "inside" the network. Outside they don't. I have been able to forward ports to anything connected to the N directly or wirelessly.
Any thoughts on what the proper configuration of the AE G or the AE N to get port forwarding to work from the AE N through to the clients of the AE G?
I have DHCP, and the clients of the AE G are getting IP addresses and working as they should.

I checked that. I can forward ports all day long to anything connected directly (or wirelessly) to the AE N. Anything connected to the AE G, ports won't forward. For some reason the AE G in bridge mode is not letting ports forward through.
Thanks for responding, though.

How to know which port is being used by which process

Hi,
Could you please tell me how to know which port is being used by which process.as iam getting ports are already in use.
Thank you,
Sravan
Message was edited by:
sravan123

Your OS might provide a command to support this question like '"netstat".
Besides, on Unix the pseudo-file system /proc is also useful.

RV215W router port forwarding not working

RV215W router port forwarding not working.
Port forwarding works for a short period of time, then stops working. Reboot router, works again for short period of time, then stops again.
I have updated firmware to latest. I had seen other similar bugs posted for 220 and I think 180, not sure if this router has similar bugs and waiting for fix release to firmware.
I had recently purchased two, one deployed, will hold off on other now because of issues, and may have to move to different unit if a resolution not found this week.
Dave Gritten
IT Director
Maritime Beauty
3695 Barrington St
Halifax NS B3K 2Y3
cell 902.223.9685
phone 902.429.8510 ext231
fax 902.422.7983
[email protected]
www.MaritimeBeauty.com

It's not just single port forwarding that has bugs, the entire router has bugs and simply does not work as advertised. I have found the following bugs/aspects of this router that just does not work correctly: 1. If you have to open ports, and who doesn’t, this router will eventually stop accepting packets from WAN>LAN. You will still have Internet access but no open ports. A reboot will fix this problem. Oh, by the way, this router has no scheduled reboot option! <--That would be a workaround but a welcome one for this router. 2. Firewall Access rules do not work!! Yep, a Cisco router and basic functionality simply does not work. I called Cisco and even though the tech saw the router not working denied it was a bug! Said we have to do port mirroring, setup a workstation with WireShark and capture packets so we can debug the issues. That would take several hours. I told him I would have appreciated if Cisco would have debugged the issues with their router BEFORE they shipped the units. Stay away from Cisco Small Business Routers. I wish I had. And if there are any Cisco die-hards out there willing to prove me wrong, just reply to this and please, prove me wrong that the RV series and specifically the RV215W is not JUNK.

How can I setup port forwarding for RDP (3389) using MHS291LVW?

Hi,
I went into my MHS291LVW and I enabled port forwarding. I didn't see an option for Remote Desktop (RDP) so I added a custom application called RDP and I set "Global Port" and "Private Port" to port number 3389 and I set it as TCP/UDP and then entered the local IP (192.168.1.135) of the PC I want to connect to. I made my local PC use a static IP so this 192.168.1.135 will never change.
Then when I go under "About Jetpack" I see that there is a WAN IP address listed; so I wrote this down and then I tried to connect remotely to this PC from outside the Verizon Jetpack network but it didn't work.
Then the strange thing is when I go to Google and type "what's my IP", Google shows me a different external WAN IP address that Verizon Jetpack showed me in the admin web interface. Anyway, I tried this WAN IP address that Google gave me but it still didn't connect to my local PC.
Can someone please help me in figuring out why this is not working?
I've setup port forwarding on plenty of other routers (Linksys, Netgear, etc.), but I never tried it on a Verizon Jetpack MHS291LVW but it should work the same so I'm not sure why this is not working for me.
Thank you!

> If I can't use the "Microsoft Windows RDP" service because of the private IP; would I be able to use a software like "TeamViewer" to gain access to my PC?
Yes. This is how a VPN server works around the private IP address restrictions of the VZW network. It will work and you will be able to access anything that is centrally connected to a VPN server.
> Also, if I were to take the VPN option and setup a VPN server on the PC
Not on the remote PC silly guy. Hosting a VPN from within the VZW network wont do you any good as its IP will be masked by the NAT firewall. You must setup a VPN server off of the VZW network for it to work. That way when you remote into the VPN server it is already outside of the VZW NAT that is restricting you in the first place. There are many VPN vendors that you can test out and pay access for if you don't have any interest in setting up one on your own. Some are free where others charge more money for more bandwidth and customization features.
> If I were to try to connect to this PC on the JetPack side from an external PC on a different network I don't know how I would be able to access it since the JetPack IP address is private.
The idea is that everything rests on the VPN server when remote connections are made. The Jetpack PC, VPN Server and your current local PC all connect to the VPN server so everything is then local communication. The VPN will make it appear as though everything is virtually connected to the same appliance even though they are physically separated by whatever distance you want.

How do I do port forwarding on my airport extreme for my IP camera (foscam)?

Hi,
I've been working on this for what seems like a week. I purchased a wireless security camera to put in my house and to see from my laptop (or IPAD2) when I'm away. I am able to see it from either device when I'm here at home, but not when I'm out on the road.
According to the instructions for a mac setup, I needed to set up a DDNS service and get a free account at DynDNS, which I did. They also told me to use a different port than 80, suggesting 8081 as the http port which I plugged in to the camera device setting.. The next step is to do PORT FORWARDING and then I should be able to use my DDNS domain name and port number to login to my camera anywhere...
I'm stuck in how to do this with my airport extreme. I see where I have to go into utilities and click on airport utility, and then manual set-up..
Right now when I click on the Internet tab at the top I see the connection sharing is off (Bridge Mode), and that I have to change it to share a public IP address to get DHCP and NAT to appear in the tabs..
when I go to NAT, the box for enable NAT port mapping protocol is checked and then there is a tab I can click on that says Configure Port Mapping.
I know that I'm supposed to click the plus button + to enter a service and a port and here's where I get stuck
when I click the + button I can either click on the choose a service tab, which then drops down a list of services like Personal File Sharing, Window Sharing, Personal Web Sharing, Remote Login SSH , etc, or just keep it where it says choose a service and not choose one of the services.
Then there are some boxes to fill in for Public UDP Port(s), Public TCP Port(s), PRIVATE IP address-where the only numbers I can change are the last ones and I don't know if I'm supposed to put the IP address of the camera or what? and then the boxes for Public UDP and PUBLIC TCP.
I tried a few times to fill out the port numbers to 8081 (the one I selected for the IP camera) but I don't know what to do for the private IP address. When I changed the last numbers to the IP address of my camera, and went to update, it told me that I had to correct the 2 problems before updating:
DHCP beginning address, and dhcp ending address...as the DHCP range you have entered conflicts with the WAN IP address of your Airport wireless device. So I cancel and am stuck.
Sorry this is so long.. but I really can't get anyone to help me figure this out.. The camera company isn't answering ..
Thanks!!
Barry

Thanks for the info. I checked the model number on the Westell site to get info on the device. From Westell's info.....
1. Product Description
This ADSL modem is a NAT router with a four port 10/100BaseT Ethernet switch, a USB port and 802.11g wireless interface.
So, while you might refer to it as a "modem" ( a modem will only have one Ethernet port), you have a router or gateway. A gateway is simply a modem and router in the same box.
With the AirPort Extreme, you have 2 routers on the network. Basic networking rules dictate that when there are 2 routers, the first....your Westell.....must handlde DHCP and NAT, and the second router....in this case the AirPort Extreme....must be configured to operate in Bridge Mode so that it will function correctly on the network. That's why the AirPort Extreme is in Bridge Mode. That is the correct setting on your network.
That's also why you were getting the error messages when you tried to configure the Extreme as a second router.
As I mentioned before, any port mapping or port forwarding is going to have to be set up on the "main" router....your Westell. It cannot be set up on the AirPort Extreme.

HH3 Type B port forwarding not working.

Hi there.
I have searched absolutely everywhere for a solution to my problem before posting here. Basically port forwarding isn't working at all on my HH3 Type B router.
I've read all about the problems people have had with the Type A's but as far as I see nobody seems to have a problem with the Type B in regards to port forwarding or loopback.
I've set up port fowarding on many different routers with many different ISP's so I don't think it's something I'm doing, or rather, not doing but you never know.
These are the steps I take when setting up port forwarding:
Firstly setting up my static IP (obviously only needed to be done once) which I've chosen one outside of the routers DHCP range as I've always done in the past. Then I open the router screen, go to Settings / Advanced Settings / Port Forwarding / Supported Applications and click "Add new game or application".
I then enter a name, change "Copy existing game or application" to "No", and then change the "Protocol" to UDP or TCP as needed (also have tried using "Any" too with no luck). Next add a "Port Range" for example 12345 - 12345 then add "Translate To" 12345 - 12345 (port ranges obtained from portforward.com per application) then click "Add" and repeat for additional ports as needed.
Once that is all done, click "Apply" then go to Port Forwarding / Configuration or go to Home Network, select the applicable device and choose the newly added application from the "Port Forwarding" drop down list (and choose applicable device if doing it from Port Forwarding / Configuration). Click "Add" once application is selected.
Add additional applications where needed then finally click "Apply" to store the forwarded ports.
Close router page and port forwarding should be fully setup and working.
That's basically how I would do it anyway, but I also checked on portforward.com and it says pretty much the same and on these forums as well as a few other sites and I see nothing different but port forwarding still isn't working.
In my router "Event Log" it does show "The Port Forwarding entry of [xxx.xxx.x.xx] has been added or modified.".
My Firmware version is V100R001C01B036SP03_L_B. Last updated 19/05/13.
I have no firewall on my pc and the one enabled on the router is set to default but have also tried disabling it. Have tried enabling DMZ as suggested in various places with no luck and have tried changing UPnP settings again with no luck.
So if anybody has any suggestions I am all ears because this is bugging me so much as there are a few applications and games that require port forwarding and are pretty useless without it really.
Thank you.

If you follow the instructions on this page, it should work. Please see note about CG-NAT.
Port forwarding problems
There are some useful help pages here, for BT Broadband customers only, on my personal website.
BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

Ssh Port Forwarding Stopped Working

I have used ssh port forwarding in the past, and it has come in handy.
I have recently upgraded to Mavericks, but it does appear that my ssh port forwarding stopped some time before this. The last time I know it worked was 5/14/14, and feel it has worked more recently as well.
Here's what I do, from my Mac I ssh to my work jump server (port 22, let's say its IP is 11.22.33.44), and my jump server has access to work PC (lets say IP of 10.1.2.3). My work PC has RDP running on it on the common port 3389. I have verified that I can set up a working RDP session at work from another box. Also, I know that my jump server can get to my PC at work as I can ping my work IP if I just ssh straight to my jump server. And I know that there is no firewall stopping me from the jump server as I can also open a telnet session to my work PC on port 3389, without errors.
So, here's how I have done it in the past and it has worked, but now recently stopped working in Terminal app:
ssh -f [email protected] -L 3388:10.1.2.3:3389 -Nnv
The verbose logging shows that it sets up connectivity. If I then look to see if my local port is listening I can type:
netstat -an | grep 127.0
I will note that port 3387 is in fact LISTENing and waiting for connection
I then start my RDP client app, and start a session to "localhost:3387" (I could also use "127.0.0.1:3387", and have, but it does not work either). My RDP client eventually times out. I have turned my firewall off and on, neither way works.
Does anyone know why this may have stopped working?
Your input is most appreciated.
The verbose log shows the following is setup appropriately (with noted modifications to server names and actual IPs):
debug1: Authentication succeeded (keyboard-interactive).
Authenticated to somewhere.net ([11.22.33.44]:22).
debug1: Local connections to localhost:3387 forwarded to remote address 10.1.2.3:3389
debug1: Local forwarding listening on 127.0.0.1 port 3387.

Unfortunately I don't have another device to test if RDP is working on my LAN, however, when I check out my network connections and this is what I see after setting up the ssh tunnel and prior to attempting the RDP connection (again names protected):
my-rmbp:~ me2$ netstat -an | grep 127.0
tcp4       0      0 127.0.0.1.3387         *.*                    LISTEN
Then, as it is difficult to catch in the middle of TCP 3-way handshaking, here's what happens after an attempt with the RDP client while it sits and spins:
my-rmbp:~ me2$ netstat -an | grep 127.0
tcp4       0      0 127.0.0.1.3387         127.0.0.1.50323        FIN_WAIT_2
tcp4       0      0 127.0.0.1.50323        127.0.0.1.3387         CLOSE_WAIT
tcp4       0      0 127.0.0.1.3387         *.*                    LISTEN
You can clearly see it's attempting to make a connection over the tunnel via my RDP client, but it's being shut down right away. I will obtain a WireShark packet capture and see exactly what's happening. Oh, and if I tried to RDP to a port other than the one I set up the port forwarding tunnel with, RDP would disconnect right away.
What I'm most interested in is why, without any known changes, other than OS updates, did this work a few months ago, and now it does not?
I have also tried other test ssh port forwarding, such as to www.apple.com forwarding 8080 on localhost to 80, and others, and none of those work either with web browsers, I assume this is something Apple has done to disable ssh port forwarding/tunneling. Perhaps someone else has bumped into this and found a fix? Please share!
Also, I have heard that you have to be root in order to set up port forwarding, but clearly this is not accurate, as it worked before, and also as you can see above it worked without root. But I tried both ways, and sadly neither worked.
Could it by my jump server? Possibly, but others at work do this and it works just fine for them from their Windoze PCs. So can't be that either.
Perhaps my capture will tell me, I'll report back here with what I discover. Thanks in advance!

WRT110 - still can't get Port forwarding to work

Here's the deal: Vista PC behind WRT110 in PPPOe mode which is behind a successfully bridged AT&T Westell modem/router (but it's not in DMZ mode). I've setup a static IP on my computer and enabled port forwarding to it in the router. Then I test port forwarding and still fail the test. On my Westell modem, it says I can share my (external) static IP with my router. Would that do anything helpful? Can you suggest anything else helpful? Thanks so much!!

Mort wrote:
You can use the Static IP under WRT110 .... using Internet Connection type ....
If the port forwarding is not working then reset & reconfigure the router ...
Thanks for your reply! If my modem is bridged, how do I know what my router's static IP address should be? Would it be the same as the modem?

Port Forwarding not working (PLEASE HELP!)

I have been trying to port forward a Minecraft server for fun, however the port will not open no matter how many times I try. Here's what I've been doing: Enter 192.168.1.1 in browser and log in. Once on the home screen -> advanced -> port forwarding rules -> add port -> tcp -> any source -> single destination: 25565 (default port for a Minecraft server) -> add port -> udp -> any source -> single destination: 25565 -> apply -> fire wall settings -> typical security -> port forwarding -> select my computer I am on -> select the port forward I had previously created -> add -> resolve now & apply. The status shows as active, but when I use a site like checkmyports.net, it states that the port is closed.Is anyone else having port forwarding issues? What's the problem? Did I miss something? Thanks in advance.

KevinC45 wrote:
I have been trying to port forward a Minecraft server for fun, however the port will not open no matter how many times I try. Here's what I've been doing: Enter 192.168.1.1 in browser and log in. Once on the home screen -> advanced -> port forwarding rules -> add port -> tcp -> any source -> single destination: 25565 (default port for a Minecraft server) -> add port -> udp -> any source -> single destination: 25565 -> apply -> fire wall settings -> typical security -> port forwarding -> select my computer I am on -> select the port forward I had previously created -> add -> resolve now & apply. The status shows as active, but when I use a site like checkmyports.net, it states that the port is closed.Is anyone else having port forwarding issues? What's the problem? Did I miss something? Thanks in advance.Do you have an application on the internal device that is listening on port 25565? Port will only report as open if there is a listening appliaction on the port on the destination device. Try something simple that we know works e.g. remote desktop which uses port 3389Enable remote desktop on your computer - typically right mouse click my computer, select properties, select remote settings, select remote, select Allow connections any version.now logon to router select firewall settingsselect port forwardingspecify ip address of your machineselect Remote Desktop from services - will show tcp any -> 3389 udp any -> 3389select addselect apply Now try checkmyport.net and test port 3389If it doesn't show as open then it sounds like a firewall issue In either case you'll probably want to go back in and turn off remote desktop access unless you really want to access your machine from the outside. let us know the results.

How to know if port forwarding is working?

Similar Messages

Maybe you are looking for