AT&T 2Wire 2701HG-B Disconnects / Drops

[Distressedtothe…]

When I wake up I have all solid lines on my router and then once I get on my computer and open my Internet, to put it in the search bar, my Internet shuts off

[desmolift]

@glassheart

Disabling packet flooding did not work for me.  Changing my wireless bandwidth from 54Mbs to 11Mbs did work.  There are many folks having trouble with this 2wire router.  It appears that reducing the load on the router, either by reducing connection speeds or reducing the firewall features seems to help the performance and the stability of this device.  Try either or both and see if it helps.

[desmolift]

I completed installation of a new 2701 2wire.... and I get the same results, not surprising, ERR_DMA causing my DSL connection to go down.  This is disappointing, AT&T needs to ditch this modem, it doesn't work.

[rvpdsl]

Hi desmolift,

Was your 2Wire under warranty that they replaced it for $12 shipping only? I've been having this problem, called tech support, they found a problem on the line, changed a cable outside, and the problem continues. I was told that since my modem is out of warranty, any tech-support check leading to modem replacement will incur a charge.

Thank you.

[rvpdsl]

A switch to 802.11b from 802.11b/g seems to work for me. I used to have several DSL disconnects, "signal lost" events per day. Since I switched to 802.11b about 8 hours ago I haven't had a single one. However I have a wireless adapter that doesn't like 802.11b; now I have to spend more time and money on fixing that.

@desmolift: I think your analysis of ERR_DMA maybe the root-cause. Thank you for that information.

@glassheart828 and someone else: Thank you for the tip about switching to 802.11b. This hack works for me so far (since the last 8 hours or so). This limits my bandwidth (LAN too) to 11Mbps. This is good data for root-causing the problem but not a long-term fix.

[desmolift]

@rvpdsl

Demand a replacement 2701, they will just charge you shipping.  State its due to ERR_DMA, they know of this problem... but it won't solve the problem in my experience.

[rvpdsl]

@desmolift:

I will do that on Monday, thank you.

By the way, my Software/Firmware rev is 5.29.109.5 and the system says that it's uptodate. I wonder if the upgrade of .13 is for new HW. What does it say in the Vendor field in the Training History on your box? For the most part the Vendor field in the DSL Diagnostics Training History has been Broadcom. I have seen some folks w/ Alcatel and other HW but not sure what SW/FW they have on their system.

[desmolift]

I looked it up in the manual... this is the DSLAM vendor.

[jmuoio]

Did you know  that /mdc link hasn't worked for over a year.  But, if you are with AT&T AND you are a software guy, I'd be happy to send you whatever you want and you can get into my gateway to figure out the issue.  Something is going on and your company keeps throwing line techs and hardware at it, when I think it's software.  I've told at least a dozen people in your support organization that there are WRN error entries in the System log every time I have a wirelss episode.  I think you may be having some sort of resource issue in the firmware like it's running out of heap or something.  But, at the moment, I can't a DHCP address on my laptop, instead having to fall back on my alternate configuration.  I'm enclosing a cut/paste from my error log for the most recent/current episode where I lose all wireless connectivity and can't get a new address.  If you are with AT&T please help me.

Thank you,

John

