IDNet maintenance - Saturday, January 12, 2008

[Adam]

All seems fine to me but we've been unable to ping any of our routers from 11am that are on idnet. Every other service seems fine.

Thanks

Theo

Welcome to the forum, Theo. I believe most of the issues have been resolved, though from the sound of it you have a custom setup. It may be worth contacting IDNet regarding your problem as I'm sure they'd be more than willing to get it resolved ASAP.

[Phil123]

When I ping www.bbc.co.uk I get destination host unreachable but I can surf the BBC site no problem.
I just pinged www.jolt.co.uk and pings seem faster if anything as does IDNet:

Pinging www.jolt.co.uk [82.133.85.65] with 32 bytes of data:

Reply from 82.133.85.65: bytes=32 time=18ms TTL=56
Reply from 82.133.85.65: bytes=32 time=18ms TTL=56
Reply from 82.133.85.65: bytes=32 time=19ms TTL=56
Reply from 82.133.85.65: bytes=32 time=19ms TTL=56

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


Pinging www.idnet.net [212.69.36.10] with 32 bytes of data:

Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=16ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59

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

[Adam]

They do seem to have calmed down now, so hopefully the problems have been sorted.

[Lance]

Hi Theo, and welcome to the forum - have a welcome karma!

[Inactive]

Welcome Theo, have a welcome Karma.. 

[Rik]

All seems fine to me but we've been unable to ping any of our routers from 11am that are on idnet. Every other service seems fine.

Hi Theo, welcome to IDNetters.

Have you contacted IDNet? If your problems are continuing, I think you need to let them know asap.

[Phil123]

I'm still getting this if I ping www.bbc.co.uk:

Pinging www.bbc.net.uk [212.58.251.203] with 32 bytes of data:

Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

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

However surfing the BBC's site is working fine and pinging other sites also works fine, so it's not causing me any problems, just thought I would post incase it indicates some other problem that IDNet might need to know about. Also even though I typed ping www.bbc.co.uk it tried to ping www.bbc.net.uk

[Rik]

That's odd, Phil. I've just got this:

ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.253.71] with 32 bytes of data:

Reply from 212.58.253.71: bytes=32 time=26ms TTL=249
Reply from 212.58.253.71: bytes=32 time=26ms TTL=249
Reply from 212.58.253.71: bytes=32 time=23ms TTL=249
Reply from 212.58.253.71: bytes=32 time=24ms TTL=249

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

It might be 2-3ms slower than usual, but otherwise it's fine. It always does the 'net' switch, btw - at least for me.

Anyone else seeing problems?

[Ann]

No problems here, fine.

[Gary]

My ping is 36ms to the bbc Rik, but no issue with things being unreachable

[cavillas]

No.  can ping everything and it all seems much snappier and faster.  They did it for me.

[Inactive]

I wouldn't know what a " ping " was if one hit me in the face Rik, but surfing is fine.

[Rik]

If one did hit you in the face, In, you might know what it was afterwards?? 

[Noreen]

I wouldn't know what a " ping " was if one hit me in the face Rik, but surfing is fine.

Ditto.

[Inactive]

Ditto.

Nice to know that I ain't alone Noreen.. 

[Rik]

Shall I tell you?

[Den]

Tell us all PLEASE Rik 

[Inactive]

Shall I tell you?

Go on then, you know you can't resist.. 

[Rik]

OK... A ping is a useful diagnostic for a connection. For example, if you are having trouble with your connection, a simple diagnostic would be to ping the router - this would quickly establish whether the computer and router are talking. From there, a ping to the BBC or other 'known good' site, can establish whether your connection is talking to the web at large.

In addition to establishing whether the connection is working, a ping tells you how fast the remote site is responding (latency). This figure is critical for gamers, they need low latency so that they can respond in a timely manner (before someone zaps them, iow ).

To run a ping test, hit Start > Run > CMD <press Enter>

that will bring up a DOS-like window.

In that, type ping www.bbc.co.uk or ping <router address>.

The results look like the post above, and can be copied by right-clicking on the title bar of the window, selecting edit, then select all, press <Enter> to copy, paste in the normal way.

[Inactive]

Thanks Rik, I am a little wiser now.

[Noreen]

Thanks Rik, I am a little wiser now.

Me too although I can'r see me ever using it.

[Rik]

As I say, Noreen, it's a useful diagnostic if you have a problem. Beyond that, I find little use for pings - I just get on and use the service.

[Simon]

Pinging www.bbc.net.uk [212.58.253.74] with 32 bytes of data:

Reply from 212.58.253.74: bytes=32 time=31ms TTL=248
Reply from 212.58.253.74: bytes=32 time=30ms TTL=248
Reply from 212.58.253.74: bytes=32 time=31ms TTL=248
Reply from 212.58.253.74: bytes=32 time=35ms TTL=248

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

[Rik]

How far are you from London, Simon? About 60 miles or a bit less?

[Simon]

From the outskirts of London, about 35 miles, Rik.