Category: Internet access

Internet issues

We have received a handful of reports where schools cannot access the internet. It appears to be connected to schools that use the SafetyNet Go extension. RM are investigating. Apologies for the inconvenience.

PDNS

The NCSC’S PDNS service has been rolled out for all HFL Broadband schools:

Transparent proxy issues

Good morning… and Happy New Year.

Unfortunately, we have received a few reports today that there are issues with the transparent proxy networks This morning. Devices are connecting okay but can’t browse the internet. This is in hand and apologies.

Thanks, Kev

issues with Chromebooks connecting

We have received reports that Chromebooks are struggling to connect to the the internet.

It appears that if the Chromebooks are connected to the transparent proxy. Or if they use the no SSL proxy settings, they connect fine. It appears to be connected to SSL inspection.

This has been passed to RM to investigate…

Thanks all.

Proxy issues?

In the early hours of this morning, RM engineers added some new SafetyNet Load Balancers into service. This was planned maintenance work to ensure the service remains stable. We have received some reports this morning advising us that there are problems browsing the internet today. This is back with RM who are investigating…

I’ll add another update shortly.

Thanks,

Kevin Crawley

Websites that use websockets – Chromebooks

When using Chromebooks, you may experience issues accessing websites that use websockets. In these instances, the browser on the Chromebook attempts to go out to the internet using the SOCKS protocol entry from the proxy settings.

Normally sessions go out to the internet using the top 3 protocols (HTTP and HTTPS especially). Other devices (Windows etc) have the SOCKS protocol blank so it will send the session to the internet via HTTP/HTTPS instead. On Chromebooks if you’ve set a proxy (wf1.thegrid.org.uk etc) via G-Suite it ticks it for all protocols (including SOCKS). However, RM do not support the SOCKS protocol and this makes the outbound connection fail.

There are some high profile websites that use websockets such as SCOMIS, Spotify, and LiveStorm. It may also cause issues when using the remote desktop web client into a LARA server.

There are a couple of fixes!

Option 1) remove the entry from the SOCKS protocol, and leave it blank.
Option 2) schools connect the Chromebooks to a transparent proxy network (typically a 10.* range), instead of the proxied network (172.* range)

If you have any queries, please get in touch with our Service Desk. Thanks