Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: [1] 2 3

Author Topic: request timed out  (Read 9726 times)

clueless

  • Member
  • **
  • Posts: 19
request timed out
« on: March 26, 2012, 01:53:52 PM »

For about the last 8 months I have been experiencing game freezing lag on Xbox Live at very regular intervals at least once an hour, though often more , any time of day, every day; the freeze/lag lasts for around 5 seconds then returns to normal.

After running persistent Ping tests It turned out that while getting this freezing I was getting 'request timed out' errors. This error occurs with or with out any type activity over the net (excluding the Ping test obviously).

This happens on wired and wireless PC, laptop or console. My router is plugged directly into the master socket with a splitter. I have also tested the router plugged into the test socket with no phones connected.

I bought a new router (Billion 7800N) which didn't make any difference. I used this router to set my SNR to 6 (it was at 12 previously) which improved my sync... but now it has crept back up again (boo!).

During this time frame my attenuation has increased from 53 to 63.5, which obviously has increased my woes!

I have spent the last month conversing (tickets) with my ISP (ADSL24). I have checked and rechecked router settings, changed cables. ADSL24 say they have run test and can't find any issues on their end; they suggest that I need to get BT to look into it.

I did a quiet line test with a wired phone plugged directly into the master socket (nothing else plugged in)- there is a gentle hum on the line but no crackling, does this sound like a line fault?

I'm reluctant to contact BT without a plan as I don't want to be told that my internet is working within their acceptable range and then get slapped in the face with a huge fee for nothing.

I would appreciate your thoughts on what is causing the 'request timed out' message or on how I should present the issue to BT.

Line stats:

31/7/11:

# adslctl info --stats
adslctl: ADSL driver and PHY status
Status: Showtime  Channel: INTR, Upstream rate = 448 Kbps, Downstream rate = 364
8 Kbps
Link Power State: L0
Mode:                   G.DMT
Channel:                Interleave
Trellis:                ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):       8.8             17.0
Attn(dB):       56.5            31.5
Pwr(dBm):       18.7            12.3
Max(Kbps):      3936            964
Rate (Kbps):    3648            448
                        G.dmt framing
K:              115(0)          15
R:              16              16
S:              2               8
D:              16              4
                        ADSL2 framing
MSGc:           1               1
B:              115             15
M:              2               8
T:              1               1
R:              16              16
S:              2.1379          9.0000
L:              928             128
D:              16              4
                        Counters
SF:             9405384         9405382
SFErr:          152             0
RS:             319783086               79945747
RSCorr:         32185           0
RSUnCorr:       1116            0

HEC:            123             0
OCD:            0               0
LCD:            0               0
Total Cells:    1375667416              0
Data Cells:     13571465                0
Drop Cells:     0
Bit Errors:     0               0

ES:             108             0
SES:            0               0
UAS:            9               0
Total time = 1 days 20 hours 20 min 9 sec
SF  = 9405384
CRC = 152
LOS = 0
LOF = 0
ES  = 108
Latest 1 day time = 20 hours 20 min 9 sec
SF  = 4306361
CRC = 85
LOS = 0
LOF = 0
ES  = 61
Latest 15 minutes time = 5 min 9 sec
SF  = 18231
CRC = 1
LOS = 0
LOF = 0
ES  = 1
Previous 15 minutes time = 15 min 0 sec
SF  = 52931
CRC = 1
LOS = 0
LOF = 0
ES  = 1
Previous 1 day time = 24 hours 0 sec
SF  = 5099023
CRC = 67
LOS = 0
LOF = 0
ES  = 47
15 minutes interval [-30 min to -15 min] time = 15 min 0 sec
SF  = 52930
CRC = 0
LOS = 0
LOF = 0
ES  = 0
15 minutes interval [-45 min to -30 min] time = 15 min 0 sec
SF  = 52931
CRC = 0
LOS = 0
LOF = 0
ES  = 0
15 minutes interval [-60 min to -45 min] time = 15 min 0 sec
SF  = 52930
CRC = 6
LOS = 0
LOF = 0
ES  = 6
#
#

26/3/12:

> adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime
Retrain Reason: 1
Max:    Upstream rate = 900 Kbps, Downstream rate = 3072 Kbps
Channel:        FAST, Upstream rate = 448 Kbps, Downstream rate = 3040 Kbps

