This may help in your testing.
There are three Internet connections that have to work. Occasionally, one or more of these may be blocked by a firewall (more likely in commercial/educational networks).
The OS on the shake has the tools needed to help diagnose any problems.
Test for connectivity to DNS, NTP and the raspberryshake server:
# Connect to DNS
nc -zvw5 1.1.1.1 53
# Connect to NTP
nc -uzvw5 132.163.97.5 123
# Connect to raspberryshake server
nc -zvw5 144.91.66.87 55555
NOTE the ‘u’ in the NTP test - NTP us a UDP service.
All of those need to report success.
If any of them fail, you can find out where it is failing using traceroute. Let’s assume DNS had problems. Use traceroute to report every system that a request passes through to the destination.
This is for my shake - your network addresses will, of course, be different:
$ traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets
1 10.0.0.1 (10.0.0.1) 1.431 ms 3.337 ms 3.468 ms
2 50-209-43-154-static.hfc.comcastbusiness.net (50.209.43.154) 5.614 ms 6.538 ms 7.500 ms
3 96.120.60.177 (96.120.60.177) 16.875 ms 25.110 ms 25.848 ms
4 68.85.148.9 (68.85.148.9) 25.808 ms 25.968 ms 26.218 ms
5 68.85.146.170 (68.85.146.170) 23.204 ms 24.517 ms 25.613 ms
6 po-100-xar02.salem.or.bverton.comcast.net (96.216.60.209) 23.360 ms 20.282 ms 11.298 ms
7 ae-75-ar01.troutdale.or.bverton.comcast.net (96.216.60.221) 18.343 ms 43.621 ms 43.257 ms
8 69.252.236.134 (69.252.236.134) 52.732 ms 22.172 ms 22.083 ms
9 one.one.one.one (1.1.1.1) 19.702 ms 21.643 ms 19.435 ms
Seeing where the list ends (if its not at 1.1.1.1) will help you (or your network engineer) to determine where the problem lies.