High pings again

[Dopamine]

Same happened to me today on two different IDNet lines, each on a different exchange. Pings over 300ms on both, so dropped the PPP and tried to reconnect. Neither line would reconnect, one for well over two hours, the other for more than five minutes. This is not an isolated incident as it's happened many times before, although on those occasions reconnections usually happen within two minutes.

Pings on one line went back to 150ms+ after an hour, so this time I tried a full reboot. Synced immediately, but took 4 minutes to connect to IDNet.

Several weeks ago, totally fed up with IDNet, I requested my MAC. I received a phone call the following morning from a staff operative explaining that there would be a new hostlink arriving on the 20 something of October, that this would solve all problems and that I should reconsider moving away. Stupidly, I believed them, put on hold the use of my MAC and have put up with a terrible connection ever since, the hostlink still not active, being "tested" instead.

Never in the history of anything have I received so many empty promises from one company, and today's troubles are the end for me. Now IDNet won't be losing just one customer, me, they'll be losing two, the owner of the other line I help with too.

IDNet, don't make promises you can't keep.

[Tacitus]

....I received a phone call the following morning from a staff operative explaining that there would be a new hostlink arriving on the 20 something of October, that this would solve all problems and that I should reconsider moving away. Stupidly, I believed them, put on hold the use of my MAC and have put up with a terrible connection ever since, the hostlink still not active, being "tested" instead.....

If they said the new hostlink would 'arrive' on the 20th October (ie be delivered to them by BT) they are quite probably correct. 

What would you rather they do?  Have the hostlink delivered and then go live the same day without a period of testing?  Given the problems WBC has caused for everyone - not just iDNet - they would rightly be accused of crass stupidity. 

Looks like they can't win on this one.

[Gary]

They hoped to stary moving people early this week, that was the last message Dopamine, if you had read through a few posts you would have seen Rik's post, the new link has to be tested, you cannot transfer thousands of customers and then go "oops it went wrong, guess we should have tested it" which would method you have preferred, no testing and maybe issues or a better new connection with backup? Yes the tested route I'm sure 

[Mohux_Jnr]

 Let me guess, we would have seen high pings, connection drops and sync problems if it was not tested?.
So no change in service then.


Mac code requested today and I will bear with it another 4 days, 5 months of waiting for a resolution to high pings has come to an end for me. I am afraid I am not willing to wait for testing and teething problems. I hope the new hostlink works out for the peeps on Max and I will continue to keep an eye on proceedings in case my new ISP does not work out.
Good luck!

[Rik]

How's your dad, Mo?

[Mohux_Jnr]

Rik,
     He is fine, the last time I saw him he had just installed Win 7 and was getting everything back in working order  . His health could be better but only to be expected when you reach 126 years of age!. He will appreciate you asking and I will pass on your regards.

[Rik]

Please do.

[Fox]

My ping is pants again

Pinging idnet.com [212.69.36.10] with 32 bytes of data:
Reply from 212.69.36.10: bytes=32 time=187ms TTL=59
Reply from 212.69.36.10: bytes=32 time=192ms TTL=59
Reply from 212.69.36.10: bytes=32 time=162ms TTL=59
Reply from 212.69.36.10: bytes=32 time=193ms 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 = 162ms, Maximum = 193ms, Average = 183ms

Plus I lost service this weekend 3 times (Friday night for over 2 hours, Saturday night for over 2 hours, Sunday afternoon for about 30 mins), the router was synced but no service. I hoped it was IDNet moving me over to the host link but look at my pings today I guess not.

[Lance]

IDNet are not, automatically, moving people over to the new service. To get connected on the hostlink, you will need to restart your PPP session (or reboot your router).

After a month, anyone who hasn't reconnected and therefore still on the old central will be manually kicked off the network forcing the new session

[Simon]

Is that with immediate effect, Lance?

[Simon]

Simon has just answered my question in the hostlink announcement thread.  It seems, if you reboot your router, you should then be connected to the new hostlink, with standard ADSL connections.

[psp83]

i've rebooted mine and my pings are around 12ms now. 4ms drop from what i used to have (when it wasnt c*cking up)

time will tell tonight.

[Sebby]

[Tacitus]

Funny, I just rebooted and my pings have gone from around 30 to an average around 70/75 .....

[Rik]

Better check with support, Tac, in case something odd has happened, eg you re-connected to a central.

[Sebby]

I was just wondering, is there a way to check if we're on the new hostlink, perhaps by running a tracert?

[Rik]

I don't know, Seb, someone would have to do a before and after to see...

[Rik]

 

OK, to check if you've connected to the hostlink, do a tracert to idnet.net. If the first hop IP address ends in 101 or 102, you're on the hostlink. For WBC customers, that will be 99/100.

In theory. It doesn't seem to working though.

[psp83]

C:\Users\Paul>tracert www.idnet.net

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  www.routerlogin.com [192.168.0.1]
  2    14 ms    13 ms    13 ms  telehouse-gw2-lo1.idnet.net [212.69.63.51]
  3    13 ms    13 ms    13 ms  telehouse-gw3-g0-1-400.idnet.net [212.69.63.243]
  4    13 ms    14 ms    13 ms  redbus-gw2-g0-1-331.idnet.net [212.69.63.5]
  5    13 ms    14 ms    13 ms  redbus-gw1-fa2-0-300.idnet.net [212.69.63.225]
  6    14 ms    13 ms    14 ms  www.idnet.net [212.69.36.10]

Trace complete.

I'm not on the new hostlink then. must be everyone moving to the new hostlink giving me the better ping

[Rik]

It would appear you're not...

[psp83]

Looks like a reboot dont always move you then!

[Rik]

I've let Simon know...

[Rik]

It might be worth giving the router 5 minutes or so to ensure the PPP clears...

[psp83]

well i've gotta go turn the router off anyways, need to put a new surge protector in, the other one is not working no more!

[Simon]

Sorry, unless I'm not seeing something on my phone, I don't understand what IP address we're supposed to be looking for.