NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
4.3.3-6
2 TopicsProtocol Binding 4.3.3-6 no internet DNS request resolved
SRX5308 with 4.3.3-6 firmware. We have 3 WAN ports in use. WAN1 suddenlink, WAN2 ATT, WAN3 3rd party. All can supply access to the internet and all work correctly when I connect my laptop directly to the port. I want to implement protocol binding in the version. Previous versions I would specify the special protocols to the appropriate WAN ports and then have an all that would cover everything else. WAN1 HTTP traffic, WAN2 SMTP and WAN3 PPTP, then an ANY protocol for WAN1. So this would direct any protocol not specifically specified to WAN1. Well the firmware now will not let you do this. It tells you not allowed to assign duplicate protocol. As soon as I enable load balancing which is required for protocol binding all the my dns request fail. I have reset the system to factory defaults and hand keyed all the settings for the upgrade but it still will not process DNS request when load balancing is enabled. From the diagnostics ping I see returns from the internet so the internet connection is working. I had this working perfectly in my previous firmware version. I took screenshots of the setup before setting the defaults on the unit and upgrading the firmware. When I dont have protocol binding (load balancing) enabled the unit works as expected after a reboot. It is when I enable load balancing when I cannot resolve any DNS request. I have set the defaults and loaded the firmware above 3 times.4.2KViews0likes7CommentsFVS336GV2 VLANS and Port Forwarding - firmware 4.3.3-6
Howdy, Correct me if I am wrong, but in order to get full VLAN support I need to use 4.x firmware. I saw the LAN Groups in firmware 3.11.0-8, but it didnt really look like true VLANs (but I could be wrong). Let me know if I can get this working with firmware 3.11.0-8 As well, once upgraded to 4.3.3-6 (to get VLAN support) I am having difficulty getting Port Forwarding for RDP AKA Terminal Services (port 3389) to work. I want to achieve 3 VLANs, port forwards, and VPN access with this environment: Port/VLAN 1 (Default - Office Network -- port forwards and VPN access) Port/VLAN 2 (Phones) Port/VLAN 3 (Video) ...and I'd like to get the Port Forwards to work currently. I havent't tried getting the VPN working yet as I have to get the ISP to correct something with the Modem/Gateway first so I can get to the interface to change settings and allow the IPSec traffic to pass through. I'd like to keep the Modem's Wifi working so I can use it as as a guest Wifi. As it stands, I have told the FVS336GV2 (192.168.10.x network) to forward 3389 on TCP and UDP from WAN1 (192.168.0.x) to the IP of the device I am trying to reach in the 192.168.10.x network. WIndows Firewalls are set to OFF for Public and Private interfaces. I have validated I can get to port 3389 if I connect a 2nd NIC directly to the ISP's Gateway (192.168.0.x) on a different IP than the FVS336GV2's WAN1 IP and change the port forward on the ISP's gateway to this IP, but the FVS336GV2 doesnt act like it even sees the traffic (no firewall logs) when the Forward is set to the WAN1 IP in the ISP's Gateway. Any thoughts on how I can get this sorted out? Or is firmware 3.11.0-8 capable of VLANS as needed, as I know the port forwards and VPN work there. P.S. according to the firmware notes for 4.x, there is a 25% speed drop as a result of the newer firmware. Is the 25% speed drop just in the interface for the FVS336GV2 or the overall performance of the network activity of the device itself? Please and Thank You, StevenSolved5KViews0likes4Comments