NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
port forwarding on FVS336gv3
I migrated from a sonicwall to Netgear FVS336Gv3, I´m configuring port fordwarding to permit RDP (in a special port 3839) and NAS (8080).
I created a Service for each port, then created a service group with both ports in it. I went to Security - Firewall - LAN WAN Rules and created an inbound rule to "always allow" under LAN Server i put the internal IP address of the RDP server "192.168.1.10", In WAN USERS Any, Destination WAN1.
I tested the conection from out off the office and it doesn´t work. If I test in the LAN it works good, for example RDP 192.168.1.10:3839.
I review the LOG and packets are accepted, but it doesn´t work.
- Have you checked the network settings of the client? Check especially default gateway but also things like firewall. An incorrect set default gateway = works locally but not from Internet.
You can also run wireshark on the client to make sure traffic hits it. The log indicates that the message is being forwarded, the fact that port testers show it as offline means that nothing responds on that port. Which is likely to be an issue on the client rather than he firewall. Packet captures would be able to prove this; do a LAN packet capture on the fvs336gv3 from the diagnostics page, if you see the traffic go out the LAN but nothing coming back the issue is with the client or something in between.
-danthem
14 Replies
Hello opeinado,
Welcome to the community!
Can you send me a PM of the screenshots of the Inbound Rules table and the rule itself?
Thanks,
Hi opeinado,
Kindly test if both ports 3839 and 8080 are really open on your FVS336Gv3 by using an online port checker tool like http://www.subnetonline.com/pages/network-tools/online-port-scanner.php. Fill-up the required fields then click "Scan Port." Let us know the results.
Regards,
DaneA
NETGEAR Community Team
It may seem silly but check and make sure that the pc that you are RDPing in to has the right default gateway. Especially since you changed out your firewall, I've seen it before. It would explain why it works locally but not from an external network despite logs showing packets as accepted.
- Have you checked the network settings of the client? Check especially default gateway but also things like firewall. An incorrect set default gateway = works locally but not from Internet.
You can also run wireshark on the client to make sure traffic hits it. The log indicates that the message is being forwarded, the fact that port testers show it as offline means that nothing responds on that port. Which is likely to be an issue on the client rather than he firewall. Packet captures would be able to prove this; do a LAN packet capture on the fvs336gv3 from the diagnostics page, if you see the traffic go out the LAN but nothing coming back the issue is with the client or something in between.
-danthemHello,
I test the server, I can view that the default gateway in the server was wrong, becouse it was pointing to the old firewall (sonicwall).
So the problem was that the conection arrived to the server, but it can´t return. I changed and now it works fine.
Thank you very much for your help.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
