NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Win7_Was_My_Ide
Jan 24, 2013Aspirant
FVS318G - port forwarding not working
I have a FVS318G router with firmware 3.0.7-34. A VPN is running between two sites, each have an identical FVS318G router, both using DDNS.
The VPN didn't take long to set up, even though I had no experience in setting up VPN.
Although I have had plenty of experience setting up port forwarding in other routers, I have not been able to do it on the FVS318G.
I need port forwarding because my ISP doesn't allow me to use port 80 for running a web server. I chose to use port 8079 instead. I cannot use port 8080 since FVS318G uses it for remote admin.
On my previous router, the Actiontec MI424WR router we got from Verizon FiOS, I could easily set up port forwarding to 8079, so that remote users could use my website at http://:8079
But I have had trouble doing the same on the FVS318G. The starter of this thread seemed to have the same problem as mine and was able to fix it, but I couldn't.
I followed exactly what he did:
I went to Security, Services, and added a custom service:
WEB1, TCP, 8079, 8079, Normal-Service
I went to Security, Firewall, LAN WAN Rules and added an Inbound Service:
WEB1, Allow Always, 192.168.2.12, Any, WAN1, None, Never
192.168.2.12 is the PC with the web server. Within the network, I can access http://192.168.2.12:8079 , showing the port is working on that end.
But I can't seem to open the port ON THE ROUTER. The Shields Up! website always shows my port 8079 is in STEALTH.
I mentioned earlier the FVS318G uses port 8080 for remote admin. Shields Up! *does* show port 8080 to be open. And remote admin also works (by accessing https://:8080
So why can't I open port 8079, and have I missed something with the port forwarding setup?
Thanks in advance for any help.
The VPN didn't take long to set up, even though I had no experience in setting up VPN.
Although I have had plenty of experience setting up port forwarding in other routers, I have not been able to do it on the FVS318G.
I need port forwarding because my ISP doesn't allow me to use port 80 for running a web server. I chose to use port 8079 instead. I cannot use port 8080 since FVS318G uses it for remote admin.
On my previous router, the Actiontec MI424WR router we got from Verizon FiOS, I could easily set up port forwarding to 8079, so that remote users could use my website at http://
But I have had trouble doing the same on the FVS318G. The starter of this thread seemed to have the same problem as mine and was able to fix it, but I couldn't.
I followed exactly what he did:
I went to Security, Services, and added a custom service:
WEB1, TCP, 8079, 8079, Normal-Service
I went to Security, Firewall, LAN WAN Rules and added an Inbound Service:
WEB1, Allow Always, 192.168.2.12, Any, WAN1, None, Never
192.168.2.12 is the PC with the web server. Within the network, I can access http://192.168.2.12:8079 , showing the port is working on that end.
But I can't seem to open the port ON THE ROUTER. The Shields Up! website always shows my port 8079 is in STEALTH.
I mentioned earlier the FVS318G uses port 8080 for remote admin. Shields Up! *does* show port 8080 to be open. And remote admin also works (by accessing https://
So why can't I open port 8079, and have I missed something with the port forwarding setup?
Thanks in advance for any help.
13 Replies
- Daedalus01AspirantNot sure if you have the little tick box as I do not have that particular router, but there should a box that says "translate to port". Click that (looks like 8079 internally) and enter that port number. Thats how I've been doing it on my FVS336Gv2 for quite a while.
- Win7_Was_My_IdeAspirantI do have a "Translate to port number" option but it has made no difference. I entered 8079, and Shields Up! still said port 8079 was not open. This thread (post #5) suggests not to use "translate to port number". I tried that and it didn't open the port either.
I tried many other port #s too and none worked.
I also tried setting the Inbound Service to use standard HTTP service instead of my custom service and it didn't work. - jmizoguchiVirtuoso
But I can't seem to open the port ON THE ROUTER. The Shields Up! website always shows my port 8079 is in STEALTH.
because stealth mode is enabled at default
http://interface.netgear-forum.com/FVS336G/attack_checks.htm
You should fine same with FVS318G.. I believe - Win7_Was_My_IdeAspirantDisabling stealth mode makes no difference. Shields Up! simply says the port is "Closed" instead of in "Stealth". The problem is I cannot OPEN a port for port forwarding. The only port I can open and close is the one for remote admin (Administration -> Remote Management).
- jmizoguchiVirtuosopost screenshot of your inbound rules
- aditMentorThe port say it is closed because the server isn't responding to 8079, probably just port 80/443. Like Daedalus said, you need to translate 8079 to 80.
- Win7_Was_My_IdeAspirant


- jmizoguchiVirtuoso
https://www.dropbox.com/s/kgvypfydhcil3qx/FVS318G%20screen%2001.jpg
https://www.dropbox.com/s/ilbfnxvd8p5m9xt/FVS318G%20screen%2002.jpg
looks good to me...
Looks like 8079 was working in LAN so your Web server is already configure to use 8079 - Win7_Was_My_IdeAspirant
adit wrote: The port say it is closed because the server isn't responding to 8079, probably just port 80/443.
Like Daedalus said, you need to translate 8079 to 80.
As I mentioned in my original post, the web server listens to port 8079, not 80. It does respond to 8079, since I can access the web server locally with http://192.168.2.12:8079
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!