Sophos Connect 2.3 MR1 iPSec DNS problems but SSL OK

Hi StefanS,

Thank you for reaching out to Sophos Community. 

To verify, do the IPsec DNS settings change after the update? And in comparison with the SSL VPN DNS settings

I recommend creating a support case and kindly sharing it here since the issue occurs upon firmware upgrade. This will allow us to check this further.

Hi Erick,
Thank you for your answer.
The DNS settings for remote IP-Sec are correct.
I will open a ticket for this problem as you recommended.

Case ID: 07421499

Hi StefanS 

We are trying to reproduce this in our lab and we will come back with an update soon this topic.

Hi StefanS 

What is the Windows version that you are on ?

Is the Windows version(10 or 11), when you were on SFOS version v19.5MR1 ??

Is the DNS entry populated correctly when you were on v19.5MR1 ?

Please share the openvpn log from the SCC.

Hi Giridhar Katti 
the affected systems are Windows 10.
Out of about 60 systems, the upgrade to v2.3.1, 2 systems were affected where the wrong DNS server is published with IPsec and on some other systems only the FQDN works, the hostname alone does not work here. Although the domain suffix was also specified in the IPsec profile.
In SFOS 19.5.1 and Sophos Connect v2.2.9 we only saw the FQDN problem sporadically, but not that the wrong DNS servers were transmitted completely.
What we can say in general is, that with SSL VPN the DNS resolution works very stable instead of IPSec.

For those 2 Win-10 machines, could you share the screen shot of the Network adapters ? 

On working machines, the virtual adapter's name would be "Sophos TAP Adapter". Right ?

On non-working machines, what is the name of virtual adapter ? Do you see any suffix to "Sophos TAP Adapter" ? Like "Sophos TAP Adapter #2" or "Sophos TAP Adapter #3" etc" ?

You can see these details under "Control Panel\Network and Internet\Network Connections".

Hi StefanS,

Upon checking case 07421499.

Further updates will be shared on the committed date, August 2, 2024.

Before opening a support case of my own I wanted to see if there were any updates that could be shared on this issue as I'm experiencing similar problems.

The correct IPv4 DNS server addresses are not populated into the Sophos TAP adapter on specifically two machines but works on the rest of the fleet.

I'm also seeing in the logs "x.x.x.x not in server list doing add",

"TAP adapter not found. Error code = 0x00000001",

"failed to get TAP adapter information. Error code = 2"

"adding DNS server failed"

Hi David,

We regret to hear about your experience.

Could you share more information about the issue you’re experiencing with the two clients? 

What firmware version are you using in your firewall? Sophos Connect Client Version?

You may also check the following issues, which the update has resolved.

 Sophos Connect 2.3 Update Released