Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 2 subscribers
  • Views 13612 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

SSL VPN no access to internal network

mwingeier

Let me start off by saying that I do not use my VPN frequently, so I cannot say when it stopped working.  I had occasion to use the VPN a few weeks ago, and notice that I did not have access to my internal network.  I could not reach anything by name, fully qualified name, nor IP.  Looking at my routing table, it shows that the proper routes got added, but looking at the adapter properties, it seems that there is no default gateway assigned.  I thought that this might be due to Windows 10, but I tried it on Windows 7, and neither one worked.  My DHCP is handled internally by my Windows servers, and it has always been handled there, but I do wonder if that is suddenly a problem after an update or something, I am running firmware 9.403-4.  Any help with this situation is appreciated!



This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to sachingurung

    Yes, that did resolve the problem, though it is my first attempt at SNAT, so I hope I did it properly.  I have it set up like so:

    Traffic from: VPN Pool
    Using Service: Any
    Going to: Any

    Change source to: Internal (Address)
    Service to: <blank>

    Automatic firewall rule created

    Are there changes I should make for security's sake?

Children
Unfiltered HTML