Comments
-
That is a great question. Phone --> Switch --> Allworx Server --> Watchguard --> Internet That's my thinking at least.
-
Current DHCP Server IP 192.168.2.254 Current DHCP Lease Time 0 hr 30 min 54 sec Current SNTP Time Server IP 192.168.2.254 Current Boot Server IP 192.168.2.254 Current Phone IP 192.168.2.10 Current Subnet IP 255.255.255.0 Current Gateway IP 192.168.2.254 Current VLAN Mode LLDP Enabled Primary DNS Server 8.8.8.8
-
Thank you for clarifying, it appears the gateway setting on the phone points to the Allworx Server @ 192.168.2.254
-
192.168.20.1 is the default gateway set on the Allworkx system (192.168.2.254) that currently comes into the Watchguard over the ETH2 interface, so it seems the infamous Watchguard has dominion over it.
-
Thank you for the advice, I will roll with that.
-
Yes it did have connectivity issues with the SonicWALL in place, I could ping the devices on the 192.168.2.0 subnet but they did not have internet access. I do have admin access to the Allworx phone server but wouldn't say I'm "comfortable" with troubleshooting it but have to grab the bull by the horns as they don't have…
-
Well my thinking is to eliminate the 192.168.20.0 subnet altogether , change the gateway of the phone server to point the SonicWALL at 192.168.0.254 and attempt to tag traffic coming from the Phone Server with QoS on the SonicWALL. I would think we can remove the static on X3 at that point , test and go from there.
-
No offense taken, thanks for reaching out.
-
Thank you for the response, I agree on the Watchguard portion. We would prefer to move everything to the SonicWALL but didn't want to break anything in the process. Currently this is what we have setup on the SonicWALL X0 LAN 192.168.0.254 <- SonicWALL IP , didn't think we needed to define a VLAN for the primary subnet of…