USG40: My PC on LAN1 cannot connect to a device on LAN2

estabroj

ZyXEL Device: USG40.
I have a ALLWORX 6 VOIP switch on LAN2, IP 172.16.10.254\24, Interface 4. My PC is on LAN1, IP 192.168.10.73\24, Interface 1. I am trying to connect to the ALLWORX's web configuration server, unsuccessfully, so for. I have plugged my PC directly into the ALLWORX and it provided my PC with an IP and I was able to connect successfully, so it will accept connections. I'd like to be able to get to the ALLWORX through the network for convenience and so I can work on its configuration from my iPAD or another device.

There is a direct route configured, that I believe was established when I created the 172 network on LAN2. See the Following image please.



I have not established a Policy Route yet, as I didn’t think I’d need it. 



What I know so far.

I can successfully ping the USG40's interface on LAN2 at 172.16.10.1 FROM MY PC.

C:\>ping 172.16.10.1

Pinging 172.16.10.1 with 32 bytes of data:

Reply from 172.16.10.1: bytes=32 time<1ms TTL=64

Reply from 172.16.10.1: bytes=32 time<1ms TTL=64

Reply from 172.16.10.1: bytes=32 time<1ms TTL=64

Reply from 172.16.10.1: bytes=32 time<1ms TTL=64

Ping statistics for 172.16.10.1:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = 0ms, Average = 0ms

I cannot ping the ALLWORX FROM MY PC.

C:\>ping 172.16.10.254

Pinging 172.16.10.254 with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 172.16.10.254:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

The USG40 can successfully PING the ALLWORX using the built in Diagnostic tools.

# ping 192.168.10.254 -n -c 3

PING 192.168.10.254 (192.168.10.254) 56(84) bytes of data.

64 bytes from 192.168.10.254: icmp_seq=1 ttl=64 time=0.291 ms

64 bytes from 192.168.10.254: icmp_seq=2 ttl=64 time=0.186 ms

64 bytes from 192.168.10.254: icmp_seq=3 ttl=64 time=0.160 ms

--- 192.168.10.254 ping statistics ---

3 packets transmitted, 3 received, 0% packet loss, time 1998ms

rtt min/avg/max/mdev = 0.160/0.212/0.291/0.057 ms

I think I need a policy route, but I've played with that all night with no success.

Any help would be provided.

Thanks.

JE.

#Biz_Security_Jan_2019

Blabababa

Did you enabled the layer 2 isolation function or proxy-ARP on the device? If so, you can try to turn it off and see if it works