On Tuesday 09 January 2007 18:45, Rob Malpass wrote:
> Hi all
>
> I hope this doesn't turn into a thread that spirals off in all directions
> but if someone could shed some light on this for me (a self taught
> enthusiastic amateur) I'd be grateful.
>
> Today at work, there was no web access. To the best of my knowledge,
> internet email was ok. Calling our IT guys, a recorded message said
> there was a national problem and n3 (whoever they are) and BT were working
> on it.
>
> Being the enthusiastic amateur that I am, I did a few tests from the W2k
> command line...
>
> ping www.bbc.co.uk - no packet loss
> ping www.abc.net.au - 100% packet loss
> ping www.itn.co.uk - 100% packet loss
>
> [and on all 3 occasions, it reported the IP address it was trying to ping
> so I conclude (probably incorrectly) no DNS issue]
>
> I also tried tracert www.bbc.co.uk which sometimes worked, sometimes timed
> out at hops that didn't identify themselves.
>
> Webpages looked as if they would work, but after the first few bytes e.g.
> just the google logo, they all just hung.
>
> What I don't understand is why if a website pings ok (no packet loss), we
> couldn't get at the content - clearly there wasn't an error at the server
> end.
>
> Cheers me dears
>
> Rob
Well I have justed tried pinging
www.itn.co.uk and
www.abc.net.au and neither
were accessible, there IP's were shown and their web pages were displayedable
in a browser.
Are they normally pingable (some sites block ping responses)
My ISP NTL
Tim
Send instant messages to your online friends
http://uk.messenger.yahoo.com
