Leaving Nildram

[GarryF]

I went to http://speedtester.bt.com/ and it's giving me

Test Error
The system is currently busy. Please try again shortly, however if this problem persists, raise the issue with your service provider.

[Rik]

Sadly, that's par for the course, Garry. Try in the morning, it's usually easier then, and use IE rather than any other browser.

[Inactive]

I went to http://speedtester.bt.com/ and it's giving me

Test Error
The system is currently busy. Please try again shortly, however if this problem persists, raise the issue with your service provider.

Keep trying Garry, it showed that for me a couple of times, then magically cleared, mind you that was at around 2.00 am.

Best to try at quiet times, as Rik suggested if it will not kick in.

[GarryF]

Hah, now I see why you said "have you managed to run..." 

I'll keep trying it and post in a week or two when it finally runs

[Rik]

That's the idea, Garry.

[Sebby]

Don't give up. Patience is a virtue.

[Rik]

And her sister is a Carthusian. 

[GarryF]

Had a look on the router this morning and things are looking up

Downstream noise margin has dropped from 15dB to 6dB over the last two days on it's own?

Speed test this morning
http://www.thinkbroadband.com/speedtest/results/id/1207559054354174600.html

and making some notes of ping times before the change

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

Reply from 82.133.85.65: bytes=32 time=55ms TTL=50
Reply from 82.133.85.65: bytes=32 time=56ms TTL=50
Reply from 82.133.85.65: bytes=32 time=70ms TTL=50
Reply from 82.133.85.65: bytes=32 time=56ms TTL=50

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

Any other tests you think I can run before migrating

[attachment deleted by admin]

[Rik]

Hi Garry

The noise margin is meant to reduce automatically, it just doesn't always do it. Have you re-booted the router though, iow is that NM just after a re-sync? If not, it could actually indicate noise on the line, which would also explain why you're not synching at 8128 as I would have expected you to.

Your pings look a bit high, but that could be influenced by a number of factors.

[GarryF]

Hi Rik

I just restarted router and noise went back up to 15dB, same sync speeds as before.

I'm hoping pings might improve with idnet, we'll see tomorrow

[Rik]

Hi Garry

Your line is noisy then, and the margin has reduced from 15 to 6db due to extra noise, rather than any improvements. On a relatively short line, that shouldn't be happening, but Netgears are notorious for flaky noise reporting. Pings could well improve, they are a function of your distance from the remote server and congestion on the network. Hopefully, IDNet will sort a big chunk of that issue out.

[Sebby]

Speed is looking low given your sync, but I suspect the profile hasn't caught up. Otherwise, what Rik said.

[GarryF]

it's all been done over night, just logged in 5 mins ago and first speed test gives
http://www.thinkbroadband.com/speedtest/results/id/120763510113108523675.html

Not a bad start !

giganews goes straight up to 760kb/s, very nice !!!!

pings not much better

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

Reply from 82.133.85.65: bytes=32 time=47ms TTL=58
Reply from 82.133.85.65: bytes=32 time=51ms TTL=58
Reply from 82.133.85.65: bytes=32 time=55ms TTL=58
Reply from 82.133.85.65: bytes=32 time=52ms TTL=58

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

[Lance]

Those higher pings are likely to be because of Interleaving being turned on for your line. Once we have established why your noise margin swings by so much, and the source of the noise, we might be able to put a case together to persuade BT to turn it off.

What are your latest line stats?

[Rik]

Hi Garry

Glad the migration went smoothly. What Lance said...

[Sebby]

Ditto.

[GarryF]

Hi Lance

I'm at work now, from memory sync was a little higher at over 7500, other stats were the same, I'll check tonight when I get home and see how they look

Ping doesn't bother me much, I'm not doing any online fps etc, I'd far rather have a stable line that downloads at 1MB/s when I ask it 

I'd noticed VPN into my work server had been pretty ropey as well over the last few months, will be nice to see if this is a bit more stable now, and I only did the face plate on Saturday so things might get faster yet

Overall I'm delighted, thanks for all the help guys !!!

[Rik]

NP. Welcome to our happy band.

[Danni]

Welcome to IDNet I'm sure the people here will get your line as close to perfection as possible.

[Malc]

Welcome to IDNet I'm sure the people here will get your line as close to perfection as possible.

However, your sanity...

[Rik]

 

For that we give no guarantees.

[GarryF]

I'm probably not sane anyways 

attached is current stats from the router, router was set to dial on demand instead of always on from this morning when I ran through wizard, so it's been connecting a few times today.

I'll try rebooting the router later when the other half isn't online 

giganews is still a rock solid 760kb/s just now in the evening

[attachment deleted by admin]

[Rik]

7616 is the theoretical maximum speed for an interleaved line, Garry and will result in a profile of 6500. It would be worth keeping an eye on the error count and, if it stays low and the line stays stable, try with interleaving off (ask support to turn it off). For best speeds, re-boot the router in the morning. For best stability, re-boot it at night.

[Sebby]

Isn't it a 7000 profile on an interleaved line at full sync?

[Rik]

Thanks, Sebby, helps if I don't type the sync speed twice.