WRN	2011-12-12T07:19:19-08:00	iswphy: port 2, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:20:23-08:00	iswphy: port 0, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:20:35-08:00	iswphy: port 0, stat 3 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:20:59-08:00	iswphy: port 1, stat 3 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:21:35-08:00	iswphy: port 3, stat 0 possible bad read 0x0005 -> 0x0002
WRN	2011-12-12T07:28:07-08:00	iswphy: port 5, stat 2 possible bad read 0x0005 -> 0x0002
WRN	2011-12-12T07:28:27-08:00	iswphy: port 0, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:28:47-08:00	iswphy: port 1, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:28:55-08:00	iswphy: port 1, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:34:27-08:00	iswphy: port 0, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:36:07-08:00	iswphy: port 5, stat 2 possible bad read 0x0005 -> 0x0002
WRN	2011-12-12T07:36:47-08:00	iswphy: port 1, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:36:51-08:00	iswphy: port 1, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:37:11-08:00	iswphy: port 2, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:38:23-08:00	iswphy: port 0, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:38:31-08:00	iswphy: port 0, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:38:35-08:00	iswphy: port 0, stat 3 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:42:07-08:00	iswphy: port 5, stat 2 possible bad read 0x0005 -> 0x0002
WRN	2011-12-12T07:42:27-08:00	iswphy: port 0, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:48:07-08:00	iswphy: port 5, stat 2 possible bad read 0x0005 -> 0x0002
WRN	2011-12-12T07:50:27-08:00	iswphy: port 0, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:50:47-08:00	iswphy: port 1, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:58:31-08:00	iswphy: port 0, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T07:58:47-08:00	iswphy: port 1, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:00:07-08:00	iswphy: port 5, stat 2 possible bad read 0x0005 -> 0x0002
WRN	2011-12-12T08:11:11-08:00	iswphy: port 2, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:14:47-08:00	iswphy: port 1, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:19:36-08:00	iswphy: port 3, stat 0 possible bad read 0x0005 -> 0x0002
WRN	2011-12-12T08:20:08-08:00	iswphy: port 5, stat 2 possible bad read 0x0005 -> 0x0002
WRN	2011-12-12T08:20:24-08:00	iswphy: port 0, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:20:28-08:00	iswphy: port 0, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:20:36-08:00	iswphy: port 0, stat 3 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:20:52-08:00	iswphy: port 1, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:20:56-08:00	iswphy: port 1, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:21:00-08:00	iswphy: port 1, stat 3 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:21:12-08:00	iswphy: port 2, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:21:20-08:00	iswphy: port 2, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:24:28-08:00	iswphy: port 0, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:44:28-08:00	iswphy: Previous log entry repeated 1 times
INF	2011-12-12T08:51:26-08:00	rtp: RTCPGetReports: Use symmetric owd
WRN	2011-12-12T08:52:08-08:00	iswphy: port 5, stat 2 possible bad read 0x0005 -> 0x0002
INF	2011-12-12T08:53:02-08:00	rtp: RTCPGetReports: Use symmetric owd
WRN	2011-12-12T08:54:32-08:00	iswphy: port 0, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:55:00-08:00	iswphy: port 1, stat 3 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:55:12-08:00	iswphy: port 2, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:56:28-08:00	iswphy: port 0, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:56:36-08:00	iswphy: port 0, stat 3 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:57:20-08:00	iswphy: port 2, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T08:57:36-08:00	iswphy: port 3, stat 0 possible bad read 0x0005 -> 0x0002
WRN	2011-12-12T09:05:12-08:00	iswphy: port 2, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:06:28-08:00	iswphy: port 0, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:06:52-08:00	iswphy: port 1, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:12:36-08:00	iswphy: port 0, stat 3 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:12:56-08:00	iswphy: port 1, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:13:00-08:00	iswphy: port 1, stat 3 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:13:12-08:00	iswphy: port 2, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:13:20-08:00	iswphy: port 2, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:16:37-08:00	iswphy: port 0, stat 3 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:34:33-08:00	iswphy: port 0, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:34:49-08:00	iswphy: port 1, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:37:01-08:00	iswphy: port 1, stat 3 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:38:09-08:00	iswphy: port 5, stat 2 possible bad read 0x0005 -> 0x0002
WRN	2011-12-12T09:38:29-08:00	iswphy: port 0, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:40:33-08:00	iswphy: port 0, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:40:53-08:00	iswphy: port 1, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:41:21-08:00	iswphy: port 2, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:41:37-08:00	iswphy: port 3, stat 0 possible bad read 0x0005 -> 0x0002
WRN	2011-12-12T09:42:49-08:00	iswphy: port 1, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:42:57-08:00	iswphy: port 1, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:43:13-08:00	iswphy: port 2, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T09:56:57-08:00	iswphy: port 1, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:08:25-08:00	iswphy: port 0, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:08:33-08:00	iswphy: port 0, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:16:10-08:00	iswphy: port 5, stat 2 possible bad read 0x0005 -> 0x0002
WRN	2011-12-12T10:18:50-08:00	iswphy: port 1, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:22:30-08:00	iswphy: port 0, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:23:02-08:00	iswphy: port 1, stat 3 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:26:10-08:00	iswphy: port 5, stat 2 possible bad read 0x0005 -> 0x0002
WRN	2011-12-12T10:26:34-08:00	iswphy: port 0, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:26:50-08:00	iswphy: port 1, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:26:54-08:00	iswphy: port 1, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:26:58-08:00	iswphy: port 1, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:27:02-08:00	iswphy: port 1, stat 3 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:27:14-08:00	iswphy: port 2, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:27:22-08:00	iswphy: port 2, stat 2 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:27:38-08:00	iswphy: port 3, stat 0 possible bad read 0x0005 -> 0x0002
WRN	2011-12-12T10:28:26-08:00	iswphy: port 0, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:28:30-08:00	iswphy: port 0, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:28:38-08:00	iswphy: port 0, stat 3 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:40:26-08:00	iswphy: port 0, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:40:30-08:00	iswphy: port 0, stat 1 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T10:40:50-08:00	iswphy: port 1, stat 0 possible bad read 0x0005 -> 0x0000
WRN	2011-12-12T11:10:30-08:00	iswphy: port 0, stat 1 possible bad read 0x0006 -> 0x0000
WRN	2011-12-12T11:11:02-08:00	iswphy: port 1, stat 3 possible bad read 0x0006 -> 0x0000
WRN	2011-12-12T11:12:50-08:00	iswphy: port 1, stat 0 possible bad read 0x0006 -> 0x0000
WRN	2011-12-12T11:12:54-08:00	iswphy: port 1, stat 1 possible bad read 0x0006 -> 0x0000
WRN	2011-12-12T11:16:30-08:00	iswphy: port 0, stat 1 possible bad read 0x0006 -> 0x0000
WRN	2011-12-12T11:17:38-08:00	iswphy: port 3, stat 0 possible bad read 0x0006 -> 0x0002
WRN	2011-12-12T11:18:54-08:00	iswphy: port 1, stat 1 possible bad read 0x0006 -> 0x0000
WRN	2011-12-12T11:22:50-08:00	iswphy: port 1, stat 0 possible bad read 0x0006 -> 0x0000

