Comments on: XplorNet Customer Service Found Lacking http://blog.verselogic.net/archives/2005/xplornet-customer-service-found-lacking/ The personal blog of Alan J Castonguay. Sat, 22 Nov 2008 12:41:12 +0000 http://wordpress.org/?v=2.7-hemorrhage hourly 1 By: Anonymous http://blog.verselogic.net/archives/2005/xplornet-customer-service-found-lacking/#comment-9583 Anonymous Fri, 03 Nov 2006 06:25:57 +0000 http://blog.verselogic.net/archives/2005/05/28/xplornet-customer-service-found-lacking/#comment-9583 xplornet should have a class action law suit against it. this is unusable worthless dishonest advertising. it doesnt work, dont get it xplornet should have a class action law suit against it.
this is unusable worthless dishonest advertising.
it doesnt work, dont get it

]]> By: Alan J Castonguay http://blog.verselogic.net/archives/2005/xplornet-customer-service-found-lacking/#comment-8523 Alan J Castonguay Wed, 06 Sep 2006 23:37:53 +0000 http://blog.verselogic.net/archives/2005/05/28/xplornet-customer-service-found-lacking/#comment-8523 Ok, that was my fault totally. Not a windows computer, but rather a router that I had configured with an overly locked down ICMP policy last week. That's been fixed, and my traceroute returns to its former glory. <code>traceroute from azaphrael.org (69.130.198.24) to verselogic.net (142.46.152.131) 1 mdsnwigjbas01-lo0-secondary7.network.tds.net (216.165.144.1) 42.474 ms 42.416 ms 44.663 ms 2 mdsnwigjlcr51-v702.network.tds.net (216.165.156.82) 43.266 ms 43.023 ms 43.303 ms 3 rt1ec-equinix.il.shawcable.net (206.223.119.20) 46.567 ms 47.213 ms 47.261 ms 4 rd1ec-ge0-0-0.il.shawcable.net (66.163.65.17) 47.292 ms 46.978 ms 47.038 ms 5 rc1ch-pos5-0.il.shawcable.net (66.163.65.9) 47.261 ms 47.010 ms 47.251 ms 6 rc2sh-pos14-0-0.mt.shawcable.net (66.163.77.97) 58.378 ms 58.609 ms 58.306 ms 7 ra1sh-ge3-4.mt.shawcable.net (66.163.66.30) 59.118 ms 59.289 ms 59.324 ms 8 rx0sh-hydro-one-telecom.mt.bigpipeinc.com (66.244.223.246) 58.871 ms 59.804 ms 59.348 ms 9 142.46.128.6 (142.46.128.6) 120.518 ms 73.711 ms 72.327 ms 10 142.46.128.82 (142.46.128.82) 74.836 ms 74.818 ms 76.336 ms 11 142.46.130.26 (142.46.130.26) 83.516 ms 87.612 ms 84.987 ms 12 verselogic.net (142.46.152.131) 117.025 ms 121.857 ms 120.752 ms</code> Ok, that was my fault totally. Not a windows computer, but rather a router that I had configured with an overly locked down ICMP policy last week. That’s been fixed, and my traceroute returns to its former glory.

traceroute from azaphrael.org (69.130.198.24) to verselogic.net (142.46.152.131)
1 mdsnwigjbas01-lo0-secondary7.network.tds.net (216.165.144.1) 42.474 ms 42.416 ms 44.663 ms
2 mdsnwigjlcr51-v702.network.tds.net (216.165.156.82) 43.266 ms 43.023 ms 43.303 ms
3 rt1ec-equinix.il.shawcable.net (206.223.119.20) 46.567 ms 47.213 ms 47.261 ms
4 rd1ec-ge0-0-0.il.shawcable.net (66.163.65.17) 47.292 ms 46.978 ms 47.038 ms
5 rc1ch-pos5-0.il.shawcable.net (66.163.65.9) 47.261 ms 47.010 ms 47.251 ms
6 rc2sh-pos14-0-0.mt.shawcable.net (66.163.77.97) 58.378 ms 58.609 ms 58.306 ms
7 ra1sh-ge3-4.mt.shawcable.net (66.163.66.30) 59.118 ms 59.289 ms 59.324 ms
8 rx0sh-hydro-one-telecom.mt.bigpipeinc.com (66.244.223.246) 58.871 ms 59.804 ms 59.348 ms
9 142.46.128.6 (142.46.128.6) 120.518 ms 73.711 ms 72.327 ms
10 142.46.128.82 (142.46.128.82) 74.836 ms 74.818 ms 76.336 ms
11 142.46.130.26 (142.46.130.26) 83.516 ms 87.612 ms 84.987 ms
12 verselogic.net (142.46.152.131) 117.025 ms 121.857 ms 120.752 ms

]]> By: 8Ball http://blog.verselogic.net/archives/2005/xplornet-customer-service-found-lacking/#comment-8510 8Ball Wed, 06 Sep 2006 16:40:56 +0000 http://blog.verselogic.net/archives/2005/05/28/xplornet-customer-service-found-lacking/#comment-8510 Hey Alan ! Can't ping your IP ? Reason : Check your ICMP settings in the properties of your local area connection. You'll find it in the Advance Tab in the settings of the Windows firewall. (Or other Firewall) In other words. YOU are blocking the ping request with your firewalls. Check it out !! Hey Alan !

Can’t ping your IP ?

Reason : Check your ICMP settings in the properties of your local area connection.

You’ll find it in the Advance Tab in the settings of the Windows firewall. (Or other Firewall)

In other words. YOU are blocking the ping request with your firewalls.

Check it out !!

]]>