Link Power State:       L0
Mode:                   G.DMT
TPS-TC:                 ATM Mode
Trellis:                ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):        10.1            17.0
Attn(dB):        63.5            31.5
Pwr(dBm):        18.3            12.3
                        G.dmt framing
K:              96(0)           15
R:              0               0
S:              1               1
D:              1               1
                        Counters
SF:             16135319                16135540
SFErr:          13024           1
RS:             0               0
RSCorr:         0               0
RSUnCorr:       0               0

HEC:            8123            0
OCD:            24              0
LCD:            0               0
Total Cells:    1966662776              0
Data Cells:     20808936                0
Drop Cells:     0
Bit Errors:     0               0

ES:             25365           0
SES:            207             0
UAS:            119             119
AS:             274305

INP:            0.00            0.00
PER:            1.75            1.75
delay:          0.25            0.25
OR:             32.00           32.00

Bitswap:        33484           686

Total time = 1 days 18 hours 4 min 9 sec
FEC:            0               0
CRC:            66209           0
ES:             25365           0
SES:            207             0
UAS:            119             119
LOS:            2               0
LOF:            18              0
Latest 15 minutes time = 4 min 9 sec
FEC:            0               0
CRC:            328             0
ES:             157             0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
Previous 15 minutes time = 15 min 0 sec
FEC:            0               0
CRC:            267             0
ES:             112             0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
Latest 1 day time = 18 hours 4 min 9 sec
FEC:            0               0
CRC:            3798            0
ES:             1903            0
SES:            0               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
Previous 1 day time = 24 hours 0 sec
FEC:            0               0
CRC:            1033            0
ES:             640             0
SES:            1               0
UAS:            0               0
LOS:            0               0
LOF:            0               0
Since Link time = 3 days 4 hours 11 min 44 sec
FEC:            0               0
CRC:            13024           1
ES:             6106            0
SES:            13              0
UAS:            0               0
LOS:            0               0
LOF:            0               0
>

Cheers.

Logged

coolsnakeman

  • Reg Member
  • ***
  • Posts: 421
    • IT Support Belfast
Re: request timed out
« Reply #1 on: March 26, 2012, 03:08:23 PM »

Hey,

Increase in attenuation doesn't always mean a line fault but again it doesn't mean to say it isn't. Is your SP detecting a copper line fault from there tests and if they are what do they say the line fault is CA,CE,EX,LN or FU? There is no harm in you contacting BT to request a line test to be run you are not obligating yourself into getting an engineer sent out. If BT test your line ok then its down to your SP to get this problem resolved for you especially if you have tried from the test port, changed cables and changed your router over. I can see CRC errors building so the "request timed out" could be a result of performance issues. Do you see your webpages on the PC both wireless and wired timing out on you and do you notice high ping times aswell as slow throughput issues. If so this could all be the result of errors gathering causing latency issues. Do you notice those errors going down while connected to the test socket or do you notice them increasing or staying at the same level. You can request an SFI visit to investigate those errors for you. Huming noise on the line during the quiet line test however would point me in the PSTN direction and i would certainly be getting BT to run a line test on that line.

Regards
Gary
Logged

clueless

  • Member
  • **
  • Posts: 19
Re: request timed out
« Reply #2 on: March 26, 2012, 04:02:46 PM »

Hey,

Increase in attenuation doesn't always mean a line fault but again it doesn't mean to say it isn't. Is your SP detecting a copper line fault from there tests and if they are what do they say the line fault is CA,CE,EX,LN or FU? There is no harm in you contacting BT to request a line test to be run you are not obligating yourself into getting an engineer sent out. If BT test your line ok then its down to your SP to get this problem resolved for you especially if you have tried from the test port, changed cables and changed your router over. I can see CRC errors building so the "request timed out" could be a result of performance issues. Do you see your webpages on the PC both wireless and wired timing out on you and do you notice high ping times aswell as slow throughput issues. If so this could all be the result of errors gathering causing latency issues. Do you notice those errors going down while connected to the test socket or do you notice them increasing or staying at the same level. You can request an SFI visit to investigate those errors for you. Huming noise on the line during the quiet line test however would point me in the PSTN direction and i would certainly be getting BT to run a line test on that line.

Regards
Gary

My SP say they can find no fault at there end.

My Ping is very consistent, rarely dropping more than 1-2ms.

I haven't noticed any page time-out issues.

The test socket hasn't made things better or worse as far as I can tell. I wouldn't really know how to interpret all of the data I listed. I have been running from the TS for about 10 days, I could put front panel back on and simply compare what I see.

My down speed is usually fairly stable; that speed does vary regularly but doesn't seem overly erratic. I use FTP tests to judge the stability.

I shall request a line test then.

Thanks.
Logged

Black Sheep

  • Helpful
  • Addicted Kitizen
  • *
  • Posts: 5722
Re: request timed out
« Reply #3 on: March 26, 2012, 04:07:40 PM »

To add further to Gary's comments .............

I realise you're a gamer, but having your latency (Interleaving depth, Run-mode, Connection-mode ...... all mean the same) set to 'FAST' on a line of your length, is just asking for trouble. As Gary has mooted, your 'errors' will increment causing massive instability. I would insist that you are reverted back to 'INTERLEAVED'. Yes, slightly increased 'ping' but give me that over 'time-outs' any day.

Regarding the attenuation difference, that could even be your new router that's got a greater resistance than the previous one ?? For clarity, could you plug your old router back in and get the stats, then plug the new one in straight away and do the same ???

If it does prove to be a line fault caused an attenuation shift, you are in the fortunate position of being able to request a 'RADE1' task. These are only built if the attenuation has altered by more than 6dB since initial 'Base-line loss' data was stored in the DLM. In other words, if with the same router plugged in the attenuation has increased from what it was when you were first activated, (and you haven't added any extentions etc etc ), then there is obviously a fault somewhere, because your house hasn't moved nor has the Exchange. ;D

You need to be in the test socket with the same router, and I would listen on 17070 option 2, (Quiet line test), to put the circuit under full load to see if noise is heard. Humming noises are usually what we would call an 'Earth fault'. Crackling noises are usually 'High Resistance faults'. Both can play silly buggars with your attenuation. The key is to double-check everything so the blame cannot be laid at your door. ;) :)
Logged

clueless

  • Member
  • **
  • Posts: 19
Re: request timed out
« Reply #4 on: March 26, 2012, 04:38:06 PM »

To add further to Gary's comments .............

I realise you're a gamer, but having your latency (Interleaving depth, Run-mode, Connection-mode ...... all mean the same) set to 'FAST' on a line of your length, is just asking for trouble. As Gary has mooted, your 'errors' will increment causing massive instability. I would insist that you are reverted back to 'INTERLEAVED'. Yes, slightly increased 'ping' but give me that over 'time-outs' any day.

Regarding the attenuation difference, that could even be your new router that's got a greater resistance than the previous one ?? For clarity, could you plug your old router back in and get the stats, then plug the new one in straight away and do the same ???

If it does prove to be a line fault caused an attenuation shift, you are in the fortunate position of being able to request a 'RADE1' task. These are only built if the attenuation has altered by more than 6dB since initial 'Base-line loss' data was stored in the DLM. In other words, if with the same router plugged in the attenuation has increased from what it was when you were first activated, (and you haven't added any extentions etc etc ), then there is obviously a fault somewhere, because your house hasn't moved nor has the Exchange. ;D

You need to be in the test socket with the same router, and I would listen on 17070 option 2, (Quiet line test), to put the circuit under full load to see if noise is heard. Humming noises are usually what we would call an 'Earth fault'. Crackling noises are usually 'High Resistance faults'. Both can play silly buggars with your attenuation. The key is to double-check everything so the blame cannot be laid at your door. ;) :)

The line was working fine after I had 'Fast' enabled for a couple of month (I think) I shall request it to be changed back to be sure.

Regarding attenuation: My ISP informed me I had a 53 last summer. The first line stats I posted from july/11 were 56.

These stats are from 3/2/12 with my previous router (WAG54GS) shortly before I swapped to the 7800N.

# adslctl info --stats
adslctl: ADSL driver and PHY status
Status: Showtime  Channel: FAST, Upstream rate = 448 Kbps, Downstream rate = 284
8 Kbps
Link Power State: L0
Mode:                   G.DMT
Channel:                Fast
Trellis:                ON
Line Status:            No Defect
Training Status:        Showtime
                Down            Up
SNR (dB):       11.6            17.0
Attn(dB):       55.0            31.5
Pwr(dBm):       18.2            12.3
Max(Kbps):      2880            900
Rate (Kbps):    2848            448
                        G.dmt framing
K:              90(0)           15
R:              0               0
S:              1               1
D:              1               1
                        ADSL2 framing
MSGc:           1               1
B:              90              15
M:              1               1
T:              1               1
R:              0               0
S:              1.0000          1.0000
L:              728             128
D:              1               1
                        Counters
SF:             14799290                14799288
SFErr:          2569            0
RS:             0               0
RSCorr:         0               0
RSUnCorr:       0               0

HEC:            951             0
OCD:            0               0
LCD:            0               0
Total Cells:    1689913322              0
Data Cells:     22220724                0
Drop Cells:     0
Bit Errors:     0               0

ES:             1698            0
SES:            5               0
UAS:            9               0
Total time = 1 days 21 hours 48 min 27 sec
SF  = 14799290
CRC = 2569
LOS = 0
LOF = 0
ES  = 1698
Latest 1 day time = 21 hours 48 min 27 sec
SF  = 4618004
CRC = 1267
LOS = 0
LOF = 0
ES  = 637
Latest 15 minutes time = 3 min 27 sec
SF  = 12174
CRC = 6
LOS = 0
LOF = 0
ES  = 6
Previous 15 minutes time = 15 min 0 sec
SF  = 52930
CRC = 10
LOS = 0
LOF = 0
ES  = 10
Previous 1 day time = 24 hours 0 sec
SF  = 5082263
CRC = 639
LOS = 0
LOF = 0
ES  = 471
15 minutes interval [-30 min to -15 min] time = 15 min 0 sec
SF  = 52931
CRC = 0
LOS = 0
LOF = 0
ES  = 0
15 minutes interval [-45 min to -30 min] time = 15 min 0 sec
SF  = 52989
CRC = 11
LOS = 0
LOF = 0
ES  = 5
15 minutes interval [-60 min to -45 min] time = 15 min 0 sec
SF  = 52930
CRC = 126
LOS = 0
LOF = 0
ES  = 41
#
#

I shall plug the WAG back in and capture some stats shortly.

regarding quiet test: Do you want me to plug the router and a wired phone through a filter or just use a splitter?

Which router (I'm getting confused!).

DL/UL a file while I listen for any noise, yes?
Logged

Black Sheep

  • Helpful
  • Addicted Kitizen
  • *
  • Posts: 5722
Re: request timed out
« Reply #5 on: March 26, 2012, 06:51:02 PM »

Yes, plug your WAG back in and see what your attenuation is with that. All electrical/electronic items have their own internal resistance. You can't raise a case for attenuation issues if you're quoting figures from 2 different pieces of equipment. There has to be a 'known constant', and that can only be acieved by using the same router.

Not sure what you mean re: splitter/filter ?? Just to save any embarrasment, it would be best to plug just a single filter into the test socket. Out of the back of this filter you can plug the router in one port, and the corded phone in another. Once the DSL light on the router is lit, then proceed with the 'Quiet Line' test. I don't suppose D/L a file would do any harm, but it's not something I've ever done whilst faulting.

The aim of this test is to see if your router loses synch whilst the phone is in use, and if you can access an error log, to see if there are massive incrementation of CRC's on DS or US whilst the phone is in use ? It's a kind of easy test to perform whilst ensuring the line is under 'full load'. Another simple test is to leave the set up as mentioned afore, and keep ringing your landline. Ringing voltage is almost double nominal dial-tone voltage, and is an AC waveform, not DC. This high burst of ringing voltage/current can sometimes detect errors better than 'Quiet Line Test'.

Failing that ............. get Walter to nip round with his new 301C 'mole'. ;D
Logged

coolsnakeman

  • Reg Member
  • ***
  • Posts: 421
    • IT Support Belfast
Re: request timed out
« Reply #6 on: March 27, 2012, 07:45:31 AM »

Not sure what you mean re: splitter/filter ??

Was kind of thinking that myself. Only device that should be used into the test socket directly is a filter. No splitter should be in place before this. Same applies when connecting into the master socket filter should always be your first device into the socket. After you have carried out what BS has suggested i would also suggest a quiet line test done in the test socket with no filter and no router connected to see if you continue to get that humming noise. Cause rightly so if you do get a humming noise on your line with your broadband kit disconnected your broadband SP is not going to take ownership of the fault and pass you onto BT.

Regards
Gary
Logged

clueless

  • Member
  • **
  • Posts: 19
Re: request timed out
« Reply #7 on: March 27, 2012, 10:03:13 AM »

Thanks guys.

I'll do the tests this morning.

Just explain the filter/splitter thing: among other things I have tried, I have used a splitter plugged into the MS- one socket for the router ONLY and one socket with a filter fitted for the wireless phones.

I currently the usual filter in the MS with the router and wireless phones though it.
Logged

coolsnakeman

  • Reg Member
  • ***
  • Posts: 421
    • IT Support Belfast
Re: request timed out
« Reply #8 on: March 27, 2012, 11:28:12 AM »

Doesn't sound like a standard setup to me. As i said the only splitter that should go into the master socket is an ADSL filter unless you have a filtered faceplate (SSFP) which in that case you don't need any filters on your master socket or any of your extension sockets. The other 2 splitters i know off are a standard telephone splitter that you would use off course for a telephone or a sky tv top box etc and the other splitter i know off is one that goes into the back of your router that is used generally for VOIP which is a facility that comes with the HGV2700 and HGV2701. However if you have tried everything from the test port via a filter and the phone without a filter and have also tried another phone you know is working ok to test for noise and you are still getting the same problems then i would point the problem out towards the external network.

Regards
Gary
Logged

coolsnakeman

  • Reg Member
  • ***
  • Posts: 421
    • IT Support Belfast
Re: request timed out
« Reply #9 on: March 27, 2012, 11:31:27 AM »

Try not to get to technical with it. Your job is to simple prove these issues are not related to your own kit. Once you have done that leave the rest to the engineers ain't that right BS  :lol:
Logged

clueless

  • Member
  • **
  • Posts: 19
Re: request timed out
« Reply #10 on: March 27, 2012, 12:01:28 PM »

Not to get bogged down by this- this splitter (as I call it) is just an adapter with a male phone plug on one side and several female sockets on the other.

Anyhoo I have attached the line stats with the WAG reinstalled then the Billion installed once again.

The Billion SNR has defaulted from my manual setting which accounts for the big change in that value.

I did a quite line test with the router and phone plugged in, I get the hum but no crackles.

My router doesn't seem to have an error log, just a system log which doesn't show much of anything.

Should I maybe take a snapshot of the line stats before making the phone ring for a while then get the stats again afterwards to show if an unsual amount errors occurred, would this be worth while to you?

Incidentally I have requested interleaving to be re-enabled.
« Last Edit: March 27, 2012, 12:05:09 PM by clueless »
Logged

Black Sheep

  • Helpful
  • Addicted Kitizen
  • *
  • Posts: 5722
Re: request timed out
« Reply #11 on: March 27, 2012, 01:27:04 PM »

Try not to get to technical with it. Your job is to simple prove these issues are not related to your own kit. Once you have done that leave the rest to the engineers ain't that right BS  :lol:

If they must. Suppose I've gotta earn this £80K wage doing something. ;) ;D
Logged

coolsnakeman

  • Reg Member
  • ***
  • Posts: 421
    • IT Support Belfast
Re: request timed out
« Reply #12 on: March 27, 2012, 01:31:57 PM »

Get line stats before making the call then line stats when you make a call. I would also do a quiet line test with the phone plugged into the test socket on its own with no filter or router attached and see if you still get that humming noise. BS you trying to make me jealous  :P

Gary
Logged

clueless

  • Member
  • **
  • Posts: 19
Re: request timed out
« Reply #13 on: March 27, 2012, 02:25:45 PM »

I let the phone ring for 10 secs before getting the stats while it was still ringing.

The humming is present with only the wired phone plugged into the test socket.
Logged

coolsnakeman

  • Reg Member
  • ***
  • Posts: 421
    • IT Support Belfast
Re: request timed out
« Reply #14 on: March 27, 2012, 03:26:09 PM »

Can't see a difference in the 2 of those results i could be missing something so i will let one of the other guys read over them results. Humming still there with phone connected on its own is def suggesting a line fault. BS what do you make of this i think he should request a PSTN engineer to be sent out to this maybe CE or LN?? Either that or i would suggest you request BT to send over to diagnostics for further diagnostics to be run on this. Chances are DT may task to a LN engineer to look at this. You could go down the SFI visit route but you need to lie to your broadband service provider cause they are not going to send out an SFI as long as that humming noise is there with there broadband kit disconnected cause i know i wouldn't.

Regards
Gary
Logged
Pages: [1] 2 3
 

anything