Next

[jmuoio]

I have the latest and greatest replacement and it didn't do anything. I've had new cables (5 times) new gateway, new placement, dedicated line, moved the device, multiple line techs, multiple prem techs and still, when I have these "possible bad reads" I can't even get to the gateway with the IP address in a browser over the wireless. It's not a hardware issue, it's programming/firmware.

[BruceGlenn]

Your instructions were the solution
Had same problems forever
Thanks a gillion !!! 

[luka123]

Can someone help here. Few daus ago I noticed my 2Wire router just stopped working properly. It was rock solid for 3 years. It powers up and power is solid green light. Once in awhile Ethernet lights gets red, blincks , and I hear noise like modem is trying to conect, but lights goes off. And then again after few minutes, and so forth.

Is this bad modem or something else? Thanks .

[carlclaunch]

My system drops many times a day with red blinking light, have had too many rounds calling help desk who test line and say all is okay, even with hundreds of errors per day in the statistics.

Here is the MDC console diagnostics output - any ideas what is going wrong and where to check next?

General Information
DSL Line (Wire Pair):	Line 1 (inner pair)
Downstream Rate Cap:	6016 kbps
Downstream Atten. at 300kHz:	37.3 dB
Uncancelled Echo:	-3.7 dB	Ok
VCXO Frequency Offset:	-51.8 ppm	Ok
Final Rx Gain:	29.9 dB	Ok
Impulse Noise Comp. Tones:	0	Ok
Excessive Impulse Noise:	0	Ok
Impulse noise protection:	0.00
Delay of latency path:	0.25 ms

[Removed Over-sized Table to preserve message width]

[carlclaunch]

Had to append this to previous message as someone helpfully removed the diagnostic info you need:

Training History
    Downstream         Upstream
