Sophos Connect on Windows Server

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-downloads

What is the built of your Windows Server 2016 can you share more details on that ? 

Hello! 
Sophos connect versions are

• Sophos Connect service 2.2.75.0506
• strongSwan service 5.9.5
• OpenVPN service 2.5.6.0

And Windows Server 2016 build is 1607

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 [4644] inf Starting Sophos Sophos Connect version 2.2.75.0506
2022-07-14 12:21:37PM [4644] dbg Initializing protected storage
2022-07-14 12:21:37PM [4644] inf Logged on user is VMI258713\Administrator
2022-07-14 12:21:37PM [4644] dbg Starting the auto-importer
2022-07-14 12:21:37PM [4644] inf Initializing strongSwan
2022-07-14 12:21:40PM [4644] dbg strongSwan version 5.9.5 has been started
2022-07-14 12:21:40PM [4644] inf Initializing open vpn service
2022-07-14 12:21:40PM [4644] dbg Starting the communications module
2022-07-14 12:21:40PM [4644] dbg Starting HTTP server on 127.0.0.1:60110
2022-07-14 12:21:40PM [4644] inf Sophos Connect started
2022-07-14 12:21:45PM [8144] dbg Sending telemetry data to sftelemetry.sophos.com:443
2022-07-14 12:21:52PM [4272] dbg ssl01.hbbody.com VPN state changed to connecting
2022-07-14 12:21:52PM [4272] dbg Starting tunnel (connecting)
2022-07-14 12:21:52PM [4272] dbg Can't create tunnel - failed to start ovpn
2022-07-14 12:21:52PM [4272] dbg State is connecting, setting to disconnected
2022-07-14 12:21:52PM [4272] dbg ssl01.hbbody.com VPN state changed to disconnected
2022-07-14 12:21:52PM [4272] 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.

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.

LTSC are not supported TheMonzel

Just found this in another topic -.-
(Sophos Connect - OpenVPN service not available - Windows 10 LTSB (IoT) - Discussions - Sophos Firewall - Sophos Community)

yeayyy

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