Some websites timing out

[NewsreadeR]

If I ping the easynet.co.uk ip address directly I get total loss, no packets returned. If somebody could type "ping 84.38.37.38" without the quotes into the command prompt to see what they get and let me know it'd be much appreciated.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Ged>ping 84.38.37.38

Pinging 84.38.37.38 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 84.38.37.38:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\Ged>

[nevets5891]

Thanks. It's definitely not just me then. If you run tracert Sky.com - your home for the latest news, sport and entertainment does yours go through that ip?

-I hate that stupid URL thing www. sky .com no spaces.

[NewsreadeR]

Thanks. It's definitely not just me then. If you run tracert Sky.com - your home for the latest news, sport and entertainment does yours go through that ip?

-I hate that stupid URL thing www. sky .com no spaces.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Ged>tracert Sky.com - your home for the latest news, sport and entertainment

Tracing route to a1065.b.akamai.net [83.231.150.35]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms SkyRouter.Home [192.168.0.1]
2 27 ms 26 ms 26 ms cr1.lvmsx.uk.easynet.net [87.87.248.221]
3 22 ms 21 ms 22 ms 5adfb011.bb.sky.com [90.223.176.17]
4 33 ms 31 ms 31 ms ip-89-200-131-153.ov.easynet.net [89.200.131.153
]
5 29 ms 29 ms 28 ms 83.231.221.45
6 28 ms 29 ms 29 ms a83-231-150-35.deploy.akamaitechnologies.com [83
.231.150.35]

Trace complete.

C:\Users\Ged>

[nevets5891]

Thanks again. Yours didn't go through the same ip as mine when it left your exchange. So I'm gonna assume its a problem with l local node or something like that. I've heard of a few other people in East Lothian with the same problem.

[nevets5891]

Well the internet is working again. But I still get a problem when I run tracert.

C:\Users\Steve>tracert Sky.com - your home for the latest news, sport and entertainment

Tracing route to a1065.b.akamai.net [90.223.216.113]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms MyRouter.Home [192.168.0.1]
2 23 ms 22 ms 23 ms bm0.esnrb-dhcp.isp.sky.com [2.125.105.62]
3 * * * Request timed out.
4 39 ms 38 ms 39 ms ip-84-38-37-38.easynet.co.uk [84.38.37.38]
5 37 ms 37 ms 38 ms 89.200.135.53
6 37 ms 43 ms 37 ms 027ff103.bb.sky.com [2.127.241.3]
7 38 ms 37 ms 38 ms host113-rangeB-akamai-aanp.cdn.encax.isp.sky.com
[90.223.216.113]

Trace complete.


And if I ping that ip directly.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Steve>ping 84.38.37.38

Pinging 84.38.37.38 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 84.38.37.38:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

A bit strange.

[Leo_KLG]

Like you nevets my connection problems cleared up when i checked about 6 this morning. No timeout messages.

I'll try it again when i get home later and report back.

[nevets5891]

Ok. I'll do the same.

[Isitme]

Well the internet is working again. But I still get a problem when I run tracert.


1 <1 ms 1 ms <1 ms MyRouter.Home [192.168.0.1]
2 23 ms 22 ms 23 ms bm0.esnrb-dhcp.isp.sky.com [2.125.105.62]
3 * * * Request timed out.
4 39 ms 38 ms 39 ms ip-84-38-37-38.easynet.co.uk [84.38.37.38]

You are connected to the Sky Voice and Broadband network. The 84.38.37.38 address you see is a 'card' within the Sky server farm which passes you on to the easynet backbone. It will not respond to a ping request, it will just time out or give an unreachable reply. My card in the server is 89.200.128.39, if you ping this you will get the same reply. The next address down the line will respond to a ping request.

If Leo_KLG is getting Easynet for the second hop, as NR is, then your problems are not likely to be related as this indicates a connection to your local phone exchange, not direct to the server farm.

[nevets5891]

Ah right. So does that mean that anyone on the SVBN will have the timed out *** when they do tracert?

Broadband seams to be all sorted now anyway. I'd still like to know what exactly was going on.

[nevets5891]

My card in the server is 89.200.128.39, if you ping this you will get the same reply.

I just pinged this ip and got a reply. To be honest, I don't know enough about these things to work it out. I'll need to learn.