Learn about the Benefits of Multi-Factor Authentication (MFA) . Turn your MFA on now!
Information: Three minute survey on Exploring more ways to contact Sophos Technical Supportt. If you can spare the time, we would love your feedback!
We'd love to hear about it! Click here to go to the product suggestion community
Hi, I have a customer with an XG210 on 17.0.6 MR-6. In the last week or so, an increasing number of users have reported seeing the yellow exclamation mark on the internet connection icon, where Windows says there is no internet access. That's not true, everything else is working fine, web, Exchange, etc. It is intermittent. We could just ignore it, but some of the Office 365 sign-in screens use the same check, so we can't get new users logged in or passwords updated.
In the firewall log, there are entries relating to the affected PCs saying Invalid Traffic, Could not associate packet to any connection.
I can browse to http://www.msftconnecttest.com/connecttest.txt on my network (on an XG105w) and also don't get the problem. We can't browse to that page on affected PCs at the customer site. Firewall, servers, PCs all restarted. I've found some discussions in these forums on similar topics but nothing that's worked here. We're not using STAS. I've added an exception in the web filtering for ^([A-Za-z0-9.-]*\.)?msftconnecttest\.com/ but that made no difference.
How can I get these connections working again?
We are experiencing the same issue. Yet to log a support case however.
Work around was to create a firewall rule at the top of the list that allows HTTP(S) to msftconnecttest.com with Scan HTTP disabled.
In reply to HaydnCockayne:
Thanks, that has also got it working for us.
This was caused by the application filter for us (that's why the web exceptions do not work). Psiphon Proxy was the detection
The rule workaround wasn't good enough for us because it would require NAT MASQ which would pump everything to that site out one IP and we have multiple connection behind the firewall. I bet if you put the same application filter on your "workaround rule" it would stop working
In reply to Jacob McClain:
Is this something that is being fixed so it doesn't detect this going forward, or do we all need to start allowing Psiphon Proxy now? I've seen this on top of the list for blocked apps on most of the XGs I manage.