Pinging v tracert

Hi

I wonder if anyone can help me, apologies for the post length.

I was a customer of old Metronet and am still a customer of new
Metronet now owned by Plus Net. At some point during or shortly after
the assimilation of the two networks last November I suddenly found I
could no longer join a certain game server I used a lot.

I did tracert and ping as follows:

Tracing route to opt71.multiplay.co.uk [85.236.101.61]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms . [Local router]
2 * * 2348 ms ppp.adsl-17.router.parbin.co.uk
[213.162.127.192]
3 15 ms 14 ms 14 ms uk-e14-4.plusnet-y.router.parbin.co.uk
[213.162.96.62]
4 15 ms 14 ms 14 ms uk-e14-4.uk-e14-3.router.parbin.co.uk
[213.162.96.17]
5 14 ms 16 ms 15 ms lipex2.enta.net [193.109.219.57]
6 14 ms 13 ms 15 ms telehouse-east.core.enta.net
[84.45.193.195]
7 17 ms 14 ms 15 ms gi4-3.enta-transit.as35028.net
[84.45.252.122]
8 16 ms 16 ms 18 ms opt71.multiplay.co.uk [85.236.101.61]

The problem is clearly the LNS at the end of my VC (hope I have the
terms correct) according to the tracert and this is consistent over
long periods of time.

If I ping the LNS I get:

C:\WINDOWS\SYSTEM32>ping 213.162.127.192

Pinging 213.162.127.192 with 32 bytes of data:

Reply from 213.162.127.192: bytes=32 time=14ms TTL=126
Reply from 213.162.127.192: bytes=32 time=14ms TTL=126
Reply from 213.162.127.192: bytes=32 time=13ms TTL=126
Reply from 213.162.127.192: bytes=32 time=14ms TTL=126

Ping statistics for 213.162.127.192:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 14ms, Average = 13ms

This is also consistent.

Two questions really, can anyone tell me why the results for tracert
and ping are so wildly different.

Secondly can anyone tell me what PlusNet will have done to merge the
networks, I assume the LNS at the end of my VC is still where it always
was and that they have done something on the other side to move the
traffic to +net CO which I think is in Sheffield. I am guessing that
in the process of this something got screwed at the LNS but I don't
know anything about them, something has certainly been broken and as of
yet I cannot persuade Metronet/+net to fix it.

Cheers

Andy Barron

"Andy Barron" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Hi
>
> I wonder if anyone can help me, apologies for the post length.
>
> I was a customer of old Metronet and am still a customer of new
> Metronet now owned by Plus Net. At some point during or shortly after
> the assimilation of the two networks last November I suddenly found I
> could no longer join a certain game server I used a lot.
>
> I did tracert and ping as follows:
>
> Tracing route to opt71.multiplay.co.uk [85.236.101.61]
> over a maximum of 30 hops:
>
> 1 <1 ms <1 ms <1 ms . [Local router]
> 2 * * 2348 ms ppp.adsl-17.router.parbin.co.uk
> [213.162.127.192]
> 3 15 ms 14 ms 14 ms uk-e14-4.plusnet-y.router.parbin.co.uk
> [213.162.96.62]
> 4 15 ms 14 ms 14 ms uk-e14-4.uk-e14-3.router.parbin.co.uk
> [213.162.96.17]
> 5 14 ms 16 ms 15 ms lipex2.enta.net [193.109.219.57]
> 6 14 ms 13 ms 15 ms telehouse-east.core.enta.net
> [84.45.193.195]
> 7 17 ms 14 ms 15 ms gi4-3.enta-transit.as35028.net
> [84.45.252.122]
> 8 16 ms 16 ms 18 ms opt71.multiplay.co.uk [85.236.101.61]
>
> The problem is clearly the LNS at the end of my VC (hope I have the
> terms correct) according to the tracert and this is consistent over
> long periods of time.
>
> If I ping the LNS I get:
>
> C:\WINDOWS\SYSTEM32>ping 213.162.127.192
>
> Pinging 213.162.127.192 with 32 bytes of data:
>
> Reply from 213.162.127.192: bytes=32 time=14ms TTL=126
> Reply from 213.162.127.192: bytes=32 time=14ms TTL=126
> Reply from 213.162.127.192: bytes=32 time=13ms TTL=126
> Reply from 213.162.127.192: bytes=32 time=14ms TTL=126
>
> Ping statistics for 213.162.127.192:
> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 13ms, Maximum = 14ms, Average = 13ms
>
> This is also consistent.
>
> Two questions really, can anyone tell me why the results for tracert
> and ping are so wildly different.

No idea off the top of my head, but have you tried a pathping too?
IIRC, one times each hop, the other times each hop but cumulatively... er...
I forget

On 21 Apr 2006 06:07:17 -0700, "Andy Barron"
<(E-Mail Removed)> wrote:

>Hi
>
>I wonder if anyone can help me, apologies for the post length.
>
>I was a customer of old Metronet and am still a customer of new
>Metronet now owned by Plus Net. At some point during or shortly after
>the assimilation of the two networks last November I suddenly found I
>could no longer join a certain game server I used a lot.
>
>I did tracert and ping as follows:
>
>Tracing route to opt71.multiplay.co.uk [85.236.101.61]
>over a maximum of 30 hops:
>
> 1 <1 ms <1 ms <1 ms . [Local router]
> 2 * * 2348 ms ppp.adsl-17.router.parbin.co.uk
>[213.162.127.192]
> 3 15 ms 14 ms 14 ms uk-e14-4.plusnet-y.router.parbin.co.uk
>[213.162.96.62]
> 4 15 ms 14 ms 14 ms uk-e14-4.uk-e14-3.router.parbin.co.uk
>[213.162.96.17]
> 5 14 ms 16 ms 15 ms lipex2.enta.net [193.109.219.57]
> 6 14 ms 13 ms 15 ms telehouse-east.core.enta.net
>[84.45.193.195]
> 7 17 ms 14 ms 15 ms gi4-3.enta-transit.as35028.net
>[84.45.252.122]
> 8 16 ms 16 ms 18 ms opt71.multiplay.co.uk [85.236.101.61]

Migrate to Entanet and shorten the network path between you and
Multiplay ;-)

--
Address munged but valid - remove mungbeans.