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
- Win7_Was_My_IdeAspirant
jmizoguchi wrote: looks good to me...
Looks like 8079 was working in LAN so your Web server is already configure to use 8079
Any solution? You've got lots of threads asking about port forwarding. What is it with this line of routers? - jmizoguchiVirtuosoAll look very straight forward. Should responds to 8079
and should be open. - Win7_Was_My_IdeAspirantFINALLY was able to fix it. I had to REBOOT the router after changing the settings in order to make it work. This is clearly a bug, since all the other features do not require a reboot to work. All the other threads about port forwarding that didn't get a solution, maybe rebooting would fix it too. It's stupid, I know. Btw, it was not my idea to buy this router, since I would never buy something that has a one-and-half-star rating at Newegg, Lol. When my consultant recommended this router to me, I was concerned. Sure enough, something stupid happened.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!