Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 5 subscribers
  • Views 12906 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

L2TP VPN connection

RonConnelly

I have setup L2TP on my UTM and I can successfully connect to it from a Windows 7, 8 & 10 and even MAC. Once connected, and authenticated, I can ping the Sophos (192.168.10.1) but nothing else. Sophos shows the user connected but cannot access the systems or ping anything.

Sophos: 192.168.10.1
VPN Pool = 10.242.3.0/24

I have tried everything I can think of, or found online, and to no avail.

Please save me. :)
Thanks

Ron



This thread was automatically locked due to age.
Parents
  • 0

    I'm experiencing something similar and would appreciate anyone's tips. What I'm seeing is inconsistent access/pings when using either PPTP or L2TP user VPN. Authentication works perfect with RADIUS going against AD. Users can connect flawlessly, but what I'm seeing is hit or miss access once authenticated. Sometimes the servers can be pinged and sometimes it will not work. If I reboot the UTM it appears to work but then after some time will act up again.

    The Dashboard also show zero connected users even though I know there are 1-2 users connected while I'm testing. Rules and Masq are setup correctly, that I can tell. And to top it off it seems to have started acting up after some of the latest updates.

    Any thoughts or things I can try? I'm willing to do just about anything at this point to get reliability back and make users happy.

  • 0 in reply to hgriffith
    Forgot to mention, I've check the rulz and all is setup correctly. UTM 9 running 9.352-6.
  • 0 in reply to hgriffith
    I think your problem is different from Ron's, hgriffith, but nothing specific comes to mind. Did you try #1 in Rulz?
    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    Thanks Bob. I did check and recheck #1 in rulz. Second guessing my config I also went through all the other rules too. Spent a good part of today going through logs and what not. Eventually narrowed it down to a split tunnel issue. Played with a couple different setup and configs to see how the traffic was being handled by the UTM. If I configured the clients to NOT use split tunnel, everything worked well. At first i thought it was because i was pulling DHCP from the internal servers to dole out addresses for remote clients. But whether i used internal DHCP for VPN clients or the predefined L2TP and PPTP pools made no difference. I thought maybe there was something with the rules and Masq doing but that didn't make a difference. When using internal DHCP to hand address out to VPN clients I noticed the firewall thought they were internal. I adjusted rules accordingly but still had the issue. I changed everything over to using the predefined VPN pools, adjusted the rules and Masq accordingly and still had the issues. Not until I set the VPN connection to NOT use split tunnel would everything work correctly.

    I don't necessarily like having clients send all traffic over the wire but that's where I ended up. I know it's not truly resolved but it's going for now until I can get some more time to work on it and figure out the true issue. As I mentioned this only seemed to start happening after 9.352-6 was installed recently in Dec. Users I polled indicated everything worked well prior to Dec and had no problems. (scratching head as to why)

    And I still can't see the # of active of VPN users in the dashboard. I have to go to the reports to see any VPN user stats. Maybe another issue with 9.352-6?
Reply
  • 0 in reply to BAlfson
    Thanks Bob. I did check and recheck #1 in rulz. Second guessing my config I also went through all the other rules too. Spent a good part of today going through logs and what not. Eventually narrowed it down to a split tunnel issue. Played with a couple different setup and configs to see how the traffic was being handled by the UTM. If I configured the clients to NOT use split tunnel, everything worked well. At first i thought it was because i was pulling DHCP from the internal servers to dole out addresses for remote clients. But whether i used internal DHCP for VPN clients or the predefined L2TP and PPTP pools made no difference. I thought maybe there was something with the rules and Masq doing but that didn't make a difference. When using internal DHCP to hand address out to VPN clients I noticed the firewall thought they were internal. I adjusted rules accordingly but still had the issue. I changed everything over to using the predefined VPN pools, adjusted the rules and Masq accordingly and still had the issues. Not until I set the VPN connection to NOT use split tunnel would everything work correctly.

    I don't necessarily like having clients send all traffic over the wire but that's where I ended up. I know it's not truly resolved but it's going for now until I can get some more time to work on it and figure out the true issue. As I mentioned this only seemed to start happening after 9.352-6 was installed recently in Dec. Users I polled indicated everything worked well prior to Dec and had no problems. (scratching head as to why)

    And I still can't see the # of active of VPN users in the dashboard. I have to go to the reports to see any VPN user stats. Maybe another issue with 9.352-6?
Children
No Data
Unfiltered HTML