Thread Info
  • State Verified Answer
  • +3 person also asked this people also asked this
  • Locked Locked
  • Replies 21 replies
  • Subscribers 34 subscribers
  • Views 40863 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

How to configure the new Sophos Connect VPN in 17.5

Brian Hawkins

So far I have found the documentation lacking for setting up the new VPN client that comes with 17.5. Specifically in regards to the internal and external ID and what thats for.  I am also wondering with the IP range? Does it create the DCHP pool automatically? 

It would be great if there was a walkthrough on setup or if there were any more details. But I can't find any.



This thread was automatically locked due to age.
  • 0 in reply to Chip Barnett

    I have that rule in place to allow access to the different vlans for the SSL VPN assumed that same VPN rule was being used by Client Connect.

  • 0

    Grab the updated installer v1.1 came out last night.

     

    https://community.sophos.com/products/xg-firewall/b/xg-blog/posts/sophos-connect-1-1-released

     

    Also for those wanting to restrict access to certain subnets / networks you can do this by modifying the TGB file with the admin tool.

    LuCar Toni Linked it earlier:

     

    https://community.sophos.com/kb/en-us/133109

     

    I did this and then pushed the Sophos Connect MSI and TGB file out via PDQ to all my VPN users. So far it's been solid.

    I find it easier to manage than SSL-VPN due to the certificate per user issue.

    Sophos XG 450 (SFOS 18.5.1 MR-1)

    Sophos R.E.D 50 x 2

    Always configuring new stuff.....

  • 0 in reply to M8ey

    Little sneak peek.. Check out the installation directory on windows. There is something called sccli.exe

    Open this with Cmd --help :) 

    __________________________________________________________________________________________________________________

  • 0 in reply to LuCar Toni

    Hmmmmm.....

     

    add options:
    -f, --file PATH Adds the connection from the specified path.
    -d, --data Send the file data instead of the file path.
    -n, --name NAME The user-friendly name of the connection. If this option
    is omitted, the name will be determined automatically.
    -a, --auto Automatically enable the connection. (TBD)
    -V, --verbose Show verbose messages.
    -H, --help Show help for the add command.

    * The add command will fail in environments where policy does not allow
    unmanaged connections to be used.
    * If the add command is successful, the connection's name will be written to
    the command line. This name is used in other command line options.
    * If the auto option is omitted, the connection may still automatically be
    enabled based on the settings in the connection file.

    Sophos XG 450 (SFOS 18.5.1 MR-1)

    Sophos R.E.D 50 x 2

    Always configuring new stuff.....

  • 0 in reply to Brian Hawkins

    Thanks for this. Mine was made that way also, just with PSK, but nonetheless, the same.

     

    Haven't had the time to fiddle with it, until today, so instaleld the new version, and boom, it all worked :-D 

     

    Hooray and merry x-mas ;)

    -----

    Best regards
    Martin

    Sophos XGS 2100 @ Home | Sophos v19 Architect

  • 0 in reply to twister5800

    Have added DC as DNS IP, I can ping the DC on IP, but not resolve domains. have any of you, got internal DNS working?

    -----

    Best regards
    Martin

    Sophos XGS 2100 @ Home | Sophos v19 Architect

  • 0

    I configured Sophos Connect on my XG, downloaded client and installed.  I can't even make a connection.  I see "Connection may fail because IKE UDP Port seems to be blocked".    It does seem like my XG has ports 500 and 4500 closed.  I have no firewall rule configured for Sophos Connect - didn't think one was needed but perhaps that's another documentation shortfall.  Any advice will be appreciated.

    Thanks!

  • 0 in reply to Ed_C

    I'm also having the same issue with IKE UDP port being blocked. What's the best solution to this? Opening up those two ports?

  • 0 in reply to Nicholas Sutrich

    Hi,

    is there a upstream router on the wan interface? use the admin tool and load the configuration. please verify the FQDN or IP-Adress of the host.

     

    best regards
    Detlef

  • 0 in reply to Ed_C

    This will require some troubleshooting to determine where along the path to the gateway (XG) UDP port 500 is blocked. scvpn.log file will provide some additional details. The log file can be found in c:\program files (x86)\sophos\connect on Windows and /var/log on Mac OS. Please post that file here so it can help me to determine the problem.

Cookie Information Banner