A new idnetter with slow speed problems

Started by eran, Jun 23, 2009, 22:23:25

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

eran

Hello,

I've had my idnet account for about a month, during which I've already managed to have it upgraded to ADSL2+.
The service is excellent - quick replies from support, very impressive web site and such.
Speed from the line itself was not stellar, at the very least.

Some technical details about my setup:
I use a Belkin F5D8636 (wireless N which is also ADSL2+ capable). I only have one socket in my house, so the router and phone are connected to it (using the cable and filter that came with the modem).
Speeds I sync on (from the modem's report page):
Data rate(Kbps) 3832Kb (Down) / 832Kb (Up)
Noise Margin 6 (Down) / 5 (Up)
Output power(dBm) 126 (Down) / 183 (Up)
Attenuation(dB) 68 (Down) / 33 (Up)

Trying to connect to the master socket or disconnecting the phone did not help much - all of the numbers above were within a +/- 1 range during various experiments I did. All experiments were done using the same filter (i.e. Could not connect it without a filter at all).

According to SamKnows.com, I am connected to Church End exchange (LNCED) and on a straight line distance of 2.58 km from the exchange.
I've tried the various tips in the FAQ and other sites (kitz, www.hmmm.ip3.co.uk) - aside from actually buying new modem / cables / filters.

Can I expect a higher speed at all? Is there something that can be done to the line itself (on BT's side) to improve these statistics?

On a side note, I have used cable internet connection exclusively in the past which (as a technology) gave me better user experience (in form of consistent speed, less disconnections, etc). In the UK, however, in order to use a professional ISP (which will not filter or shape your traffic) one is forced to use ADSL - as Virgin (as far as I understand) own and operate the cable infrastructure themselves. If the connectivity to the exchange and connectivity from the exchange to the Internet were forcibly separated (via regulations), people here would really benefit from being able to choose an infrastructure and a ISP - and, of course, less power to the big ISPs.

Sebby

:welc: :karma:

You must have a very long line as your attenuation is a whopping 68dB. Assuming this is being correctly reported, you're actually doing extremely well. There's absolutely no chance of doing better on a line that long I'm afraid. :)

Lance

Welcome to the forum, eran!

I'm afraid I can only echo what sebby has already said - you've a great sync for such a high attenuation and it seems unlikely there is anything you can do with the exception of trying a new router - I'm specifically thinking of the 2wire 2700hgv which many of us have found great on longer lines. Personally though I think you've already got as good as your line gets.
Lance
_____

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

Simon

AMMOI, why is Eran's 'Up' attenuation less than half of the 'Down'?

:welc:  Eran.
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Nova

Also worth checking the netgear DG834 (which I believe IDnet supply), I use one of those and they are able to hold a line in some pretty severe circumstances, however your attenuation is pretty nasty. I doubt you're going to get -much- of an improvement.

Sebby


Ray

Ray
--------------------

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

eran

Thanks everyone for the quick replies.

Sadly, I think the attenuation is correctly reported - which, as you all said, means the modem is synchronized as best as possible.
Does any of you think it'll make sense to ask BT to have the line checked? It is a long shot, as the distance from the exchange is long and all of the subscribers in this post code may be getting equally bad service.

Lance

If your line is stable without disconnects, then I wouldn't expect a BT check to turn up anything.
Lance
_____

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

Sebby

I agree. It's just a long line and there doesn't appear to be a fault.