Scheduled maintenance on Saturday, August 8th from 7am to 10am (UTC). Licensing registrations and key activations will be unavailable during this period. More info here.
We'd love to hear about it! Click here to go to the product suggestion community
...back again with another Connect Client issue
I can establish a connection but there are wrong (external IPV6) DNS server entries on the client.
I configured DNS servers on the XG:But this is what the client shows:Therefore I'm unable to ping hostnames, IPs work fine.
Client Version is 1.2.5.0202XG Version 17.5.4 MR-4
In reply to rmk_2018:
actually I gave up this morning... All I can say is that everytime I make a change in the policy I click on Apply afterwards and Export connection. On the client-side I delete the "old" profile and import the new one.I tried 3 different certificates: Appliance cert, our domain cert and a self generated cert - Everytime I get the same errors: no issuer certificate found and no trusted RSA public key found
Sorry if my dumbness is the cause of this
I opened a support case.
In reply to ChristianD:
My apologies for any inconvenience caused and no worries at all, we are here to help. Would it be possible to PM me with your support case details so I can follow up with you accordingly?
In reply to FloSupport:
Same problem for me. I opened a case with French support,they noticed the problem on my computer but can't find a solution.
The "Sophos Connect" window indicates the right dns servers, but ipconfig /all shows that there are only ipv6 servers in there.
In reply to yvesGourle:
I suppose you are testing with the latest release of Sophos Connect Client? Sorry to hear that the problem isn't solved.I didn't test anymore since I opend this threat, because we needed a solution immediatelly. We are using OpenVPN client.
Yes, last XG firmware and last Connect version...The problem occurs on some computers but not on all. And obviously we can't see what makes them different.
Ok, that's strange
Could you please post any update on this?
there is another post about the same problem
Workaround is suggested, I'll try. Also it seems it occurs only on 1903 (or insiders above) versions.
Thank you Yves, I'll follow this post. Good luck on the workaround!