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

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 40 subscribers
  • Views 2286 views
  • Users 0 members are here
Options
Suggested
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

Sophos Home Firewall - Work VPN connects, applications don't work

Chris Barton

Hi, 

I'm currently running Sophos Home Firewall on my home network (192.168.X.X) and having trouble working from home using the VPN provided by my workplace (Cisco Duo). I can connect to the VPN ok, i receive the local IP address (10.x.x.x) and any locally installed applications and network drives are working. There are some applications that are accessed through citrix and these are not working when connected through the sophos firewall.  If i connect the same PC to a mobile wifi hotspot, the applications work perfectly, however as soon as i route through sophos, i cant access the remote applications even though the VPN is connected.

I created a firewall rule to let anything out from that mac address, but something is still being blocked. 

Any ideas where else i need to look please? I have checked logs and cant see any traffic being dropped using the local ip address as source or destination ip.

Thanks



This thread was automatically locked due to age.
Parents
  • +1

    Hi All, 

    Thanks for everyone's help, i did try all of the below but after probing further, capturing packets and pinging domain names, I found it to be an address/domain authentication conflict with the remote server. It was setup using the 192.168.X.X range which was then causing authentication issues based on my internal network setup and connecting through the work VPN. I created a separate VLAN (10.1.1.X range) and assigned my work laptop to that and it connected to the RDP servers straight away. 

    Just wanted to close the loop for people

    Thanks

Reply
  • +1

    Hi All, 

    Thanks for everyone's help, i did try all of the below but after probing further, capturing packets and pinging domain names, I found it to be an address/domain authentication conflict with the remote server. It was setup using the 192.168.X.X range which was then causing authentication issues based on my internal network setup and connecting through the work VPN. I created a separate VLAN (10.1.1.X range) and assigned my work laptop to that and it connected to the RDP servers straight away. 

    Just wanted to close the loop for people

    Thanks

Children
Unfiltered HTML