Time     Line         Rate     Max1     Max2     Max3     Mgn1     Mgn2     Attn     Pwr     CRCs     FECs     INP     DLY         Rate     Max     Mgn     Attn     Pwr     CRCs     FECs         Mode     Vendor     State     Exit Code     Echo     VCXO     Rx Gain     INC Tones
2012/01/03 21:37:35 PST     1         6016     8128     8128     8128     16.0     16.0     36.6     13.9     0     0     0.00     0.25         768     1144     19.0     18.5     11.9     0     0         G.DMT Annex A     Alcatel     229/103     ERR_DMA     -3.5     -51.3     29.9     0
2012/01/03 21:37:42 PST     1         0     0     0     0     0.0     0.0     0.0     0.0     0     0     0.00     0.00         0     0     0.0     0.0     0.0     0     0         Unknown     Alcatel     11/13     ERR_DMA     0.0     0.0     0.0     0
2012/01/03 21:43:59 PST     1         6016     8128     8128     8128     16.0     16.0     36.6     14.1     1     0     0.00     0.25         768     1148     19.0     18.5     11.9     0     0         G.DMT Annex A     Alcatel     229/103     ERR_DMA     -3.6     -51.2     29.9     0
2012/01/03 21:48:11 PST     1         6016     8128     8128     8128     16.0     17.0     36.6     14.8     0     0     0.00     0.25         768     1144     19.0     18.5     11.9     0     0         G.DMT Annex A     Alcatel     229/103     ERR_DMA     -3.7     -51.3     29.9     0
2012/01/03 21:51:49 PST     1         6016     8128     8128     8128     16.0     16.0     36.6     14.5     0     0     0.00     0.25         768     1144     19.0     18.5     11.9     0     0         G.DMT Annex A     Alcatel     229/103     ERR_DMA     -3.7     -51.8     29.9     0
2012/01/03 21:52:07 PST     1         0     0     0     0     0.0     0.0     0.0     0.0     0     0     0.00     0.00         0     0     0.0     0.0     0.0     0     0         Unknown     Alcatel     24/18     ERR_INTERNAL     0.0     -43.5     18.4     0
2012/01/03 22:00:06 PST     1         6016     8128     8128     8128     16.0     17.0     36.6     14.5     1     0     0.00     0.25         768     1144     19.0     18.5     11.9     0     0         G.DMT Annex A     Alcatel     229/103     ERR_DMA     -3.6     -51.4     29.9     0
2012/01/03 22:00:13 PST     1         0     0     0     0     0.0     0.0     0.0     0.0     0     0     0.00     0.00         0     0     0.0     0.0     0.0     0     0         Unknown     Alcatel     11/13     ERR_DMA     0.0     0.0     0.0     0
2012/01/03 22:02:15 PST     1         6016     8128     8128     8128     16.0     16.0     36.6     14.1     0     0     0.00     0.25         768     1148     18.0     18.5     11.9     0     0         G.DMT Annex A     Alcatel     229/103     ERR_DMA     -3.6     -51.3     29.9     0
2012/01/03 22:08:54 PST     1         6016     8128     8128     8128     16.0     17.0     36.6     14.3     0     0     0.00     0.25         768     1148     19.0     18.5     11.9     0     0         G.DMT Annex A     Alcatel     229/103     ERR_DMA     -3.7     -51.4     29.9     0
2012/01/03 22:09:09 PST     1         0     0     0     0     0.0     0.0     0.0     0.0     0     0     0.00     0.00         0     0     0.0     0.0     0.0     0     0         Unknown     Alcatel     18/15     ERR_DMA     0.0     -43.5     18.4     0
2012/01/03 22:09:25 PST     1         0     0     0     0     0.0     0.0     0.0     0.0     0     0     0.00     0.00         0     0     0.0     0.0     0.0     0     0         Unknown     Alcatel     26/19     ERR_DMA     0.0     -43.5     2.3     0
2012/01/03 22:26:18 PST     1         6016     8128     8128     8128     16.0     17.0     36.6     14.9     0     0     0.00     0.25         768     1144     19.0     18.5     11.9     0     0         G.DMT Annex A     Alcatel     229/103     ERR_DMA     -3.6     -51.4     29.9     0
2012/01/03 22:26:25 PST     1         0     0     0     0     0.0     0.0     0.0     0.0     0     0     0.00     0.00         0     0     0.0     0.0     0.0     0     0         Unknown     Alcatel     11/13     ERR_DMA     0.0     0.0     0.0     0
2012/01/03 22:26:33 PST     1         0     0     0     0     0.0     0.0     0.0     0.0     0     0     0.00     0.00         0     0     0.0     0.0     0.0     0     0         Unknown     Alcatel     24/18     ERR_DMA     0.0     -43.3     2.3     0
2012/01/03 22:26:49 PST     1         0     0     0     0     0.0     0.0     0.0     0.0     0     0     0.00     0.00         0     0     0.0     0.0     0.0     0     0         Unknown     Alcatel     27/20     ERR_DMA     0.0     -43.3     2.3     0
2012/01/03 22:34:27 PST     1         6016     8128     8128     8128     16.0     17.0     36.6     14.2     0     0     0.00     0.25         768     1148     19.0     18.5     11.9     0     0         G.DMT Annex A     Alcatel     229/103     ERR_DMA     -3.8     -51.5     29.9     0
2012/01/03 22:35:07 PST     1         6016     8128     8128     8128     16.0     16.0     36.6     14.7     0     0     0.00     0.25         768     1144     19.0     18.5     11.9     0     0         G.DMT Annex A     Alcatel     229/103     ERR_DMA     -3.7     -51.3     29.9     0
2012/01/03 22:38:21 PST     1         6016     8128     8128     8128     16.0     17.0     36.6     14.3     1     0     0.00     0.25         768     1144     18.0     18.5     11.9     0     0         G.DMT Annex A     Alcatel     229/103     ERR_DMA     -3.7     -51.6     29.9     0
2012/01/04 10:20:19 PST     1         6016     8128     8128     8128     16.0     16.0     36.6     14.8     20     0     0.00     0.25         768     1144     19.0     18.5     11.9     0     0         G.DMT Annex A     Alcatel     229/103     N/A     -3.7     -51.8     29.9     0

