Guest User!

You are not Sophos Staff.

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

SSL VPN routing issue

Hi, I have got the SSL VPN working great on a remote Win10 laptop, it gets assigned and IP address and I can access local resources as I should.

Locally we have some websites/software that needs access to specific IP address that are routed out via another interface (not via the internet).

This works perfect locally but will not work on the VPN client.  Do I need to make any changes on the UTM to allow the to work remotely as it does internally?

 

I hope this makes sense, still getting use to configuring the UTM.

Regards

Lee 



This thread was automatically locked due to age.
Parents
  • 1) are the target ip addresses allowed in the ssl vpn profile?  Can you ping them?   Download prtqryui from Microsoft and see if you can reach the target ports.

    2) are the names resolving to tbe correct ip address?    With split tunnelling, the dns lookup might be going to the internet instead of your internal dns.  Can you ping the intended dns server?

    3) if using Stanard mode, can the vpn client fetch the proxy script and can it reach the proxy address and port (another item to test with portqryui)

Reply
  • 1) are the target ip addresses allowed in the ssl vpn profile?  Can you ping them?   Download prtqryui from Microsoft and see if you can reach the target ports.

    2) are the names resolving to tbe correct ip address?    With split tunnelling, the dns lookup might be going to the internet instead of your internal dns.  Can you ping the intended dns server?

    3) if using Stanard mode, can the vpn client fetch the proxy script and can it reach the proxy address and port (another item to test with portqryui)

Children
No Data