I tried to install Sophos connect to a windows server 2016 to run server as a client. I installed it, I Imported the config file but when I Try to connect it says OpenVPN service is not available. I looked for the services but everything is running. My suspicious is windows server cannot run as a client. Any ideas?? Thanks you!
LTSC are not supported TheMonzel
Hello Angelos Zikos1,Thank you for reaching out to the community, which version of sophos connect you are using?Between you can download the latest version of the Sophos Connect (IPSec and SSLVPN Client) - https://www.sophos.com/en-us/support/downloads/utm-downloadsWhat is the built of your Windows Server 2016 can you share more details on that ?
Thanks & Regards,
Vivek Jagad | Technical Account Manager 3 | Cyber Security Evolved
Sophos Community | Product Documentation | Sophos Techvids | SMSIf a post solves your question please use the 'Verify Answer' button.
Hello! Sophos connect versions are
And Windows Server 2016 build is 1607
Are you able to find the Sophos connect services & OpenVPNService under services.msc ? Angelos Zikos1
Then have you tried uninstalling and re-installing the client and ensure no other similar client is active like legacy SSL client or something similar !!
I have tried that many times... still nothing.. I also turned off windows firewall in case that something is wrong with that...
Can you share the scvpn logs from the following directory "C:\Program Files (x86)\Sophos\Connect"
you can open the scvpn text document, that will have the log information !!
2022-07-14 12:21:37PM  inf Starting Sophos Sophos Connect version 2.2.75.05062022-07-14 12:21:37PM  dbg Initializing protected storage2022-07-14 12:21:37PM  inf Logged on user is VMI258713\Administrator2022-07-14 12:21:37PM  dbg Starting the auto-importer2022-07-14 12:21:37PM  inf Initializing strongSwan2022-07-14 12:21:40PM  dbg strongSwan version 5.9.5 has been started2022-07-14 12:21:40PM  inf Initializing open vpn service2022-07-14 12:21:40PM  dbg Starting the communications module2022-07-14 12:21:40PM  dbg Starting HTTP server on 127.0.0.1:601102022-07-14 12:21:40PM  inf Sophos Connect started2022-07-14 12:21:45PM  dbg Sending telemetry data to sftelemetry.sophos.com:4432022-07-14 12:21:52PM  dbg ssl01.hbbody.com VPN state changed to connecting2022-07-14 12:21:52PM  dbg Starting tunnel (connecting)2022-07-14 12:21:52PM  dbg Can't create tunnel - failed to start ovpn2022-07-14 12:21:52PM  dbg State is connecting, setting to disconnected2022-07-14 12:21:52PM  dbg ssl01.hbbody.com VPN state changed to disconnected2022-07-14 12:21:52PM  dbg Sending notification: OpenVPN service is not available
The logs shared matches with the known issue list - https://support.sophos.com/support/s/article/KB-000036055?language=en_US[NCL-1380/NCL-1382] where in “OpenVPN service is not available” not available while connecting SSL VPN from windows 7 and 8. Can you try installing the Sophos Connect Client on another machine which has Windows Server 2016 with 1607 Build ?
I just tried.. still the same problem...you think the problem is that it is a windows server? I tried on windows pc and worked fine..
Yup, the latest windows OS like 10 are supported well, I am suspecting a similar issue as mentioned above with the known issue with the windows server too.
I seem to have the same problem on Windows 10 LTSC Versions. I got a support Case (05483174) for this, but were not have a deeper look with the support.
The legacy client worked fine on those devices.I will update the support case and come back, if there are any news.
Just found this in another topic -.-(Sophos Connect - OpenVPN service not available - Windows 10 LTSB (IoT) - Discussions - Sophos Firewall - Sophos Community)
TheMonzel, check the following doc: > https://docs.sophos.com/nsg/sophos-firewall/18.5/Help/en-us/webhelp/onlinehelp/AdministratorHelp/VPN/RemoteAccessVPN/VPNSophosConnectClient/index.html#sophos-connect-client-compatibility-with-platforms
For anyone seeing this - Vivek Jagad and I had discussion about ARM/LTSC/IoT and that LTSC/IoT is equal to ARM and that those editions can be a x86/x64 system. The docs does not cover those cases. Vivek is going to have a deeper look internally, raised a service request and will update us all once there are more infos