[cb6614]

Hey Carl, welcome to the forum. Great job reading the other posts and listing your diagnostic info with your question, I'll never understand why more people don't take the time to do that. Moving on to your concern, the modem reports that the DSL signal appears to be fine coming to your house. No major interference, unfiltered phones, or anything like that so there's a plus for you. In this case I'd want to look at a couple of things. First, what speed package do you subscribe to? 6Meg DSL? If so, then your modem's syncing a bit low @ just over 6000Kbps so I'd check the length of your data cable. If its less than 10ft, then I'd move the modem to another jack to see if you can get the modem to sync somewhere near 8128Kbps downstream for a 6Meg connection. If that doesn't do it, disconnect all phones in the house and try again. If that doesn't do it, I'd call the help desk and ask for a line qualification to make sure you're not too far in the loop for 6Meg service. If all that checks out, you can get a Pace 4111N which is replacing the 2Wire from this site (http://att.com/equipment) and that should resolve the issue. Good luck and let us know how it goes.

[carlclaunch]

The Pace model shows up on the page but no data is displayed about it. Further, when I go to the onliine store it does not list the Pace as a choice. Has this been dropped?

[rvpdsl]

carlclaunch, Are you running in 802.11g mode? If yes then, have you tried the following? If not then try them, separately:

1. On the "Home Network > Configure The Wireless Network" screen, switch to Wireless Mode = 802.11b, Maximum Connection Rate = 11Mbps. If this works then you can stick with 802.11g with one of several workarounds.

2. Change the Wireless Channel.

#1 works for me; I don't use a workaround yet so I'm running in 802.11b mode at the moment.

[carlclaunch]

I switched the wireless to 802.11b, didn't even scale down the max speed, and the red light disconnects all disappeared. Amazing that a clearly shoddy device, the 2Wire, would be promoted by AT&T as it made me doubt the quality of their DSL service for the last several years and undoubtedly has lost them business with many other customers. Since Pace just bought 2Wire and likely the new 4111 gateway is made by them, not sure why I would expect it to be better.

It is not the failure that bothers me, but their lack of honesty about it, their continued marketing of the 2wire as a 802.11g capable device when it is not engineered to keep up, the lack of any warnings about this from 2wire or to AT&T, and the unwillingness to provide updated firmware that would flag the problems or put in a clear log entry (DMA errors mean overrun, thus the log entry could say that the device is not able to keep up with total wifi load and the user should configure to b mode only).

