" Mark -
Thanks for writing to Todd at GNC to inquire about the show.
I changed to a different server February 1st to increase overall reliability and in the transition there have been troubles, mostly with Cox subscribers, that apparently is traceable to problems in cached DNS information and ACL lists.
You could be of great help if you could do a traceroute or tracert to 188.8.131.52, and email me a copy of the results. It appears that a machine formerly at that IP address at GoDaddy had been repeatedly attacked from various blocks within Cox but that an exact IP address for the attacker was not determined. Godaddy and Cox both have selectively blocked certain portions and addresses and if I can get listeners to do a traceroute attempt we can determine where the blockage exists. The more data points we can get will help us converge on the problem ACL.
If you have friends who are also SDR listeners or non-listeners that you could ask to send in a ping report it would really help.
A clean ping and traceroute should look something like this.
Pinging slashdotreview.com [184.108.40.206] with 32 bytes of data:
Reply from 220.127.116.11: bytes=32 time=218ms TTL=49
Reply from 18.104.22.168: bytes=32 time=244ms TTL=49
Reply from 22.214.171.124: bytes=32 time=257ms TTL=49
Reply from 126.96.36.199: bytes=32 time=184ms TTL=49
Ping statistics for 188.8.131.52:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 184ms, Maximum = 257ms, Average = 225ms
If the ping does not resolve to 184.108.40.206, then Andy would really like to see a traceroute.
Tracing route to ip-68-178-200-238.ip.secureserver.net [220.127.116.11]
over a maximum of 30 hops:
1 73 ms 49 ms 252 ms 18.104.22.168
2 163 ms 70 ms 52 ms dis10-london14_Vlan103.net.bell.ca [22.214.171.124]
3 209 ms 170 ms 53 ms core1-london14_GE4-0.net.bell.ca [126.96.36.199]
4 122 ms 164 ms 47 ms core1-toronto63_POS9-3.net.bell.ca [188.8.131.52]
5 131 ms 102 ms 92 ms core4-toronto63_POS0-1.net.bell.ca [184.108.40.206]
6 167 ms 146 ms 59 ms core1-chicago23_pos12-0-0.net.bell.ca [220.127.116.11]
7 199 ms 56 ms 157 ms bx1-chicagodt_POS6-0.net.bell.ca [18.104.22.168]
8 76 ms 106 ms 55 ms Qwest_bx1-chicagodt_POS7_0.net.bell.ca [22.214.171.124]
9 56 ms 62 ms 398 ms cer-core-02.inet.qwest.net [126.96.36.199]
10 * * * Request timed out.
11 101 ms 101 ms 390 ms phv-edge-03.inet.qwest.net [188.8.131.52]
12 102 ms 249 ms 167 ms 184.108.40.206
13 187 ms 214 ms 106 ms ip-208-109-112-154.ip.secureserver.net [220.127.116.11]
14 124 ms 275 ms 247 ms ip-208-109-112-137.ip.secureserver.net [18.104.22.168]
15 327 ms 200 ms 115 ms ip-208-109-112-161.ip.secureserver.net [22.214.171.124]
16 134 ms 147 ms 106 ms ip-216-69-188-18.ip.secureserver.net [126.96.36.199]
17 169 ms 278 ms 178 ms ip-68-178-200-238.ip.secureserver.net [188.8.131.52]
Thanks in advance for any help. If you can post any failing traceroutes here I will forward them to Andy
Help, my PC with Windows 10 won't shut down properly
Since upgrading to Windows 10 my computer won't shut down properly. I use the menu button shutdown and the screen goes blank, but the system does not fully shut down. The only way to get it to shut down is to hold the physical power button down till it shuts down. Any suggestions?