Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[SOLVED} Sophos Connect Clients can't ping LAN resources

ETA Solution: Windows Firewall, of course.
Thanks @LuCar Toni





The Sophos Client successfully connects to the XG.
I can ping 8.8.8.8 while connected.
I can ping the XG's LAN interface (10.0.4.1) while connected (172.16.16.5 can ping 10.0.4.1).
I can NOT ping any resources on the LAN (e.g., 10.0.4.2) while connected.
I can NOT ping 172.16.16.5 (Sophos Connect Client virt. IP) from the XG command line).
Wireshark PCAP on 10.0.4.2 shows the ping arriving at 10.0.4.2 NIC but I get a "(no response found!)" rather than the expected "(reply in [time])"

Port 1 is physically connected to the LAN switch.

PCAP on the XG: When I ping 10.0.4.2 from the remote client, I see the following...
ipsec0, IN: 172.16.16.5 > 10.0.4.2
br0, OUT: 172.16.16.5 > 10.0.4.2
Port1, OUT: 172.16.16.5 > 10.0.4.2 


PCAP on the XG:  When I ping FROM 10.0.4.2 to the remote client, the PCAP on the XG shows the following...
Port1, IN: 10.0.4.2 > 172.16.16.5
br0, IN: 10.0.4.2 > 172.16.16.5
Port1, IN: 10.0.4.2 > 172.16.16.5

Would appreciate any help figuring out what I'm doing wrong. This should be very simple to configure. I'm either overthinking/over-complicating it, which happens a lot, or something is broken.




 


This thread was automatically locked due to age.
Parents
No Data
Reply
  • Yep.

    Thank you so much.

    I hate Windows. That should have been the first thing I checked.

    I built it with the Firewall off. The HQ is about 200 mi away from me and their part-time "IT guy" keeps it updated and sometimes tinkers around in there.

    Wow. Thanks again. I knew it was going to be something stupid simple.


Children
No Data