While I wait to see if the Pace 4111 is actually a useful fix for this, I will be looking into the max data rate issue. I put in a DSL splitter right by the NID at the outside of the house and gateway is inside but very close to the exterior wall. I will look at the wiring lengths to see if there is any reason the modem is staying at 6MB, but it could have been set by AT&T based on earlier calls about the same service problems.

[carlclaunch]

cb6614 - when you say the data cable less than 10 feet, are you talking about the run from DSL splitter to the 2Wire box? I have a splitter at the NID and separate line into the gateway, but the wire run might be longer than 10 foot simply for convenience in routing and dressing the line. I could easily redo that if the speed might improve as a result.

[carlclaunch]

rvpdsl - I think your post mentioned that if the drop to 802.11b mode worked, there were ways to set up 802.11g support (with workarounds) that might work okay. Could you point me at the posts that cover those workarounds? Thanks.

[carlclaunch]

The pace 4111N is now showing up on the ATT shopping site and information about the product is there. Might have been a glitch or perhaps it has just rolled out for the west coast.

[rvpdsl]

Take a look at desmolift's comments on the topic before you buy it.

[rvpdsl]

carlclaunch, I don't have links to those posts mentioning the workarounds. You can go thro' this thread and see if you find something that works for you, be prepared to sift thro' a lot of noise in some of those posts with a possible workaround mentioned somewhere in between. Also, desmolift has some interesting posts on the topic, if you can get to them quickly.

Here's what I think would work (none of them have been tested):

1. Plug in another modem between the 2Wire and the telephone jack on the wall and take the 2Wire off of broadband, just use it for LAN. Taking it off of BB will need to be done on the MDC console.

2. Replace the 2Wire with something not 2Wire. Pace 4111n is a 2Wire product; maybe they've fixed the problem in it.

I am going to be trying workaround #1 with an older modem that I already have or get a new one from my new ISP ;-)

[sr190sd]

Or you can think outside the box and drop at&t altogether for internet so you can have your own gigabit router. It is just amazing that at&t would come out with a new RG that doesn't support gig ethernet in 2012.. What gets me is that I like U-Verse TV but don't have U-Verse internet and STILL have to have this bulky RG in my house. The 2-Wire unit from 2008 just failed and was replaced for free by at&t with the Pace unit so why are you guys plunking down $100 for it. A Motorola SB6120 is a far better modem and add in a decent Buffalo gig router with wireless n (around $150 total if you look for them on sale through major etailers) for a far faster internet experience from your cable provider.

[ekkenny]

After reading this forum I am now sure that I am not just going insane,.

After changing to a dry loop back in June of 2011 I started getting intermittent loss of internet  -- not DSL. I tried all I could so I called ATT and now the fun starts. After 2 calls a tech was dispatched and he said that my Motorola 2210 was having a problem and he had a new 2wire 2701 in the truck. I was in a gullible mood, so I said Ok.

Bad  move! It got even worse. I will lose internet sporadically, even in the model of the night with no devices active other than my Vonage device.

I know the pain involved trying to get DSL support on the line. Some of them are helpful, but most are arrogant and assume I am stupid. Thursday I called in and actually was escalated quickly. I got a call from Ariel in California the issue occurred when I was working with him. He reset a piece of equipment IN THE OFFICE and all came back to normal. I suspect that AT&T is using some type of terminal server, but either way  a dispatch was arranged.

I was called back by Paulette in Missouri. She said there was an issue with the 2wire and ipv6. OK  I'll bite. If the dhcp is too dumb to figure out I am not ipv6, I can see there would be a issue. She was pretty good at talking down, but I am desperate and need a fix. Sync attack was switched from on to off and mode was changed from 802.11b/g to b only.

Ok I'll try this again --- I am desperate. If it works I can ask AT&T for a refund for degrading my network from 54m to 11M.

Needless to say, next day we have another series of lost internet connections, DSL is still on. Start the support process all over again, but I called the 1275 number direct and talked to Chris. He did a  test to a piece of equipment  in the office or in a server somewhere and got errors. My stuff is OK. A dispatch was again arranged.

This morning I got another call from Missouri, and this joker is telling me that windows and OS X are the problem and ---- guess what ---- if I turn off sync attack n the 2wire and degrade my network to 802.11b it will fix the problem.

