Idnet ping times of late a general question from a hopefully returning customer

Started by MarkE, Apr 03, 2009, 14:08:31

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

MarkE

Please if I have posted this in the wrong section,feel free to move it.

I left Idnet about 2 months ago? or thereabouts as at the time with the extra  bandwidth Idnet had purchased,there was a lot of ping time problems for gamers,I have recently been emailed by
Multiplay adsl my current provider and they tell me I need to find a new Isp as they are shutting down their service as of April 20th.

Now my question to everyone here is,has the ping time problems been resolved? As I would like to renew my partnership with idnet (ooooh errr)  :red:

Rik

I am seeing pings of 19-24ms to IDNet, with occasional higher spikes, Mark. Across a day, my average will be 22ms or thereabouts.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Steve

No complaints lately on the forum,myself can't complain either
PING www.idnet.net (212.69.36.10): 56 data bytes
64 bytes from 212.69.36.10: icmp_seq=0 ttl=59 time=17.262 ms
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=17.258 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=17.779 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=16.968 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=14.657 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=17.612 ms
64 bytes from 212.69.36.10: icmp_seq=6 ttl=59 time=17.011 ms
64 bytes from 212.69.36.10: icmp_seq=7 ttl=59 time=18.027 ms
64 bytes from 212.69.36.10: icmp_seq=8 ttl=59 time=17.782 ms
64 bytes from 212.69.36.10: icmp_seq=9 ttl=59 time=17.785 ms

--- www.idnet.net ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 14.657/17.214/18.027/0.918 ms
Steve
------------
This post reflects my own views, opinions and experience, not those of IDNet.

MarkE

Thanks for the replies guys,looking good  ;D I guess I will put in an order shortly then.


Maverich

Quote from: MarkE on Apr 03, 2009, 14:08:31
I left Idnet about 2 months ago? or thereabouts as at the time with the extra  bandwidth Idnet had purchased,there was a lot of ping time problems for gamers,
  :red:

Just thought i'd mention, only been with Idnet for a few days but I do a lot of online gaming, haven't had any problems what so ever!  ;D

Rik

I've just done this ping:

ping www.idnet.net -n 10

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

Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=20ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=21ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59
Reply from 212.69.36.10: bytes=32 time=19ms TTL=59
Reply from 212.69.36.10: bytes=32 time=23ms TTL=59
Reply from 212.69.36.10: bytes=32 time=24ms TTL=59

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

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

jameshurrell

Looking excellent for me:

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

Reply from 212.69.36.10: bytes=32 time=14ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60
Reply from 212.69.36.10: bytes=32 time=13ms TTL=60

Ping statistics for 212.69.36.10:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:
Minimum = 13ms, Maximum = 14ms, Average = 13ms

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Maverich

I'm very jealous  :bawl:

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

Reply from 212.69.36.10: bytes=32 time=39ms TTL=59
Reply from 212.69.36.10: bytes=32 time=37ms TTL=59
Reply from 212.69.36.10: bytes=32 time=35ms TTL=59
Reply from 212.69.36.10: bytes=32 time=36ms 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 = 35ms, Maximum = 39ms, Average = 36ms

Still better then previous Isp  ;)

Rik

Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.


Rik

About double my distance, so that will slow things a bit. Do you know if your line is interleaved?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Maverich

I'm really not sure to tell you the truth, how easy is it to find out?

Rik

It usually tells you in your router - what are you using, was it a Netgear?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Maverich


Rik

OK, I just checked, you are interleaved, although it's set to auto, so the BT software has detected some instability or errors and used interleaving to stabilise the line. Support can get it turned off for you, just email them, but there's a risk that the line may become unstable and it will just revert to on. Have we taken you through the ring wire bit (sorry, but I ask so many times, I tend to forget...  :blush:).
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Maverich

No I haven't been taken through the ring wire but have heard about it.  I hope it's straight forward enough  :fingers:

I did have quite a few problems on my line when connected with Sky as my noise margin kept dropping out so I was advised to keep rebooting the router until it maintained a higher margin.  Could that of caused interleaving to be triggered?

Rik

It could, and to be honest, it was bad advice. Do you have an NTE5 mastersocket, the type where the bottom part of the faceplate can be removed? How is the router connected, to the master socket, a hard-wired extension, or using a 'loose' extension lead?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Maverich

No I dont have a NTE5 mastersocket in fact It isn't really feasible to use my mastersocket as this is located in a separate building which is located 1 door down to where I actually live (I live in a converted barn hence the odd place).  The extensions are both hard wired.

Rik

OK, can you get at the master? If so, unscrew the faceplate and gently pull out the wire from terminal 3, usually it's orange/white. You only want a connection on terminals 2 & 5, and they should be a pair, eg blue/white & white/blue. Repeat the exercise at each socket. We often see almost miraculous improvements in speed and stability with this technique. It won't stop your phones ringing, the microfilters generate the ring voltage.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Maverich

Yes I can get at the socket.  I'll try and give that a go now and post back with any findings.  Thanks Rik.

Rik

If there's anything on terminal 4, that can safely be removed, just roll up the wire(s) and put a bit of tape round them. :)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Maverich

Ok just checked the master socket and on terminals 2 & 5 were connected.  Should I checked the extensions as well?

Rik

Yes. Even if the wire is only connected at one end, it acts as a giant antenna and drags noise into the system.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Maverich

Ok I had two extensions and both of which had a wire in terminal 3, these have now been taken out.  Whats the best way to check to see if this was havin an effect on the connection?