Hello ppl 3Dbully here,
Just gone through the signup process, looking forward to having a decent isp again.
Migrated from Pipex/Tiscali because the service just got worse and worse.
Which is a shame cos Pipex were a good company.
Shall pop by when my IDnet connection is live.
Opp's think i may have posted in the wrong area, apologies in advance.
Welcome to IDNet :karma:
Quote from: Glenn on Oct 01, 2008, 14:20:02
Welcome to IDNet :karma:
Cheer's Glenn...And thank's for the KARMA!
:welc: :karma:
IDNet will be a breath of fresh air. :)
:karma: and :welc:
Welcome aboard, 3D, here's as good a place as any. :welc: :karma:
:welc: :karma:
:welcome: Hope you find the service as good as we do! :thumb:
Hi there 3D, I am sure you will be happy here :welcome:
Well thank's for the wellcome ppl.
I hope i'm going to have a nice broadband experience with IDnet, as i'm migrating from Pipex/tiscali :eek4:
Who were a good ISP before a very nice company bought them out!
I spent a few months scoping out all ISP's in the uk, and decided on IDnet based on the info from thinkbroadband etc.
Looking forward to having priority over other ADSL traffic/user's in my town.
And having a nice stable connection which doesn't get bandwith profiled 3 times a day. :no:
Regards
3DBULLY
The stability is down to the quality of your line, 3D. There's very little an ISP can do to influence it, unfortunately, though some are better at getting BT to fix any faults than others. :fingers:
Quote from: Rik on Oct 05, 2008, 12:25:15
The stability is down to the quality of your line, 3D. There's very little an ISP can do to influence it, unfortunately, though some are better at getting BT to fix any faults than others. :fingers:
Maybe my BRAS profile is/was messed up ? not to sure!.... all i know is roughly 3 times a day at roughly the same time my sync rate would change. :notfair:
Hoping all this will change during the 10 day training period.
Will see, i shall keep you informed of thing's at my end after the 10 day's.
Regard's
3DBULLY
Well if it was, that would be to do with line instability. Anyhow, once you're on IDNet, we can get hold of your line stats and see how things are looking.
Incidentally, there won't be another training period as you're migrating.
Hi 3D Bully and welcome to Idnetters you should be happy here I came over a while ago from that dark place
:karma: :beer1: see you in the bar ;)
Quote from: 3DBULLY on Oct 05, 2008, 13:47:03
Maybe my BRAS profile is/was messed up ? not to sure!....
Run at BT speed test, http://test.speedtester.bt.com:50301/, that will tell us what your profile is. If you can also post your d/s attenuation and noise margin, we can take a guess at what might be happening.
Quote from: Sebby on Oct 05, 2008, 13:56:12
Well if it was, that would be to do with line instability. Anyhow, once you're on IDNet, we can get hold of your line stats and see how things are looking.
Incidentally, there won't be another training period as you're migrating.
That's a shame about the Line Retrain as i thought it might clear my BRAS profile and was hoping for the upstream connection speed to go up from 448kbps plus i'm positive that Pipex/Tiscali had me on interleaved, just suffer ADSL resync's about 3 times a day. ???
Before Tiscali bought pipex i had a very stable ADSL experience and after that's when thing's got worse.
I've had a new phoneline put in buy BT at there expense after one off there building anchor point's came away and said cable was damaged due to it rubbing up and down on the corner of the house, also had an ADSL NTE5 openreach faceplate fitted, plus the engineer tested the line from test socket on the nte5 to the pole just outside the boundary of my garden, then from the pole to the street termination box and from there to the exchange.(NTE5 to exchange distance 330mtr)
He said that his laptop via the test faceplate was syncing at 8100+kbps(can't remember exact figure) and would give me a profile around 7100kbps, i get close to 7100kbps sync.
From the exchange he phoned me and and said there was some resistance on the line which he found strange and apparently moved my line from one psychical location to another which solved the issue.
I must have had one of the nicest BT engineers ever!.....lucky.....Might of had something to do with the fact that whilst chatting to him i mentioned that i admin for EA on there game servers and that i needed a good stable connection to do my job.
Still have the 3 resync's roughly every day! Which is strange :comp:
Regard's
3DBULLY
Your setup sounds good (NTE5, etc) so I think there must be a line problem. Have a word with IDNet and see what they say.
Can you post your stats, 3D, that might give us a clue?
Ok rik, shall do.....
ADSL Link
Downstream
Upstream
Connection Speed
7040 kbps
448 kbps
Line Attenuation
12.0 db
6.5 db
Noise Margin
14.0 db
23.0 db
Bt speedtest busy error...Shall try again later.
Oh..by the way IDnet isnt live untill Mon 6th 6pm.
With attenuation of 12dB, you should achieve full sync easily, and you really shouldn't be having any stability issues. You're not getting full sync at the present time because of the increased SNRM, but there is an underlying factor that's causing this.
I would give IDNet a call and see what they say. Perhaps point them to this thread.
New line stat's:-
Now using idnet as of 2:20am
ADSL Link Downstream Upstream
Connection Speed 6400 kbps 448 kbps
Line Attenuation 12.0 db 6.5 db
Noise Margin 15.1 db 22.0 db
Because of migration to IDnet no line training has been done!
Was looking to have a better upstream speed!, i'm on the Home supermax package.
Still think my BRAS profile could be at fault, and i'm sure interleaving mode is on.
I would give IDNet a call as your upstream should be 768k.
Incidentally, the stats are worse than those you posted previously probably because you re-sync'd at 2.20am, when there is the most noise around.
Check with support that you've been put on SuperMax, 3D. That looks like a standard Max migration to me. Sync speed is not affected by your profile, but is affected by the target noise margin, and yours appears to have been set at 12-15db (or it has risen since the line connected in the small hours).
BT speedtest info.
Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 6720 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 2000 kbps
Actual IP throughput achieved during the test was - 1865 kbps
Yes sebby that's the problem with migrating no retrain of the line.
Should i give IDnet a call now ?
More line stat's DSL dropped whilst i was about to use the BT speedtest.
ADSL Link Downstream Upstream
Connection Speed 6720 kbps 448 kbps
Line Attenuation 12.0 db 6.5 db
Noise Margin 15.9 db 22.0 db
You've got a stuck profile, which is common when you migrate from a fixed product to Max. That'll clear by itself (and is the reason your throughput is low at the moment).
I still think that, for a 12dB line, you should get full sync. What's your setup like? Could you try plugging the router into the test socket (http://www.readman.dsl.pipex.com/other/UKphonecatwiring_files/image012.jpg) (if you have an NTE5, remove the lower half and plug the router into the socket behind the plate).
I would also call IDNet about the upload; to me it doesn't look like you're on SuperMax.
On the phone to support now!
Simon at support said that there is currently no profile assigned to my line so BT haven't quite finished the migration job, he recommends leaving everything until tomorrow before raising it with BT.
Which i think is a very valid point!....
So will shall see how thing's are tomorrow...... :P
Let us know how it goes. :thumb:
Well do sebby and rik.
Router DG834n :Rock solid no problems what so ever.
Yuck...Speedtest.net result's, hope this improves for tomorrow.
Yeah I had a stuck profile too when I migrated. I hit 830KB/s straight off as soon as BT pushed the right button.
It's weird the way BT put on the 2000 profile despite their being no line retraining. :shake:
It saves bandwidth on those who don't happen to notice.
[/cynic]
Ahem!
You might think that... ;D
Quote from: Rik on Oct 06, 2008, 15:52:22
It's weird the way BT put on the 2000 profile despite their being no line retraining. :shake:
Indeed. Another BT stupidity. :P
Quote from: Rik on Oct 06, 2008, 15:52:22
It's weird the way BT put on the 2000 profile despite their being no line retraining. :shake:
Hmmmm....yeah i see what you mean, well 6pm this evening is when the migration was supposed to conclude.
I shall do a router reboot at 6:15pm see what i sync at, and do another BT speedtest. :thumb:
It's already complete, I can see you're on an IDNet connection. :)
Well woke up this afternoon(i work night's) and the BT speedtest is telling me:
Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 6560 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 2000 kbps
Actual IP throughput achieved during the test was - 1869 kbps
If you wish to discuss these results please contact your ISP.
So no change there, can somebody explain to me why if migrating somebody stated that there is no 10 day line training period for migration is this true.
As somebody at support has told me there is a 10day line training, and would be finished on the 16th Oct.
Can somebody clarify this?, as im still stuck at the 2K profile?, plus my up speed is still on the Max product.
Regards
3DBULLY
I came from Tiscali/Pipex datastream and went through a training process.Looks like your stuck on the 2000 profile ,I presume if it doesn't change soon contact idnet so they can give BT a kick.
There's no training period, but when you migrate from a fixed-rate product to IPStream Max, the profile stays at 2000k for a couple of days. Honestly, it'll shift within a few days. If it doesn't, IDNet can ask BT to update it manually.
I still think there's a problem, 3D, and that BT haven't put you on SuperMax. I'd have another word with support.
Rik,
i have been onto support again this time i talked to a guy called james, i have sent IDnet a e-mail with 2 BT speedtests show that i'm stuck on the 2k profile, and my router stat's.
Waiting....... :whistle:
James knows his stuff, as do they all. I'm sure it will be sorted soon. :)
Update: I live and learn, migrations now produce a re-train (I swear they didn't use to!), and hopefully your line will wake up to the fact it's on SuperMax shortly.
Well you learn something new every day! :o
Quote from: Rik on Oct 07, 2008, 14:02:33
James knows his stuff, as do they all. I'm sure it will be sorted soon. :)
Update: I live and learn, migrations now produce a re-train (I swear they didn't use to!), and hopefully your line will wake up to the fact it's on SuperMax shortly.
Yeah that's why i rang support twice, because the first time i phoned they said 10days to retrain the line, i then went to the IDnet site and checked the migration detail's, then phoned support again to clarify the retrain question.
Ho hum......waiting....... :whistle:
Currently still no change still stuck at the 2k profile, Can't see any sign of the line retraining!
Still on my old Pipex max product......Fnar!
Router Stat's :
ADSL Link Downstream Upstream
Connection Speed 7072 kbps 448 kbps
Line Attenuation 12.0 db 6.5 db
Noise Margin 14.7 db 24.0 db
Still i can't raise any support issue on this until the 10 day line retraining period is over.....Which there are no tell tail sign's of the line being retrained!.....Waiting patiently..... :notfair:
Retraining ends on the 16th of this month.
Blame BT. :(
It will hopefully lift before the 10 days are up, though. :fingers:
Well it's the 15th today, line retraining is finished tomorrow of which i haven't seen any sign's of line retraining at all, I'm still on my pipex max product, which I'm sure has a messed up BRAS.
Can't wait for tomorrow as I'm going to be on the phone to support right away with my BT speedtest as ammo to get them to kick BT into action, Yes still on the 2k profile.
Router stat's at the moment :
ADSL Link Downstream Upstream
Connection Speed 6720 kbps 448 kbps
Line Attenuation 12.0 db 6.5 db
Noise Margin 14.9 db 22.0 db
The same stat's i have allways had on pipex max, oh interleaving is on. :rant2:
Regards
3DBULLY
Update: BT speedtest @ 15:02 pm
Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 6720 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 2000 kbps
Actual IP throughput achieved during the test was - 1882 kbps
I'm convinced that BT have failed to move you to the SuperMax product. This 10-day rule is a total PITA. >:(
I agree. You're not on SuperMax as far as I can see, but unfortunately BT wouldn't have listened to IDNet until the end of the training period anyway, so hopefully tomorrow you can get the sync and profile sorted. :fingers:
Well the ten day's of apparent line training is over, Phoned IDnet support they are going to now raise the issue with BT, as i'm still on the pipex max product and not on my IDnet SuperMax product.
Today's BT speedtest :
Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 6368 kbps(DOWN-STREAM), 448 kbps(UP-STREAM)
IP profile for your line is - 2000 kbps
Actual IP throughput achieved during the test was - 1868 kbps
Router Stat's :
ADSL Link
Downstream
Upstream
Connection Speed
6368 kbps
448 kbps
Line Attenuation
12.0 db
6.5 db
Noise Margin
14.0 db
22.0 db
Waiting still....... :rant2: :whistle:
Regards
3dbully
If ever there was a stuck profile, you have it 3D. :(
Its daft, how can you train a line on a stuck profile ???
You can't, Steve, it's a BT cop out. :(
Idnet support must have got through to BT as they must have hit the button, as i'm now showing sign's of being on my IDnet Super Max product!...... :tongue:
Router Stat's :
ADSL Link Downstream Upstream
Connection Speed 6368 kbps 832 kbps
Line Attenuation 12.0 db 6.5 db
Noise Margin 13.8 db 12.0 db
Showing the right down speed for Super Max! :tongue:
Bt Speedtest : to follow.
Regards
3dbully
P.s i think that my downstream should pick up in the next few day's, i also asked for interleaving to be turned off.
The profile should now follow, 3D. :thumb: Though I'm surprised you haven't got an 8192 sync.
Quote from: Rik on Oct 16, 2008, 17:33:18
The profile should now follow, 3D. :thumb: Though I'm surprised you haven't got an 8192 sync.
Yeah Rik i'm also suprised maybe things will improve in the next few day's!.....touch wood!
Remind me what your internal phone wiring is like will you, ie how many sockets, what's connected to them.
Well i have a brand new phone line from master socket (Openeach ADSL filtered face plate NTE5) to the mast, no extensions fitted, i'm on the master socket with my DG834n adsl router.
Do you need more info?
No, that's fine. There's no obvious explanation for that sync speed except a noisy line (in ADSL terms) or environment. When did you re-sync (morning, afternoon or evening)?
Routerstats shows : resync at 4:25pm and 4:32pm, dont know how to attach image.
That's OK, 3D. I gather your stats may be a bit odd for a day or so due to BT's manual intervention. Try re-syncing the router on Saturday morning and see what you get then.
Will do rik, looking forward to having a better sync rate..... :fingers:
P.s b 4 resync:
Thu 16 Oct 2008 16:23:43 **.***.*.** Rx-Noise= 14.3 Tx-Noise= 22 Rx-Sync= 6368 Tx-Sync= 448
After rysync:
Thu 16 Oct 2008 16:29:43 **.***.*.** Rx-Noise= 14.1 Tx-Noise= 10 Rx-Sync= 6272 Tx-Sync= 832
Slight drop in sync!?
Nothing to worry about, most people see a few K of change whenever they re-sync. Hopefully, it will resolve and your sync will move towards 8192. If it doesn't, and the NM immediately after a re-sync stays at 12db or more, it would be worth talking to IDNet as that would suggest that your target NM has been increased. 6db would cost you 1000-1400k, which fits the speed you are seeing. If you can borrow an alternative router, you might see an improvement.
I'm glad this is now sorted. :thumb:
Quote from: Sebby on Oct 16, 2008, 19:02:52
I'm glad this is now sorted. :thumb:
Cheers Sebby and Rik, No quite there yet...as the Bt Engineer said from my NTE5 adsl faceplate he was syncing at 8192kbps and i should have a BRAS of 7100k if i remember correctly.
Is the DG834n a bit flaky or what....?
Just wondered why Rik suggested to try a different router!
I'm very aware that different routers might be able to get more out of my line but i think i will leave it for 2 to 3 day's and see what i sync at.
When i had my pipex product(before that other company bought them out :eyebrow:) i was syncing at 8192 with a profile of 7100k, at somepoint some so 'n' so turned on interleaving when there was a problem at the street termination box(instead of fixing it they just hit the interleaving button, Must of been wet outside ;D), which was duly sorted, during this saga the other company bought pipex and the other company said that turning interleaving off was not a customer option.
And that's where i have been stuck eversince....up until now.
Regards
3dbully
what firmware you running on the DG834N 3D?
I always thought the max sync was 8128 for adsl? DG834N is v.good on my short line
Quote from: 3DBULLY on Oct 17, 2008, 04:46:47
Is the DG834n a bit flaky or what....?
Netgears can be susceptible to noise, 3D. Moving to a 2700 gave me an extra 1000k of sync.
Yeah 8128kbps, soz just was working from memory.
DG834n Firmware is 1.02.08
If you guy's have any hints on tweaking the DG834n in anyway please let me know, isnt there some guy's that do a modified firmware? is it any good give me a heads up is possible.
I'm 330mtrs from exchange, line distance.
There are some tweaked firmwares around, but you really shouldn't need anything on your line, 3D.
That's good to hear rik, speedtest.net is showing me this afternoon at 3:02pm, that i have gained another 416kbps on my down speed throughput.
I still think interleaving might be on, i don't want to hassle support at the moment, i'm of to london on monday and won't be back until thursday night, i shall see how my line stat's are then.
And if nessesary phone support to see if they managed to get BT to turn off interleaving.
Regards
3dbully
p.s router stat's is showing me that i had a resync about 5:30 mins ago.
If you can do a BT test, that will show us your profile, which may give a clue on interleaving. Otherwise, IDNet could tell you.
Bt Speedtest result :
Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 6304 kbps(DOWN-STREAM), 832 kbps(UP-STREAM)
IP profile for your line is - 6000 kbps
Actual IP throughput achieved during the test was - 5209 kbps
Router Stat's :
ADSL Link
Downstream
Upstream
Connection Speed
6304 kbps
832 kbps
Line Attenuation
12.0 db
6.5 db
Noise Margin
15.9 db
10.0 db
The profile is higher than it should be for your current sync speed, 3D, so it will probably drop in the next hour or so. The fact that it is suggests your line is unstable. Is the Netgear logging loss of LCP?
Sorry rik you have lost me there LCP?, how do i find that info on my router ?
Log into the router interface, on the menu at the left, there's a heading logs. Click on that and it should reveal the information you need. (LCP is link control protocol.)
Sorry rik bit of a numbskull today, looked at log's no mention of LCP at all, but in saying that the log is very small in size.
Can you cut and paste the contents, 3D? Later Netgear firmware did stop logging drops, so the other thing to check is the WAN uptime shown on the stats page.
Here you go.....
Fri, 2008-10-17 10:34:06 - TCP Packet - Source:212.57.230.141,64663 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 10:50:10 - TCP Packet - Source:212.57.230.141,19356 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 10:59:54 - TCP Packet - Source:118.171.71.109,52447 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:00:09 - TCP Packet - Source:118.171.71.109,52470 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:05:14 - TCP Packet - Source:212.57.230.141,21404 Destination:,54804 - [Azureus rule match]
Hmmm... yeah bit of p2p there lol
Fri, 2008-10-17 11:20:47 - TCP Packet - Source:212.57.230.141,13717 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:32:00 - TCP Packet - Source:79.94.63.27,56308 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:32:09 - TCP Packet - Source:79.94.63.27,56351 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:33:54 - TCP Packet - Source:79.94.63.27,57173 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:34:03 - TCP Packet - Source:79.94.63.27,57261 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:36:12 - TCP Packet - Source:212.57.230.141,28309 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:37:10 - TCP Packet - Source:82.47.45.152,3615 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:37:16 - TCP Packet - Source:79.65.72.108,56402 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:37:16 - TCP Packet - Source:79.65.72.108,56912 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:39:17 - TCP Packet - Source:79.94.63.27,57866 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:39:17 - TCP Packet - Source:79.94.63.27,57867 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:39:26 - TCP Packet - Source:79.94.63.27,57879 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:39:26 - TCP Packet - Source:79.94.63.27,57880 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:41:37 - TCP Packet - Source:79.65.72.108,57202 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:42:27 - TCP Packet - Source:79.94.63.27,58087 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:42:36 - TCP Packet - Source:79.94.63.27,58102 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:48:47 - TCP Packet - Source:79.94.63.27,58812 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:48:56 - TCP Packet - Source:79.94.63.27,58881 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:49:08 - TCP Packet - Source:79.94.63.27,58994 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:49:17 - TCP Packet - Source:79.94.63.27,59079 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:50:37 - TCP Packet - Source:212.57.230.141,38045 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:53:03 - TCP Packet - Source:79.94.63.27,59436 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:53:03 - TCP Packet - Source:79.94.63.27,59437 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:53:12 - TCP Packet - Source:79.94.63.27,59450 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:54:48 - TCP Packet - Source:79.94.63.27,59630 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:54:57 - TCP Packet - Source:79.94.63.27,59659 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:58:13 - TCP Packet - Source:78.86.139.14,58224 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:58:17 - TCP Packet - Source:78.86.139.14,58233 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:58:20 - TCP Packet - Source:78.86.139.14,58246 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:58:24 - TCP Packet - Source:78.86.139.14,58259 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:59:25 - TCP Packet - Source:79.94.63.27,59952 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:59:25 - TCP Packet - Source:79.94.63.27,59953 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 11:59:34 - TCP Packet - Source:79.94.63.27,59963 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:02:45 - TCP Packet - Source:79.94.63.27,60223 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:02:55 - TCP Packet - Source:79.94.63.27,60236 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:05:45 - TCP Packet - Source:212.57.230.141,45469 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:09:16 - TCP Packet - Source:79.94.63.27,61204 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:09:16 - TCP Packet - Source:79.94.63.27,61205 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:09:25 - TCP Packet - Source:79.94.63.27,61214 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:09:25 - TCP Packet - Source:79.94.63.27,61215 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:12:03 - TCP Packet - Source:79.94.63.27,61352 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:12:12 - TCP Packet - Source:79.94.63.27,61364 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:12:23 - TCP Packet - Source:79.94.63.27,61369 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:12:32 - TCP Packet - Source:79.94.63.27,61385 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:13:06 - TCP Packet - Source:77.97.91.228,64345 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:14:53 - TCP Packet - Source:79.94.63.27,61537 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:19:27 - TCP Packet - Source:79.94.63.27,61860 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:19:27 - TCP Packet - Source:79.94.63.27,61861 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:19:36 - TCP Packet - Source:79.94.63.27,61973 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:20:33 - TCP Packet - Source:212.57.230.141,41110 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:22:14 - TCP Packet - Source:79.94.63.27,62636 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:22:23 - TCP Packet - Source:79.94.63.27,62643 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:26:59 - TCP Packet - Source:77.97.91.228,63923 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:28:43 - TCP Packet - Source:79.94.63.27,63016 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:28:43 - TCP Packet - Source:79.94.63.27,63017 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:28:51 - TCP Packet - Source:79.94.63.27,63026 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:28:51 - TCP Packet - Source:79.94.63.27,63027 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:31:58 - TCP Packet - Source:79.94.63.27,63184 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:32:07 - TCP Packet - Source:79.94.63.27,63191 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:32:11 - TCP Packet - Source:79.94.63.27,63195 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:32:20 - TCP Packet - Source:79.94.63.27,63205 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:34:04 - TCP Packet - Source:79.94.63.27,63374 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:34:49 - TCP Packet - Source:212.57.230.141,41110 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:39:06 - TCP Packet - Source:79.94.63.27,64186 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:39:06 - TCP Packet - Source:79.94.63.27,64187 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:39:15 - TCP Packet - Source:79.94.63.27,64193 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:39:15 - TCP Packet - Source:79.94.63.27,64194 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:41:44 - TCP Packet - Source:79.94.63.27,64366 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:41:53 - TCP Packet - Source:79.94.63.27,64374 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:47:59 - TCP Packet - Source:79.94.63.27,64977 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:48:17 - TCP Packet - Source:79.94.63.27,65082 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:48:26 - TCP Packet - Source:79.94.63.27,65150 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:49:17 - TCP Packet - Source:212.57.230.141,28318 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:51:29 - TCP Packet - Source:79.94.63.27,49248 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:51:30 - TCP Packet - Source:79.94.63.27,49249 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:53:55 - TCP Packet - Source:79.94.63.27,49381 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:54:04 - TCP Packet - Source:79.94.63.27,49391 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:58:45 - TCP Packet - Source:82.47.45.152,4954 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:58:57 - TCP Packet - Source:79.94.63.27,49706 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:58:57 - TCP Packet - Source:79.94.63.27,49707 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 12:59:55 - TCP Packet - Source:118.171.71.109,53953 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:00:10 - TCP Packet - Source:118.171.71.109,53970 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:01:58 - TCP Packet - Source:79.94.63.27,49959 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:02:04 - TCP Packet - Source:79.94.63.27,49964 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:05:15 - TCP Packet - Source:212.57.230.141,34974 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:08:22 - TCP Packet - Source:79.94.63.27,50937 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:08:28 - TCP Packet - Source:79.94.63.27,50953 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:09:00 - TCP Packet - Source:79.94.63.27,50974 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:12:48 - TCP Packet - Source:79.94.63.27,51179 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:12:48 - TCP Packet - Source:79.94.63.27,51180 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:12:57 - TCP Packet - Source:79.94.63.27,51187 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:14:54 - TCP Packet - Source:79.94.63.27,51299 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:15:03 - TCP Packet - Source:79.94.63.27,51306 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:19:45 - TCP Packet - Source:79.94.63.27,52253 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:19:54 - TCP Packet - Source:79.94.63.27,52252 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:19:54 - TCP Packet - Source:79.94.63.27,52263 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:19:55 - TCP Packet - Source:212.57.230.141,18071 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:23:00 - TCP Packet - Source:79.94.63.27,52461 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:23:06 - TCP Packet - Source:79.94.63.27,52473 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:23:07 - TCP Packet - Source:77.97.91.228,65055 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:29:05 - TCP Packet - Source:79.94.63.27,52842 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:34:24 - TCP Packet - Source:212.57.230.141,31127 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:50:00 - TCP Packet - Source:212.57.230.141,412 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:58:14 - TCP Packet - Source:78.86.139.14,52557 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:58:18 - TCP Packet - Source:78.86.139.14,52567 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:58:21 - TCP Packet - Source:78.86.139.14,52578 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 13:58:25 - TCP Packet - Source:78.86.139.14,52595 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 14:00:42 - TCP Packet - Source:77.97.91.228,64533 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 14:10:00 - TCP Packet - Source:212.57.230.141,26262 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 14:19:26 - TCP Packet - Source:212.57.230.141,19605 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 14:38:15 - TCP Packet - Source:212.57.230.141,158 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 14:38:31 - TCP Packet - Source:77.97.91.228,61765 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 14:43:40 - Administrator login successful - IP:
Fri, 2008-10-17 14:47:09 - TCP Packet - Source:212.57.230.141,49052 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 14:47:17 - TCP Packet - Source:77.97.91.228,65065 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 14:59:55 - TCP Packet - Source:118.171.71.109,48755 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 15:00:10 - TCP Packet - Source:118.171.71.109,48763 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 15:01:43 - TCP Packet - Source:77.97.91.228,63397 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 15:01:51 - TCP Packet - Source:212.57.230.141,34709 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 15:03:52 - Administrator login successful - IP:192.168.0.2
Fri, 2008-10-17 15:17:26 - TCP Packet - Source:212.57.230.141,21910 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 15:29:08 - Administrator login successful - IP:192.168.0.2
Fri, 2008-10-17 15:32:04 - TCP Packet - Source:142.165.54.149,50118 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 15:34:21 - TCP Packet - Source:212.57.230.141,14495 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 15:47:04 - TCP Packet - Source:212.57.230.141,51358 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 15:55:28 - TCP Packet - Source:217.224.222.193,59114 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 15:58:16 - TCP Packet - Source:78.86.139.14,60466 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 15:58:31 - TCP Packet - Source:78.86.139.14,60499 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 16:00:37 - Administrator login successful - IP:
Fri, 2008-10-17 16:01:41 - TCP Packet - Source:212.57.230.141,51351 Destination:,54804 - [Azureus rule match]
Fri, 2008-10-17 16:02:43 - Administrator login successful - IP:
Nothing there. What the WAN uptime (and is it less than the LAN uptime)?
Right i have just adjusted my MTU to 1492 after using TGP optimiser, which has just dropped the LCP and reinitialised LCP so my WAN uptime has been reset, b4 reset it had been up for around 7hrs 30mins.
LAN and WLAN has been up for 27hrs 8min, so yes its been up for less.
Which suggests there is some instability, and that's affecting your profile. Is there any chance you could borrow an alternative router to try?
I cannot understand with that downstream attenuation why you are not getting a full sync? I know you have a BT filtered faceplate but I wonder if you remove it and can find a "soap and rope filter" what sync you get from the test socket?
My downstream is 22db noise margin is 15 sync 8128 interleaved on a ADSLnation filtered faceplate DG834N router
That's what's puzzling me, Steve, coupled with signs of instability.
Ok rik i shall give trying a different router ago, i have a spare linksys WAG354G V2.
I shall put that on this evening and see how that goes.
I take it I'm looking for my WAN to stay up the same amount of time as the LAN/WLAN ?
What do you suggest ?
Quote from: stevethegas on Oct 17, 2008, 16:54:43
I cannot understand with that downstream attenuation why you are not getting a full sync? I know you have a BT filtered faceplate but I wonder if you remove it and can find a "soap and rope filter" what sync you get from the test socket?
My downstream is 22db noise margin is 15 sync 8128 interleaved on a ADSLnation filtered faceplate DG834N router
Good point steve i shall try that now, removing faceplate and going to the testsocket with the so called soap on a rope...lol
Essentially, you're trying to find out if the line is dropping regularly, and then we need to work out why if it is. As Steve says, it would be good to use the test socket with a soap on a rope filter, to eliminate the possibility of a faulty face plate. If the Linksys also appears unstable, then running Routerstats for 24 hours would be a good move.
http://www.vwlowen.co.uk/moreinternet/files.htm
If I have seen any issues with the DG834N its with wireless and seems to relate to finding a channel not being used by the neighbours.As on certain channels if neighbour A turns his router on wireless dissappears
I had a WAG54GS and that used to give me a sync of 8096 with interleave on.
Steve no issues with wireless side of the router as it's on a fixed channel as AUTO channel mode is cr*p and freezes the WIFI.
Right brand new unused soap on a rope attached to bt test socket.
Router Stat's :
ADSL Link
Downstream
Upstream
Connection Speed
6176 kbps
832 kbps
Line Attenuation
12.0 db
6.5 db
Noise Margin
14.9 db
11.0 db
Slight drop in sync, due to me powering down router ? whilst i took faceplate of and attached soap on the rope.
Ideas : i have another two ADSL filters to try.
The variations in sync speed suggest there's a lot of noise being picked up somewhere, 3D. One possible culprit would be the power brick for the router, we've also seen it happen with poor power supplies in PCs and monitors. Alternatively, of course, it could be external to the property. If you have a MW, battery powered, radio, tune it away from a station, so you only have white noise, and take it walkabouts - see if the noise level increases anywhere along the route of your phone line within the building, or around your computer.
Hmmm yeah EM noise ?, my router is quite close to my HD LCD and my Logitech z5500 controler, maybe i should try and move the router to a different posistion and move the brick to a different power socket.
Oh just traced where the phone goe's from the master socket to bt's master socket and it passes right past the bl**dy FRIDGE!!!!!
If you can try the MW radio trick, that should show if the noise is a problem.
Quote from: 3DBULLY on Oct 17, 2008, 17:38:11
Hmmm yeah EM noise ?, my router is quite close to my HD LCD and my Logitech z5500 controler, maybe i should try and move the router to a different posistion and move the brick to a different power socket.
Oh just traced where the phone goe's from the master socket to bt's master socket and it passes right past the bl**dy FRIDGE!!!!!
You mention 2 master sockets?
I missed that, Steve, well spotted. :thumb:
Sorry 1 master socket and the other one is where the phoneline from the pole terminates in side the house.
Phew! ;D
Quote from: 3DBULLY on Oct 17, 2008, 18:26:03
Sorry 1 master socket and the other one is where the phoneline from the pole terminates in side the house.
What does the one where it enters the property look like? It's strange that it doesn't go straight into the master socket.
Sebby the termination box is rectangular 1.5 inch wide at the top by 2inch length has BT stamped on it.
The line exit's that box which then goes to the master socket.
I wonder what it's for... Perhaps it's from the old days when BT came and fitted the new-style socket.
I also have just done the detuned MW radio walkabout, That test shows from the BT rectangular termination box there is a plug socket right next to the phone cable which shows a high change in the tone of the white noise, next is just after the master socket where my active sub speaker sits also a massive high change in white noise, checked around the router and there doesn't seem to be any sign's of white noise tone change.
Going to move sub and route phone cable away from plug socket.
Let us know if it makes any difference. It's amazing what can be causing noise.
Quote from: Sebby on Oct 18, 2008, 14:24:33
I wonder what it's for... Perhaps it's from the old days when BT came and fitted the new-style socket.
It's quite a new box, do you remember the old termination boxes of a similar size that was a more oval shape ? circa 1980's ?
P.s the loudest change in tone with the radio was the sky box which is nowhere near any of the com's equipment.
Quote from: 3DBULLY on Oct 18, 2008, 14:30:45
It's quite a new box, do you remember the old termination boxes of a similar size that was a more oval shape ? circa 1980's ?
Yep, that's sort of what I was thinking of. I guess what you've got is a new version of that. I suppose that the problem could be there; after all, there will be joints in that box.
3D Last night when you tried the test socket was the phone line connected to the inline adsl filter as well as the router? You mentioned a sky box is it connected to the phone line?
Quote from: stevethegas on Oct 18, 2008, 15:11:02
3D Last night when you tried the test socket was the phone line connected to the inline adsl filter as well as the router? You mentioned a sky box is it connected to the phone line?
nope and nope.
Time for Routerstats maybe?
Yes rik, way ahead of you, have been monitoring router stat's most of the day very strange activity.....
Fri 17 Oct 2008 17:06:34 (UTC) **.***.*.** Rx-Noise= 13.6 Tx-Noise= 10 Rx-Sync= 5696 Tx-Sync= 832
Fri 17 Oct 2008 17:29:34 (UTC) **.***.*.** Rx-Noise= 14.1 Tx-Noise= 12 Rx-Sync= 5344 Tx-Sync= 832
Fri 17 Oct 2008 17:30:34 (UTC) **.***.*.** Rx-Noise= 14.1 Tx-Noise= 12 Rx-Sync=
Fri 17 Oct 2008 18:29:34 (UTC) **.***.*.** Rx-Noise= 0 Tx-Noise= 0 Rx-Sync= 0 Tx-Sync= 0
Fri 17 Oct 2008 18:30:34 (UTC) **.***.*.** Rx-Noise= 12.4 Tx-Noise= 12 Rx-Sync= 4960 Tx-Sync= 832
Fri 17 Oct 2008 19:23:34 (UTC) **.***.*.** Rx-Noise= 14.1 Tx-Noise= 12 Rx-Sync= 4672 Tx-Sync= 832
Sat 18 Oct 2008 13:11:50 **.***.*.** Rx-Noise= 14.3 Tx-Noise= 11 Rx-Sync= 6400 Tx-Sync= 832
Sat 18 Oct 2008 14:07:50 **.***.*.** Rx-Noise= 0 Tx-Noise= 0 Rx-Sync= 0 Tx-Sync= 0
Sat 18 Oct 2008 14:08:50 Rx-Noise= 15.3 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sat 18 Oct 2008 14:08:50 Disconnected
Sat 18 Oct 2008 14:08:50 [Alarm: Disconnected]
Sat 18 Oct 2008 14:08:50 Rx-Noise= 15.3 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sat 18 Oct 2008 14:08:50 ROUTER REBOOTED!
Sat 18 Oct 2008 14:08:50 Rx-Noise= 15.3 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sat 18 Oct 2008 14:09:50
Sat 18 Oct 2008 14:10:50
Sat 18 Oct 2008 14:11:50
Sat 18 Oct 2008 14:12:50
Sat 18 Oct 2008 14:13:50
Sat 18 Oct 2008 14:14:50 **.***.*.** Rx-Noise= 14.5 Tx-Noise= 10 Rx-Sync= 6368 Tx-Sync= 832
Sat 18 Oct 2008 15:49:34 Rx-Noise= 12.9 Tx-Noise= 10 Rx-Sync= 6368 Tx-Sync= 832
Sat 18 Oct 2008 15:49:34 Disconnected
Sat 18 Oct 2008 15:49:34 [Alarm: Disconnected]
Sat 18 Oct 2008 15:49:34 Rx-Noise= 12.9 Tx-Noise= 10 Rx-Sync= 6368 Tx-Sync= 832
Sat 18 Oct 2008 15:49:34 ROUTER REBOOTED!
Sat 18 Oct 2008 15:49:34 Rx-Noise= 12.9 Tx-Noise= 10 Rx-Sync= 6368 Tx-Sync= 832
Sat 18 Oct 2008 15:50:34
Sat 18 Oct 2008 15:51:34
Sat 18 Oct 2008 15:52:34
Sat 18 Oct 2008 15:53:34
Sat 18 Oct 2008 15:55:33 **.***.*.** Rx-Noise= 13.8 Tx-Noise= 12 Rx-Sync= 6720 Tx-Sync= 832
Sat 18 Oct 2008 16:53:33 **.***.*.** Rx-Noise= 0 Tx-Noise= 0 Rx-Sync= 0 Tx-Sync= 0
Sat 18 Oct 2008 16:54:33 **.***.*.** Rx-Noise= 12.8 Tx-Noise= 12 Rx-Sync= 6752 Tx-Sync= 832
Sat 18 Oct 2008 17:37:49 **.***.*.** Rx-Noise= 12.2 Tx-Noise= 12 Rx-Sync= 6176 Tx-Sync= 832
Sat 18 Oct 2008 18:09:57 **.***.*.** Rx-Noise= 13.7 Tx-Noise= 12 Rx-Sync= 4992 Tx-Sync= 832
Sat 18 Oct 2008 18:29:53 **.***.*.** Rx-Noise= 14.4 Tx-Noise= 12 Rx-Sync= 4992 Tx-Sync= 832
Lots and lots of resyncs there. What's curious is that your SNRM is always okay (although, admittedly, it doesn't show was before the resyncs. I'd imagine there are some surges of noise going on here.
I meant Routerstats, the program, 3D. That will graph and log the connection, so we can see if there's a correlation between noise margin and re-syncs.
That info was from routerstat's, i had to edit it because there is a limit character limit in making post's.
What would you like from routerstat's and how do i post the right info for you, as I'm new to the program.
Hi 3D. You're looking for points at which Routerstats shows an Rx noise figure of 0 or less, or an Rx sync speed of 0 (which indicates the connection has dropped). It's usually easier to spot them in the log if you use the graphs to spot the timing, ie look for the Rx speed to drop to zero.
Here is a log of quite a few drops..... ???......added log attachment.
[attachment deleted by admin]
The 2nd downstream Rx jpg.
[attachment deleted by admin]
That looks like classic cyclical noise, 3D. Can you associate the timing with any device in the house, eg boiler switching off/on?
Sorry guy's was away for a few day's in london.
I'm sure it's not the boiler as it hasn't yet been turned on to heat the house as it's still warm down here on the isle of wight.
Don't notice any increase in noise when the boiler turns on when the hot tap's on.
There's no microwave in the kitchen as we don't believe in them.
Noise increases at around 5pm and seem's to get worse from then on, going by the log data.
By around 6pm I'm down to 5000kbps, 7pm 4500kbps.
There seems to be a patten.
The pattern's called darkness, 3D. ;) I suspect, in that case, you're picking up a lot of RF noise (possibly including shipping).
http://www.idnetters.co.uk/forums/index.php?topic=7355.msg150190#msg150190
I still have the RF-1 on my line ,Goodness knows why
Because it's there, Steve? ;D
Hmm....Just had a Resync just now when the phone rang!, Just remembered that i dug up an old BT Diverse 3010 digital phone maybe that could be causing an issue?
Sat, 2000-01-01 00:00:24 - Initialize LCP.
Sat, 2000-01-01 00:00:24 - LCP is allowed to come up.
Sat, 2000-01-01 00:00:31 - CHAP authentication success
Sat, 2000-01-01 00:00:36 - Send out NTP request to time-g.netgear.com
Fri, 2008-10-24 15:07:02 - Receive NTP Reply from time-g.netgear.com
Fri, 2008-10-24 15:07:03 - Administrator login successful - IP:192.168.0.2
Fri, 2008-10-24 16:06:25 - Router start up
Fri, 2008-10-24 15:29:16 - Administrator login successful - IP:192.168.0.2
Fri, 2008-10-24 15:34:23 - LCP down.
Fri, 2008-10-24 15:34:31 - Initialize LCP.
Fri, 2008-10-24 15:34:31 - LCP is allowed to come up.
Fri, 2008-10-24 15:35:31 - Initialize LCP.
Fri, 2008-10-24 15:35:31 - LCP is allowed to come up.
Fri, 2008-10-24 15:36:31 - Initialize LCP.
Fri, 2008-10-24 15:36:31 - LCP is allowed to come up.
Fri, 2008-10-24 15:37:32 - Initialize LCP.
Fri, 2008-10-24 15:37:32 - LCP is allowed to come up.
Fri, 2008-10-24 15:37:44 - CHAP authentication success
It's the phone!..... have just got BT to ring back and each time the phone ring's the ADLS drops and resync's.
Problem solved methink's, gonna try a different phone.
It could also be the filter, 3D. If you want to get a callback easily, just dial 17070 and take option 2. :)
Quote from: stevethegas on Oct 24, 2008, 16:25:39
http://www.idnetters.co.uk/forums/index.php?topic=7355.msg150190#msg150190
I still have the RF-1 on my line ,Goodness knows why
I read something about these RF filters the other day on another forum, incidentally. You have to be careful with some of them as they filter out the frequencies that ADSL uses.
That would be the US filters, Seb. ;)
There are certainly some that work with ADSL (not sure about those from that US site). Also, whether it's for use with ADSL1, ADSL2, or ADSL2+ makes a difference as they use different frequencies.
Sorry, that was US = useless... ;)
Having some strange issues today.
Sun 26 Oct 2008 14:56:53 ***.***.***.*** Rx-Noise= 14.6 Tx-Noise= 10 Rx-Sync= 6400 Tx-Sync= 832
Sun 26 Oct 2008 14:57:53 ***.***.***.*** Rx-Noise= 14.8 Tx-Noise= 10 Rx-Sync= 6400 Tx-Sync= 832
Sun 26 Oct 2008 14:58:53 ***.***.***.*** Rx-Noise= 14.6 Tx-Noise= 10 Rx-Sync= 6400 Tx-Sync= 832
Sun 26 Oct 2008 14:59:53 ***.***.***.*** Rx-Noise= 14.3 Tx-Noise= 10 Rx-Sync= 6400 Tx-Sync= 832
Sun 26 Oct 2008 15:00:53 ***.***.***.*** Rx-Noise= 14.3 Tx-Noise= 10 Rx-Sync= 6400 Tx-Sync= 832
Sun 26 Oct 2008 15:01:53 ***.***.***.*** Rx-Noise= 14.6 Tx-Noise= 10 Rx-Sync= 6400 Tx-Sync= 832
Sun 26 Oct 2008 15:02:53 ***.***.***.*** Rx-Noise= 13.8 Tx-Noise= 10 Rx-Sync= 6400 Tx-Sync= 832
Sun 26 Oct 2008 15:03:53 ***.***.***.*** Rx-Noise= 14.6 Tx-Noise= 10 Rx-Sync= 6400 Tx-Sync= 832
Sun 26 Oct 2008 15:04:53 ***.***.***.*** Rx-Noise= 14.6 Tx-Noise= 10 Rx-Sync= 6400 Tx-Sync= 832
Sun 26 Oct 2008 15:05:53 ***.***.***.*** Rx-Noise= 14.4 Tx-Noise= 10 Rx-Sync= 6400 Tx-Sync= 832
Sun 26 Oct 2008 15:06:53 ***.***.***.*** Rx-Noise= 14.4 Tx-Noise= 10 Rx-Sync= 6400 Tx-Sync= 832
Sun 26 Oct 2008 15:07:53 ***.***.***.*** Rx-Noise= 14.1 Tx-Noise= 10 Rx-Sync= 6400 Tx-Sync= 832
Sun 26 Oct 2008 15:08:53 ***.***.***.*** Rx-Noise= 14.6 Tx-Noise= 10 Rx-Sync= 6400 Tx-Sync= 832
Sun 26 Oct 2008 15:09:53 ***.***.***.*** Rx-Noise= 14.7 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:10:53 ***.***.***.*** Rx-Noise= 12.9 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:11:53 ***.***.***.*** Rx-Noise= 14.2 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:12:54 ***.***.***.*** Rx-Noise= 15 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:13:53 ***.***.***.*** Rx-Noise= 14.4 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:14:53 ***.***.***.*** Rx-Noise= 14.9 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:15:53 ***.***.***.*** Rx-Noise= 14.3 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:16:53 ***.***.***.*** Rx-Noise= 13.9 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:17:53 ***.***.***.*** Rx-Noise= 14.1 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:18:53 ***.***.***.*** Rx-Noise= 14.6 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:19:53 ***.***.***.*** Rx-Noise= 14.3 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:20:53 ***.***.***.*** Rx-Noise= 13.8 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:21:53 ***.***.***.*** Rx-Noise= 14.2 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:22:53 ***.***.***.*** Rx-Noise= 14.4 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:23:53 ***.***.***.*** Rx-Noise= 14.7 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:24:53 ***.***.***.*** Rx-Noise= 14.5 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:25:53 ***.***.***.*** Rx-Noise= 14.4 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:26:53 ***.***.***.*** Rx-Noise= 14 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:27:53 ***.***.***.*** Rx-Noise= 14.1 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:28:53 ***.***.***.*** Rx-Noise= 13.1 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:29:53 ***.***.***.*** Rx-Noise= 13.9 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:30:53 ***.***.***.*** Rx-Noise= 13.8 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:31:53 ***.***.***.*** Rx-Noise= 14.3 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:32:53 ***.***.***.*** Rx-Noise= 14.1 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:33:53 ***.***.***.*** Rx-Noise= 14.2 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:34:53 ***.***.***.*** Rx-Noise= 14.4 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:35:53 ***.***.***.*** Rx-Noise= 14.1 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:36:53 ***.***.***.*** Rx-Noise= 14.1 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:37:53 ***.***.***.*** Rx-Noise= 13.8 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:38:53 ***.***.***.*** Rx-Noise= 14.5 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:39:53 ***.***.***.*** Rx-Noise= 13.6 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:40:53 ***.***.***.*** Rx-Noise= 14.2 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:41:53 ***.***.***.*** Rx-Noise= 13.8 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:42:53 ***.***.***.*** Rx-Noise= 13.9 Tx-Noise= 10 Rx-Sync= 6304 Tx-Sync= 832
Sun 26 Oct 2008 15:43:53 ***.***.***.*** Rx-Noise= 14.2 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 15:44:53 ***.***.***.*** Rx-Noise= 14 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 15:45:53 ***.***.***.*** Rx-Noise= 14.4 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 15:46:53 ***.***.***.*** Rx-Noise= 13.8 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 15:47:53 ***.***.***.*** Rx-Noise= 14.1 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 15:48:53 ***.***.***.*** Rx-Noise= 13.8 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 15:49:53 ***.***.***.*** Rx-Noise= 14.2 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 15:50:53 ***.***.***.*** Rx-Noise= 14.3 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 15:51:53 ***.***.***.*** Rx-Noise= 13.8 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 15:52:53 ***.***.***.*** Rx-Noise= 14 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 15:53:53 ***.***.***.*** Rx-Noise= 14 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 15:54:53 ***.***.***.*** Rx-Noise= 13.8 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 15:55:53 ***.***.***.*** Rx-Noise= 13.8 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 15:56:53 ***.***.***.*** Rx-Noise= 13.1 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 15:57:53 ***.***.***.*** Rx-Noise= 14 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 15:58:53 ***.***.***.*** Rx-Noise= 13.5 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 15:59:53 ***.***.***.*** Rx-Noise= 13.5 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 16:00:53 ***.***.***.*** Rx-Noise= 14.3 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 16:01:53 ***.***.***.*** Rx-Noise= 13.3 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 16:02:53 ***.***.***.*** Rx-Noise= 13.9 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 16:03:53 ***.***.***.*** Rx-Noise= 13.2 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 16:04:53 ***.***.***.*** Rx-Noise= 13.6 Tx-Noise= 10 Rx-Sync= 6144 Tx-Sync= 832
Sun 26 Oct 2008 16:05:53 ***.***.***.*** Rx-Noise= 0 Tx-Noise= 0 Rx-Sync= 0 Tx-Sync= 0
Sun 26 Oct 2008 16:06:53 ***.***.***.*** Rx-Noise= 14.2 Tx-Noise= 10 Rx-Sync= 5824 Tx-Sync= 832
Sun 26 Oct 2008 16:07:53 ***.***.***.*** Rx-Noise= 13.9 Tx-Noise= 10 Rx-Sync= 5824 Tx-Sync= 832
Sun 26 Oct 2008 16:08:53 ***.***.***.*** Rx-Noise= 14.5 Tx-Noise= 10 Rx-Sync= 5824 Tx-Sync= 832
Downstream sync speed dropping, but with no re-sync until 16:05:53. :dunno:
Theoretically, that's impossible, 3D. My hunch is that the line dropped and reconnected within the minute sampling range, so it doesn't show the dip to zero. Do the router logs shed any light on events?
No rik the routers log doesn't show a thing, but i did watch the WAN and the PPP link light drop.
I think it has to be what I think, 3D. On the graphs settings page, select the sample rate to be every 30 seconds, that should stop things slipping past.
ok will do rik.
Still not happy with my connection.....
Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 6560 kbps(DOWN-STREAM), 832 kbps(UP-STREAM)
IP profile for your line is - 3500 kbps
Actual IP throughput achieved during the test was - 3269 kbps
If you wish to discuss these results please contact your ISP.
Last few day's ive had loads of resyncs via the exchange(ie the two middle lights have been going out on my DG834n) in one session i had the two middle lights drop about 4 or 5 times in an hour.
[attachment deleted by admin]
We know what's happening, 3D, we don't know why. If you're sure that your internal wiring is not the problem, get onto IDNet and they can raise a fault with BT.
Rik i have just filled out the contact form, and also just phoned support to let them know that i'm not happy with my bt test results, none of my equipment my side is at fault as i tested my router at a friends house for 24hrs, no prob's on his ADSL line.
Trying to Admin on my EA game server yesterday was impossible as i kept losing my connection to the server when the two middle lights kept going out on my DG834n.
Pulling my hair out over this..... :rant2:
The important thing to remember is that the connection between you and the exchange is BT territory, and only in extreme circumstances (once in the past couple of years) have I seen an instance of dropped connections (loss of sync) being caused by an issue at IDNet. The vast majority of such problems come from noise on the line, either between you and the exchange, eg bad joint, split pair etc, or an issue with your internal wiring or equipment. The only way to resolve it is to get BT to test the line and, potentially, visit. Note, though, that if BT find a fault on your side of the master socket, you will face a charge of £160+. :(
Yeah i know about the charge as i have been hit with a subsidised bill from pipex before.
Do you know why you were charged previously?
Your throughput is good for the profile, but the profile is wrong, which indicates instability. If you're sure it's not something internal, you'll have to get IDNet to arrange for BT to pay you a visit.
Is it considered acceptable to have the phone line set up as indicated earlier with a non master socket where the line enter the premises and then a traditional master socket some distance after this.Will what is in fact an extension not potentially act as an aerial for noise?
It is, Steve, but that section of the line remains BT's, so if it's causing the problem, they have to sort it.
Rik pipex subsidised bill was £50, the reason for this was that the BT engineer could not find a fault from the master socket via my phone pole to the street termination box and from there to the exchange.
But pipex still raised a charge.
Right james from IDnet support sent me an e-mail.
Hi Simon, I have asked BTs technical teams to have a look at this for you, they have corrected the profile to match that of your sync speed however they are suggesting that your circuit seems to connect at about 4mb on occasion. This is what would cause the drop in the speed of the throughput each time. It is important that your setup is at its best to perform at the optimum speed for your line, this would mean making sure the router/modem is connected directly into the main phone socket within your property to cut out as much interference as possibly. In doing this you should see amuch more stable connection and more consistant speed.
You are actually very close to the local exchange and the line appears to be of very high quality.
Kind regards
JamesIDNet
Conclusion :- So after this i'm just going to leave routerstat's running for the next 3 day's and see how thing's pan out!
It's all you can do now...
Although Rik i'm watching the downstream noise at this moment and it was at 14db and it's slowly dropping, now at 12.3db this is when i start getting all the noise appear at around 4:30pm onwards.
Strange.
Have the street lights just turned on?
Nope the street light which is 10ft away from the phone pole is off.
Is it on, though? At this time, during the darker months, street lighting often causes problems, Christmas lights are even worse. As we reach sunset, too, RF interference increases.
Rik if you have google earth on your comp, punch in PO38 1HR. maybe beause of my close proxmity to the sea i'm getting alot of shipping noise?
You could certainly be picking up shipping traffic, though I have no idea what frequency they use (or, for that matter, marine radar).
Probably a stupid question? From the rectangle box to the "master socket" will that have a "ring wire" lead?
PS I have taken the RF-1 filter off my line so if anyone wants it send me PM.
It shouldn't, Steve, it should just be a pair at that point.
Rik's right it's just a pair, But from that box to the master socket it has more wires but only 2 are connected.
What are the colours used?
I can't remember off hand, but i'm sure they were both white/blue and possibly blue/white.
Don't want to undo the NTe5 at the mo as i'm watching the downstream noise, which is currently at 9.9db.
That's OK, it sounds like it is wired with a pair, so there shouldn't be any problems from that length of cable.
I'm not to sure about that length of cable from the sml rectangle box to the master, we had the kitchen rebuilt and i'm sure the builders moved that said cable maybe it's damaged or it could be passing by the underfloor ringmain.
Which could explain if it did pass the ringmain, that it might be picking up interference from there.
Ohh and whats the downsteam noise cutoff point b4 a resync ?
If the builders have interfered with that cable, it's illegal and could cause you problems with BT. :(
Different routers will re-sync at different margins, my Netgears held to -2db, while my 2700s seem to go at about 3db (but hold the line for longer than a Netgear ever could and at a higher sync speed).
Well they had to remove it from running along the wall when they re-plastered the wall's the floor was up at the same time so i think they ran it under the floor instead.
Technically they haven't altered anything other than the position.
Hmm phone just rang and the downstream noise just went from 10.8db to 8.3db spike.
If they haven't tampered with the connections, just moved the cable, it's not an issue.
The noise spike sounds like a bad filter.
Or possibly my Bt DECT diverse 3010 ?
Possibly, but unless the base unit is near the router, I'd be looking at the filter.
The base is not near the router, but i agree about the filter, 2 moro i will try the brand new spare filter instead of the NTe5 faceplate.
Cheers for all the help rik/sebby etc oh and IDnet support.
Let us know how it goes...
:rant2: :rant2: :rant2: :rant2:......Well here goe's my update on my FLAKEY connection, Bt are currently monitoring my line and so is IDnet support, apparently BT stated that my line is of very good quality and that i'm very close to the exchange, they also mentioned that there is something peculiar is happening with my line on Saturday's, but didn't mention what!
James from support had sent me an i-Plate to try out, but that hasn't really made any difference to the constant downstream snr dropping right off between the hours of 15:00hrs and 23:00hrs.
My connection is getting worse, it just seems to be degrading, i have exhausted all other ideas about whats causing all this god damn downstream snr drop off's, i have turned off everything in my house to try and determine if any household electrical item's were causing the dropping snr, result's for that experiment nil.
My line was never this bad, think it may need a BT Engineer or or BT's special fault finding squad You know the ones that deal with interference.
Yours depressingly
3dbully :-\
What router are you using?
Interesting that BT are admitting the issue, 3D. That's half the battle.
This may help Link (http://community.plus.net/forum/index.php?action=printpage;topic=65685.0)
The big problem is that, for most of us, we don't have the equipment to test to such a sophisticated level, Glenn. The de-tuned AM radio is as close as we can get. RF noise is so insidious that it's not surprising that it can be difficult to resolve these cases. :(
I seem to recall Dean (g7pkf) using the SFI team to try to sort his problems with the trains causing noise on his line, he maybe able to shed some light on how to get them to look at the problems.
My router is an DG834n......it's been sat on my friends broadband for 24hrs no drops, so we can rule the router out!
Quote from: Glenn on Nov 02, 2008, 14:58:06
I seem to recall Dean (g7pkf) using the SFI team to try to sort his problems with the trains causing noise on his line, he maybe able to shed some light on how to get them to look at the problems.
I'll see if I can get hold of him, Glenn. :thumb:
Quote from: 3DBULLY on Nov 02, 2008, 15:00:37
My router is an DG834n......it's been sat on my friends broadband for 24hrs no drops, so we can rule the router out!
Except...
Sometimes it's a combination of specific things, 3D. What router does your friend have, could you borrow that for a few days?
Are there any big sporting venues, racecourses, sports tracks etc nearby. Just a random thought that something of that type may be creating interference somewhere at the times you stated on a Saturday.
Quote from: cavillas on Nov 02, 2008, 16:26:17
Are there any big sporting venues, racecourses, sports tracks etc nearby. Just a random thought that something of that type may be creating interference somewhere at the times you stated on a Saturday.
.......ermm nope.
Well, I tried. ;D
SFi are BT's last resort, I had several visits from "standard" engineers (5 i think) and i just kept pestering them, eventually yes they improved matters BUT my line is still noisy.
Just keep pestering them, luckily i suspect IDNET will be pestering them as well.
I would now start to keep a diary speceific to your problem, record EXACT times of interferance , when you contact idnet or bt time date and NAME.
It may take a while but you can/will get there eventually.
Keep quiet about builders moving the point,
after re-reading this how many BT engineer's have you had out so far? do you have it in writing that they admit a fault?
Dean
p.s Here as requested Rik
Thanks, Dean. :thumb: :karma:
Dean,
i have had only the two visit's from an Engineer, one was for the damage to the drop wire which was caused by one of BT's anchor point's failing on my house, the drop wire was replaced plus the anchor point which was over a two years ago, and the other visit i never had anything in writing from the BT Engineer stating there was a fault!, the only thing he mentioned was there seemed to be some earthing on my line, i think he swapped me over in the street termination point(not to sure if it was an E side or D side swap) and also at the exchange lift and shift!
In regards of the lift and shift, 2 or 3 days after my phone line was out for a few hours then resumed phone service and ADSL it hasn't been the same since then thinking about it.
Oh the builders only removed the cable from the wall while they plastered, they never actually disconnected it!
I'm keeping a daily Routerstat's log diary, which i'm then passing onto James at IDnet support every 2 to 3 day's.
Regards
3dbully
log another call.
one of te best ways is to go via the complaints procedure on BT's website. at least then you can have your full say.
AND you will get a response.
Just a quick BT speed test :
Test1 comprises of Best Effort Test: -provides background information.
Your DSL connection rate: 6944 kbps(DOWN-STREAM), 832 kbps(UP-STREAM)
IP profile for your line is - 4000 kbps
Actual IP throughput achieved during the test was - 3544 kbps
If you wish to discuss these results please contact your ISP.
Plus i'm still on interleaved, which i dont want...... i want fast mode.
I don't think you'll get it unless your line stabilises, 3D, and the profile compared to the sync speed says it's still flapping.
Yes i agree rick, just got off the phone with james, he has now escalated this to BT for an engineer visit.
I just hope they come out at 4pm as i asked james to book it for then.
If they come before then they are not going to see the issue in it's true glory, and they will say there is no problem and walk away.
:fingers:
Let us know how it goes.
Will do rick....... :fingers:
Fingers crossed for you. :fingers: