how-to block ads
|
matt38
@frontiernet.net
| frontier DSL sync loss at night
i have had frontier for 4 years now and had nothing but line issues on and off. sometimes the connection was stable for a month or two, the next month it was unsyncing every 25 seconds for 2 days up to a month non stop at random times. occassionally it will take a break and stats would return back to normal. i would have to attribute a majoirty of my earlier problems due to faulty equipment, wiring, bad splitters and possiable EMI interference which about 5 or 6 tech calls solved for the most part for about another month until something else went wrong.
my connection since jan 09 has been pretty good, i think a couple weeks there were some problems but they cleared up for no apparent reason, for the most part i was 3 megs up for almost 3 months without a unsync or having to power cycle the dsl box. of course until about late july, early august my connection has been consistantly degrading and unsyncing every night at 8:20pm-6:20am, and the last few days earlier than its normal time. i have noticed that the street lights on the main road (since there are none on mine) do go on and off at those specific times.
i have been away from home for a few weeks and couldn't be waiting around 3-5 days for a tech to look, so i have been trying to do an isolation test to see if anything around my dsl modem or inside wiring is to blame, since the majority of problems are generally just that. i have found some things that cause EMI but during the day, those things do not affect it at all (dimmer switch, some eletrical in the basement where the tech strung the CAT3 cable).
i think the best part is using the AM radio walkman, putting it next to my DSL line and my cable TV line (come in same spot about, foot away from NID outside) 3 feet downstairs from the NID outside, the AM channels come in perfectly clean like its acting as a antenna somehow.
i was going to wait and post this tomorrow, after i tried to use the NID to test my connection later tonight when it starts acting up.. only to find it doesn't even have a test socket.
from what i can tell, they installed a "home-run"? for my dsl line last time and strung cat 3 wire to a phone jack for that and kept the regular phone line on the cat 1 this house originally had.
i just dont know where to go from here, the last time i called in for tech support it didn't do much as the problems are at night mostly and they say its all good during the day. i have had 2 new dsl modems, seimans gigaset 567, been swapping out phone cords, moving the box around and nothing seems to cure this new problem. its just strange because im 3500mbs/350kbs up during the day fine, no problems.
eventually, at night 150kbs/350kbs and about 45+ unsyncs.
looking over my stats..
the US SnR is a static 20
the DS SnR is 2 atm, (always was 15 daytime, 6-8 night)
US atten static 31
DS atten 46.5-50.5
is there anything else i can try before i tech call it out?
any other information i should post? | |
Smith6612
Premium
join:2008-02-01
united state
 ·Dish Network
 ·Verizon Online DSL
·FrontierNet Intern..
| Street lamps on copper wiring that have problems will cause the DSL to drop. It's a common thing seen over at the Verizon DSL forum when drops only take place at night. From the sounds of it, you've done every form of troubleshooting I would have suggested. Your attenuation is pretty high but the SNR holds during the day. The downstream however is causing the resyncing problem, with the low SNR and lower speeds after a resync, so if anything, I would have Frontier come out and either check your current line for any "shiners" or bare wiring on the wire, as well as any bad splices to try to improve the line. You could also ask Frontier if they might have ADSL2 or ADSL2+ available in your area to stick your DSL line onto.
But if you mention your findings to a Frontier tech, he should know what to do.
--
It's all fun and games in a Team Fortress 2 battle until your sentry gun is sapped by the Spycrab! | |
matt38
@frontiernet.net
| reply to matt38
all right, i was in the middle of getting ahold of a rep from frontier.. when i refreshed the page  . its odd now it seems to be getting gradually worse though, i dropped about 3 times before the usual timeframe today, and a couple times yesterday.
i had earlier restrung the cat3 line, because it was close to electrical wires, cable tv lines, and other things in the basement that i picked up some electrical interference with my radio, to possibly improve or fix it.
Frontier should be out by friday or monday to look at things :S
i didn't post stats before, seems like the seimans clears a majority upon a unsync, but from the last 15 minutes or so the RX errors seem extremly high? (not even sure what the first stats actually mean, for data/packets/corrections?)
High Speed Internet Status
Status ATU-C Current Tx Rate(bits/sec) 3712000
ATU-R Current Tx Rate(bits/sec) 448000
system time 09-02-2009 18:17:09
TX CRC 1
TX FEC 0
RX CRC 115
RX FEC 615918
LOS 0
SEF 0
LOS (sec) 0
SEF (sec) 0
Err (sec) 82
Rx (blocks) 53733
tx (blocks) 53733
US SnR 20.0
DS SnR 12.5
US Atten 31.0
DS Atten 50.5
US power 5.5
DS power 9.0
wish copy paste worked!
Current Log Entries
0000-00-00 00:00:01 E |System |Current Mode: Bridge-Router
0000-00-00 00:00:01 E |DSL |Boost DSP
0000-00-00 00:00:02 E |DSL |DataPump Version - 07.00.02.00
0000-00-00 00:00:02 E |DSL |State: WAITING
0000-00-00 00:00:03 E |Ethernet |Link 1 Up - 10Base-T Full Duplex
0000-00-00 00:00:07 E |DSL |State: INITIALIZING
0000-00-00 00:00:11 E |DSL |State: WAITING
0000-00-00 00:00:11 E |DHCP Server |Address 192.168.254.1 given out to 00:90:00:05:82:9e
0000-00-00 00:00:11 E |DHCP Server |1 Address(es) leased
0000-00-00 00:00:24 E |DSL |State: INITIALIZING
0000-00-00 00:00:28 E |DSL |State: WAITING
0000-00-00 00:00:31 E |CWMP |CWMP agent cannot reach the ACS named »acs.isis.frontiernet.net:1111/ACS-INTF
0000-00-00 00:00:32 E |DSL |State: INITIALIZING
0000-00-00 00:00:36 E |DSL |State: WAITING
0000-00-00 00:00:40 E |DSL |State: INITIALIZING
0000-00-00 00:00:44 E |DSL |State: WAITING
0000-00-00 00:00:49 E |DSL |State: INITIALIZING
0000-00-00 00:00:53 E |DSL |State: WAITING
0000-00-00 00:00:57 E |DSL |State: INITIALIZING
0000-00-00 00:01:05 E |DSL |HYBRID 3
0000-00-00 00:01:05 E |DSL |Link up 1 US 448 DS 3712 (INTL:G.dmt)
0000-00-00 00:01:05 E |PPPoE |Sending PADT/LCP Terminate for Session ID = ABDF
0000-00-00 00:01:06 E |PPPoE |oe00: tx PADI, id: 0000, ac: (NULL), sn: (NULL), MAC: FF:FF:FF:FF:FF:FF
0000-00-00 00:01:07 E |PPPoE |oe00: tx PADI, id: 0000, ac: (NULL), sn: (NULL), MAC: FF:FF:FF:FF:FF:FF
0000-00-00 00:01:09 E |PPPoE |oe00: tx PADI, id: 0000, ac: (NULL), sn: (NULL), MAC: FF:FF:FF:FF:FF:FF
0000-00-00 00:01:09 E |PPPoE |oe00: rx AC Name: FELD7206-01
0000-00-00 00:01:09 E |PPPoE |oe00: tx PADR, id: 0000, ac: (NULL), sn: (NULL), MAC: 00:15:C6:52:28:A8
0000-00-00 00:01:09 E |PPPoE |oe00: rx PADS id: BC70 MAC 00:15:C6:52:28:A8
0000-00-00 00:01:13 E |PPP |LCP neg PAP
0000-00-00 00:01:13 E |PPP |LCP up
0000-00-00 00:01:13 E |PPP |IPCP nak option: 3
0000-00-00 00:01:13 E |PPP |IPCP nak option: 129
0000-00-00 00:01:13 E |PPP |IPCP nak option: 131
0000-00-00 00:01:13 E |PPP |IPCP up ip: 74.44.75.167, gw: 74.44.72.1
0000-00-00 00:01:13 E |PPP |IPCP dns: 66.133.170.2, 66.133.150.12
09/02/2009 17:56:03 EDT E |SNTP Client |Updated system time from Primary server 71.252.193.25
09/02/2009 18:01:30 EDT E |DSL |Link Down
09/02/2009 18:01:30 EDT E |PPP |LCP down
09/02/2009 18:01:30 EDT E |PPP |IPCP down
09/02/2009 18:01:30 EDT E |DSL |State: WAITING
09/02/2009 18:01:35 EDT E |DSL |State: INITIALIZING
09/02/2009 18:01:39 EDT E |DSL |State: WAITING
09/02/2009 18:01:43 EDT E |DSL |State: INITIALIZING
09/02/2009 18:01:47 EDT E |DSL |State: WAITING
09/02/2009 18:01:52 EDT E |DSL |State: INITIALIZING
09/02/2009 18:01:59 EDT E |DSL |HYBRID 3
09/02/2009 18:01:59 EDT E |DSL |Link up 2 US 448 DS 3712 (INTL:G.dmt)
09/02/2009 18:02:00 EDT E |PPPoE |oe00: tx PADT, id: BC70, ac: (NULL), sn: (NULL), MAC: FF:FF:FF:FF:FF:FF
09/02/2009 18:02:00 EDT E |PPPoE |oe00: tx PADI, id: 0000, ac: (NULL), sn: (NULL), MAC: FF:FF:FF:FF:FF:FF
09/02/2009 18:02:02 EDT E |PPPoE |oe00: tx PADI, id: 0000, ac: (NULL), sn: (NULL), MAC: FF:FF:FF:FF:FF:FF
09/02/2009 18:02:02 EDT E |PPPoE |oe00: rx AC Name: FELD7206-01
09/02/2009 18:02:02 EDT E |PPPoE |oe00: tx PADR, id: 0000, ac: (NULL), sn: (NULL), MAC: 00:15:C6:52:28:A8
09/02/2009 18:02:02 EDT E |PPPoE |oe00: rx PADS id: BF21 MAC 00:15:C6:52:28:A8
09/02/2009 18:02:04 EDT E |PPP |LCP neg PAP
09/02/2009 18:02:04 EDT E |PPP |LCP up
09/02/2009 18:02:04 EDT E |PPP |IPCP nak option: 3
09/02/2009 18:02:04 EDT E |PPP |IPCP nak option: 129
09/02/2009 18:02:04 EDT E |PPP |IPCP nak option: 131
09/02/2009 18:02:04 EDT E |PPP |IPCP up ip: 74.44.76.218, gw: 74.44.72.1
09/02/2009 18:02:04 EDT E |PPP |IPCP dns: 66.133.170.2, 66.133.150.12
09/02/2009 18:02:22 EDT E |PPPoE |oe: rx PADT err: no session
09/02/2009 18:06:54 EDT E |Firewall |D:19:0 TCP 216.34.207.157:80 -> 192.168.254.1:2839 len=40 id=47299 DF=0 MF=0
if that even helps D:
| |
Smith6612
Premium
join:2008-02-01
united state
·Dish Network
·Verizon Online DSL
·FrontierNet Intern..
1 edit | reply to matt38
I don't know why the Seimens modems like to clear the log, more or less the DSL stats upon resync, but that log does provide some useful information. It shows me that your line is on Interleaved ADSL (G.DMT) mode, and I can see that you are set to the full 3Mbps profile. Your error count is pretty high, as it shows the DSL signal's SNR is bombing down during transmit and spiking back up to where it should be. Keep an eye on the SNR throughout the night, and see if any street lamps near you might have the most effect on the line.
But good luck with the tech visit! Hopefully he can find the problem if there is one.
By the way, set the PC/Device using Ethernet to use 100Mbps Full Duplex. I have no idea why that is set to 10BaseT-Full Duplex :S
As for this link the modem is reporting: »acs.isis.frontiernet.net:1111/ACS-INTF
That doesn't resolve to a thing (gives me an error) so I have no clue on what that might be.
--
It's all fun and games in a Team Fortress 2 battle until your sentry gun is sapped by the Spycrab! | |
matt38
@frontiernet.net
| reply to matt38
well i fixed the RX errors, i was getting like a million now its down to a few hundred or less, the phone cable i left in there was defective, didn't think one could have that much of an impact so detrimental.
i found a blue/white wire in the basement was broken at the copper around the nut. i tugged it and my phone went dead and i dont know what exactly that wire does for my main phone and dsl, since i thought they were on seperate lines. (ring/tip on my dsl line? house is so archaic the phone equipment is pathetic)
however the SnR margin is still dropping to a very gross low number as i type, but still its remaining at 3 megs and havn't dropped yet which is definetly odd but i wont hold my breath.
i have looked through my computer (network devices etc) and dsl modem i dont see any options to change my option to 100mbs full duplex.. did alittle google search, is it a command prompt or something? or am i totally missing it?
the tech will be here friday to inspect, and while i was on the phone, they told me that i am no longer bound into there contract (trying to get me to renew haha), so if the problem persists after this weekend, ill be switching back to roadrunner. i would've done it earlier, but TWC was trying to do what frontier did and impose a 5 gig cap, but rochester protested, all the while i thought my contract was renewed in jan. they didn't say anything they just added 10 bucks on the bill, but the service from frontier was good up until now so i didn't really consider it that much.
thansk for your time though, if i get answers from tech support if they find anything, ill post it here. | |
mkrasz
join:2000-03-06
Rochester, NY
| The acs.isis.frontiernet.net link is related the modem's TR-069 function (remote management). It is not used as the link 'goes nowhere'.
If using Windows, open the Device Manager and under Network Adapters right click on your adapter and choose properties. Look for an Advanced tab. Very often there is a speed/duplex property that can be set. You need to set speed/duplex to 'auto negotiation'. If you set it for 100 full, the modem will run at 100 half (cause it failed its auto negotiation). There is no place to adjust this in the modem. | |
Smith6612
Premium
join:2008-02-01
united state
·Dish Network
·Verizon Online DSL
·FrontierNet Intern..
1 edit | reply to matt38
Well, glad to see you may have found the source of some of the problems. A bad/degraded copper cable will cause things like that to happen. I've seen it in some of the older homes in my area that are having buzzing take place on their phone lines. Of course, these houses have 60+ year old copper trunks fueling them, so even if the copper hasn't turned to dust in the home (I've seen this. It isn't nice when you have to run a new wire because of this), the wire pair you're on is usually to blame at least in my area. For the wire duplex, mkrasz explained it all for you. I have found that on some of the network cards that come with PCs, if the card's advanced properties settings don't show something such as link speed or link duplex, if the card has it's own utility in the control panel (probably in the "others" section) you can usually change it in there. Of course if the card is already on Auto Negotiate, there is probably something wrong with the Ethernet cable being used.
@mkrasz: That explains the link. I'm wondering if that is something new I've never seen before that might be coming with the SE567's. I have a SpeedStream 6520 that is 4 years old and it doesn't show that link.
--
It's all fun and games in a Team Fortress 2 battle until your sentry gun is sapped by the Spycrab! | |
dee26527
@frontiernet.net
|  Okay, I've been looking around for the solution to this for awhile... I get speeds 30k and below at night on Frontier DSL. I have had the techs out at my house a few times, each time they have replaced a DSL filter on a phone and said that "May" be the problem. I've tried the box at various points in the house, and no luck, not until 6:20am, when the speed shoots back up to 3mb+.
One thing I noticed in the stats (and thanks for everyone on these forums who has helped me decode what they mean) is that during the loss of connectivity, the stats listed under ATM Statistics -> PDU Counters ->Rx Errors is over 3,000. I reset the stats and watch the number climb at a rate of 10 or 20 per refresh. Can anyone let me know what might be causing this, and why it seems to happen only at night? I'm rarely home during the day, and, of course, when the tech guys come in everything is pretty much fine. | |
mkrasz
join:2000-03-06
Rochester, NY | reply to Smith6612
@smith - The 6520 doesn't support TR-069. It is new with the 567. | |
Smith6612
Premium
join:2008-02-01
united state
·Dish Network
·Verizon Online DSL
·FrontierNet Intern..
1 edit | reply to dee26527
Well, I can say that on my line I get those errors as well. My line on the DSL stats doesn't show any errors one bit occurring throughout the day (I check it on a daily basis) however I found that whenever I'm downloading or uploading, I'll see ATM errors (mainly error packets on the upstream, discard packets on the downstream). I believe this is just due to the way the ATM network is (it's also inefficient in a way), and I think it might have something to do with data prioritization. It may have an effect on the line though if more of those are showing at night (which may or may not be due to line usage or the line noise). However, when I get these errors on the ATM network I'm always pulling my full speed (3200kbps download, 290kbps upload) with no CRC errors on the downstream or upstream on my line. I did ask one of the local techs about my case of these ATM errors, and he said that it does sound like a normal thing and nothing of concern at the moment. I've noticed this happens on every other Frontier line in my area, as well as someone here posted up about such errors as well and their line was fine despite a low SNR.
@mkrasz: That would explain it Thanks for the info!
--
It's all fun and games in a Team Fortress 2 battle until your sentry gun is sapped by the Spycrab! | |
-
|
