test ping

Hi ppl looks like I will be leaving nildram soon.
Need a nice new isp could anybody here ping this server for me let me see a tracert. ??

194.50.80.22:12202

Thanks.

C:\WINDOWS>tracert 194.50.80.22

Tracing route to 194.50.80.22 over a maximum of 30 hops

1 3 ms 1 ms <10 ms 192.168.1.1
2 13 ms 13 ms 13 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 14 ms 15 ms 15 ms telehouse-gw-bb.idnet.net [212.69.63.9]
4 15 ms 15 ms 16 ms lonap2.enta.net [193.203.5.135]
5 14 ms 14 ms 15 ms te4-1.telehouse-north.core.enta.net [87.127.236.38]
6 15 ms 15 ms 14 ms 84-45-244-74.no-dns-yet.enta.net [84.45.244.74]
7 15 ms 15 ms 15 ms 194.50.80.22

Trace complete.

Thanks Billford that looks gr8
Well hello to nildram for mac code tommorow.
I think idnet has a new customer

This is what I am getting now with nilly

Tracing route to 194.50.80.22 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 46 ms 45 ms 45 ms l1.ar20.gs1.dsl.pipex.net [195.112.5.29]
3 48 ms 34 ms 27 ms ge-1-0-1-0.cr02.gs1.dsl.pipex.net [84.12.224.29]

4 49 ms 26 ms 54 ms pc9.cr05.tn5.bb.pipex.net [62.72.137.13]
5 42 ms 26 ms 80 ms ge-1-5-0-cr0.thn.datahop.it [62.72.139.106]
6 52 ms 44 ms 40 ms 195.72.128.222
7 70 ms 63 ms 41 ms 62.149.39.2
8 47 ms 53 ms 48 ms 194.50.80.22

I used to get to this server in 4 hops geees pipex ty

Edited by SHUG (Mon 16-Oct-06 01:28:04)

welcome Shug - good coice ;0)

Pinging www.idnet.net with 32 bytes of data:
Reply from 212.69.36.10 bytes:32 Time:30ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:29ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:31ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:32ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:33ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:34ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:29ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:41ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:34ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:30ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:33ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:35ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:38ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:35ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:34ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:36ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:32ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:40ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:33ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:30ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:31ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:30ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:32ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:44ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:30ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:31ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:31ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:33ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:30ms TTL:60
Reply from 212.69.36.10 bytes:32 Time:30ms TTL:60

Ping statistics for www.idnet.net :

Packets: Sent = 30, Received = 30, Lost = 0 (0%) loss),
Approximate round trip times in milli-seconds:
Minimum = 29ms, Maximum = 44ms, Average = 33ms

Edited by idnetuser (Mon 16-Oct-06 19:32:38)