I have an urgent matter of the utmost importance. RED ALERT.

[DanQ]

I have received an initial reply on this from a technical support representative at ThePlanet to which I have replied; nothing substantive in either of these messages to report on.

[DrSpike]

And yet that didn't stop you reporting it.

[Nikolai]

Now, now doctor, be nice.

[DanQ]

Originally posted by DrSpike
And yet that didn't stop you reporting it.

I checked-in to note, if nothing less, than I am still following-up on this.

[DanQ]

Originally posted by Boris Godunov
Thanks, DanQ. I'm traveling until Friday, so if any action occurs and it needs testing, I won't be able to do so until at least then. Cheers.

ThePlanet has requested the following (from you, then communicated to them through me):

- A new traceroute (apparently they're displeased with the one in the opening post as it's now five days old (...));
- A ping report

[TCO]

MarkG would ask youo to do a tracert and try to blame the problem on your puter. That was back in the day

[Asher]

Originally posted by DanQ

ThePlanet has requested the following (from you, then communicated to them through me):

- A new traceroute (apparently they're displeased with the one in the opening post as it's now five days old (...));
- A ping report

That's mighty confusing. I'm not sure why the fact that it's so old matters, nor why they'd need a "ping report" considering that's a subset of the traceroute..

[Boris Godunov]

Dan, I ran a new traceroute this morning, here it is:

Tracing route to [url]www.apolyton.net[/url] [74.53.199.149]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2     6 ms     8 ms     7 ms  96.132.240.1
  3     6 ms     9 ms    13 ms  68.85.149.117
  4    31 ms     7 ms     8 ms  te-9-2-ar01.beaverton.or.bverton.comcast.net [68
.87.216.29]
  5    11 ms     9 ms    10 ms  te-0-4-0-5-cr01.portland.or.ibone.comcast.net [6
8.86.90.245]
  6    23 ms    23 ms    25 ms  pos-1-13-0-0-cr01.sacramento.ca.ibone.comcast.ne
t [68.86.85.162]
  7    34 ms    33 ms    34 ms  68.86.86.2
  8    68 ms    67 ms    68 ms  pos-0-13-0-0-cr01.dallas.tx.ibone.comcast.net [6
8.86.85.146]
  9    68 ms    68 ms    67 ms  68.86.88.50
 10    69 ms    68 ms    68 ms  te9-1.dsr02.dllstx3.theplanet.com [70.87.253.22]

 11    69 ms    70 ms    68 ms  te3-3.dsr02.dllstx2.theplanet.com [70.87.253.126
]
 12   144 ms    98 ms    69 ms  po2.car06.dllstx6.theplanet.com [12.96.160.40]
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

[Boris Godunov]

And I'm not sure what is meant by a "ping," so I'll need help there.

[Asher]

I don't know why they want one. A ping is a simple request to a server for a response. Every "hop" listed there is a ping, to each stage of the jersey. When you get a reply, you get the time it took to get the reply in milliseconds. If there is no reply, it times out.

They don't need a specific ping result since you can't connect to the server, you won't get a ping back -- as the traceroute shows.

[Dale]

Yeah that's just stupid since tracert > ping.

I suggest thePlanet hire a CCNA or someone with at least a miniscule of networking support knowledge.

[DanQ]

Originally posted by Boris Godunov
Dan, I ran a new traceroute this morning,

Noted -- thanks.

Originally posted by Dale
Yeah that's just stupid since tracert > ping.

I agree.

In any event, when you're able to post the ping report to this thread as well, Boris, I'll update the support ticket I've got open with ThePlanet on this.

[DrSpike]

Hang in there Boris, during these 'Polyless times.

I suggest we escalate this to Maroon alert.

[Asher]

Originally posted by DanQ

Noted -- thanks.


I agree.

In any event, when you're able to post the ping report to this thread as well, Boris, I'll update the support ticket I've got open with ThePlanet on this.

You have to be ****ing kidding me, Dan.

Just UPDATE IT.

The ping will NOT RESOLVE. The error he gets is HE CANNOT GET TO THE SERVER.

The traceroute even shows this.

Better yet, give me this guy's email and I'll give him a Networking 101 lecture. Christ.

[DanQ]

Originally posted by Asher


You have to be ****ing kidding me, Dan.

Just UPDATE IT.

The ping will NOT RESOLVE. The error he gets is HE CANNOT GET TO THE SERVER.

The traceroute even shows this.

Better yet, give me this guy's email and I'll give him a Networking 101 lecture. Christ.

Asher, swearing detracts from your argument greatly.

I agree providing the ping is pointless in this situation, but if I do not provide all they have requested I am certain that they will simply request it again, delaying support even further. I am working towards the path of least resistance given the communication that has already taken place.