Allworx Technical Support Forum

Hi Everyone,

I just inherited an Allworx Connect 536 and we are trying to have one of our base stations RTX8660 connect back to the server over the S2S VPN. The base station worked fine locally but it keeps failing when trying to register over the VPN. The server is located on a 192.168.15.0/24 and the remote subnet is 192.168.100.0/24. We have tried also ping the server from the remote network using its local ip but it would not respond but are able to ping all other devices on the 192.168.15.0/24 network from 192.168.100.0/24.

The Server has 2 interfaces setup one assigned a public ip and the other a local. Any help would be greatly appreciated I have been trying to figure this out for a few days now and have not been able to find a solution.

LAN Host Mode: disabled
NAT: enabled
Firewall: enabled
Stealth Mode: enabled
Public Interface Network: VLAN: ETH1/untagged | Public
Default Gateway: X.X.X.X
External IP Address
LAN Addresses and Ports
exposed through Firewall
Allworx Reach and Remote Allworx Handsets (2088,8081): disabled
Allworx View (54441): disabled
DNS Client (4069): enabled
DNS Server (53): disabled
HTTP (80): disabled
HTTPS: Secure Allworx Adminstration (8443): disabled
HTTPS: Secure My Allworx Manager (443): disabled
IMAP4 (143): disabled
Multisite Voicemail (26): disabled
POP3 (110): disabled
PPTP (1723): enabled
SIP (5060): disabled
SNMP (161): disabled
SNTP Client (4068): disabled
DNS Server Mode: Normal


VLAN Configuration Current Value
ETH0/untagged | Local Phones
192.168.15.201/24 BLF
Current IP Address: 192.168.15.201
Current IP Mask: 255.255.255.0

ETH1/untagged | Public
X.X.X.X/29 BLF
Current IP Address: X.X.X.X
Current IP Mask: 255.255.255.248

What is the gateway? That is key. If it is not the LAN gateway (meaning, the gateway routing through the VPN) then that's the problem. You can try creating a static route on the Allworx to the 192.168.100.0 network using 192.168.100.1 (if that is correct) as the gateway. I suspect traffic is getting to the Allworx from the remote side but responses by the Allworx are being sent out its WAN interface gateway instead.

wshrader wrote: ↑Tue Oct 03, 2023 5:39 pm What is the gateway? That is key. If it is not the LAN gateway (meaning, the gateway routing through the VPN) then that's the problem. You can try creating a static route on the Allworx to the 192.168.100.0 network using 192.168.100.1 (if that is correct) as the gateway. I suspect traffic is getting to the Allworx from the remote side but responses by the Allworx are being sent out its WAN interface gateway instead.

The gateway is set to the Comcast Public IP.

If I set the static route would it be like below:
Destination: 192.168.100.0 Netmask: 255.255.255.0 Gateway:192.168.100.254 - Firewall at remote location
or is gateway 192.168.15.1 which is the firewall on the same subnet as the server?

Thanks.

Thanks I was able to resolve it by setting the static route using gateway 192.168.15.1.

Solved