RIGHT !  I told him that was done and make sure not to cancel my dispatch,. So here I am waiting.

I have talked to people at AT&T who are arrogant and condescending, and I have also talked to people that genuinely want to help me. But I have yet been able to talk to someone that really knows how DSL , routing, and computers really work.

I had no issues when I was using an old Speedstream and DSL over dialtone. Everything started when I went dry loop.

Maybe today I can get the tech to look at the stuff on the AT&T side.

I am not optimistic.

ekkenny

[cb6614]

Hey Kenny, welcome to the forum. So you're using a 2Wire 2701HG-B and you're having intermittent loss of sync or is it that the DSL light stays steady green and your Internet light just goes out? Have you tried checking the diagnostic page of the 2Wire's MDC? If not, click this link from a machine that's connected to the 2Wire (http://192.168.1.254/mdc) then under Troubleshooting on the left side of the page, click "DSL Troubleshooting" (or something like that,it may be "DSL Statistics" or something but it will have the "DSL" in the title). Take a screenshot of that page and post it here. I'll take a look at your line stats and we'll try to figure out what's causing the intermittence together. I'm stepping out for a bit so I'll check back this evening to see if you've replied. Don't give up, I'm sure between here in the forums, the DSL helpdesk, and the tech that's being dispatched we'll find something that we can resolve. Have a good one!

[ekkenny]

cb6614

Thanks for the reply.

DSL stays green  --- internet goes  blank. Same issue on a Motorola 2210 I used to use.

I had to power reset 10 minutes ago, I'll try to get the diags and post them.

Either way there is an issue with either poor design on the 2wire 2701 or AT&T is hiding something.

BTW. I ran a sniffer trace and the 2wire is sending gratuitous arps every few seconds and is trying to query every device on my network. Again --- this is something that is quite unnecessary.

I know IP, I know advanced routing, and I know the internals of windows, Mac, and UNIX.  Whatever is going on here is either in the 2wire or it is on the network.

Again, I'll try anything to get this working.

Thanks

ekenny

[ekkenny]

perhaps this is what you want?

Management and Diagnostic Console

System Summary Broadband Link • Summary • Statistics • Detailed Statistics • Configure Local Network • Status • Statistics • Device List • Wireless • Configure Firewall • Settings • Detailed Information • Advanced Settings Troubleshooting • DSL Diagnostics • Event Log • Network Tests • Upgrade History • Resets Advanced • Syslog Settings • Provisioning Info • Configure Time Services • Configure Services • Static Routes • DNS Resolve • Traffic Shaping • Link Manager • Detailed Log

Troubleshooting – DSL Diagnostics General Information DSL Line (Wire Pair): Line 1 (inner pair) Downstream Rate Cap: 6016 kbps Downstream Atten. at 300kHz: 18.9 dB Uncancelled Echo: -3.9 dB Ok VCXO Frequency Offset: -34.8 ppm Ok Final Rx Gain: 18.8 dB Ok Impulse Noise Comp. Tones: 0 Ok Excessive Impulse Noise: 0 Ok Impulse noise protection: 2.21 Delay of latency path: 16.00 ms   Training History   Downstream   Upstream Time Line   Rate Max1 Max2 Max3 Mgn1 Mgn2 Attn Pwr CRCs FECs INP DLY   Rate Max Mgn Attn Pwr CRCs FECs   Mode Vendor State Exit Code Echo VCXO Rx Gain INC Tones 2012/01/14 14:03:43 CST 1   6016 8128 8128 8128 16.0 14.0 23.0 13.4 70 211 2.21 16.00   768 1116 20.0 11.0 11.9 25 44   G.DMT Annex A Alcatel 229/103 N/A -3.9 -34.8 18.8 0   Notes: Time Time of last update Max1 Max. rate at start of connection Max2 Current or final estimated max. rate Max3 Current or final estimated max. rate without INC Mgn1 Noise margin at start of connection Mgn2 Current or final noise margin DLY Delay of latency path   Bitloading | | | | ||||||||| | || ||||||||||||||||||||||||||||||||||| |||||||||||||||| | ||||||||||||||||| || || || ||| |||| |||||||||||||||||||||||||||||||||||||||||||| ||||||||||||||||||||||||||||| |||||||||||||||||||||| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| ||||||||||||||||||||||||||||||||||||| ||| ||||||||||||| ||||||||||||||||||||||| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| |||||||||||||||||||||||||||||||||||||| ||| ||| |||||| ||||||||||||| ||| ||||||||||||||||||||||| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| ||||||||||||||||||||||||||||||||||||||||||| ||| ||||| |||||| |||||||||||||||||||||| ||||| ||| | ||||||||||||||||||||||| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| ||||||||||||||||||||||||||||||||||||||||||| ||| ||| |||||| ||||||| |||||||||||||||||||||| |||||| |||||||| ||||||||||||||||||||||| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| ||||||||||||||||||||||||||||||||||||||||||||| |||||| ||||||||| |||| |||||| |||||||| |||||||||||||||||||||||| |||||| ||||||||||| ||||||||||||||||||||||| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| |||||||||||||||||||||||||||||||||||||||||||||| ||||||| ||||||||| ||||| ||||||||||||||| |||||||||||||||||||||||| ||||||||||||||||||||| ||||||||||||||||||||||| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| |||||||||||||||||||||||||||||||||||||||||||||| |||||||| ||||||||| | ||||||||||||||||||||| |||||||||||||||||||||||| |||||||||||||||||||||| ||||||||||||||||||||||| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| |||||||||| |||||||||||| |||||||||||||||||||||||||||||||||||||||||||||||||| ||||||||||||||||||||||| ||||||||||||||||||||||| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| |||||||||| |||||||||||| |||||||||||||||||||||||||||||||||||||||||||||||||| ||||||||||||||||||||||| 0000000999AAAAABBBBBBBBBAAA998000000009AA9AA9AA9AAA9AAAA9999999AAABAABBABBBBBBBBBCBBBBBBCBBBBCBBBBBBBBBCBBB2BBBBBBBBBBBBBBBBAAAAABAAAAAAA99999999877777554200234555555202556665555220023245777367888747888776522578899987999999999999975078887647776766655544432 | | | | | | | | | | | | | | | | | 0 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 256

[ekkenny]

Well,

Here it is. 2045 and no AT&T. I did get a call on my cell, but the number was blocked and when I answered the call dropped. No callback. No message. No nothing.

I am now convinced AT&T just doesn't care.

I guess I'll call Monday and rearrange a dispatch.

Does anyone have an email address of a VP in AT&T somewhere? Maybe if I cause someone up high a little grief that the grease will run downhill.

I also think that it might be time to go somewhere else. I think that the Marge Ferguson Refrigerator, Airline, and Telephone/DSL Company would be more competent and want my business more than AT&T.

This really sucks.

[rvpdsl]

---

ekkenny wrote:

After reading this forum I am now sure that I am not just going insane,.

...

 

This morning I got another call from Missouri, and this joker is telling me that windows and OS X are the problem and ---- guess what ---- if I turn off sync attack n the 2wire and degrade my network to 802.11b it will fix the problem.

---

Switching to 802.11b only fixes the ERR_DMA error (shows up in the DSL Diagnostics) that causes the DSL sync to drop and resync within about 15 seconds every so often (several 10s of times a day or more) as far as I know. It fixed my ERR_DMA problem instantly, without having to modify the firewall at all.

Your problem seems to be getting an IP & DNS and not DSL disconnect/resync.

The tech support from MO was shooting in the dark! When I was talking to tech support, before finding this forum and these threads, I was told to buy a new 2701 and the tech wasn't willing to have the dispatched tech person debug only the line and leave the modem/router alone. I had suspected that they would tell me what they told you about your Motorola 2210 and get me to buy a new 2701 since mine was out of warranty.

Then there was another tech support person on live chat that wanted me to fiddle with the wireless power settings. I questioned debugging the power/LAN settings when the problem was with the DSL sync. Instead of explaining why she thought it could be an issue with the wireless power setting she agreed that the wireless power setting was not related to the DSL sync and asked me to call tech support here for more technical help. What the !@#$!

This is what has become of this once fantastic company.

The 2Wire2701HG-B is a pretty good device for its time with some bugs that could have been fixed with firmware upgrades. The MAC filter doesn't work too.