dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
15660
share rss forum feed

Scotsman

join:2013-01-19
Austin, TX

[TWC] Time warner cable and Motorola Surfboard 6141

Click for full size
I recently upgraded my 20Mbps connection to a 30Mbps service, as well as purchasing a Motorola surfboard 6141. It's connected to an airport express (default settings) and one computer via wifi.

Since then I have had all sorts of intermittent connection problems. It seems to work fine until I am doing something intensive, and then gets choked up.

Here's a recent ping test and traceroute:

PING 8.8.8.8 (8.8.8.8): 56 data bytes

Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
64 bytes from 8.8.8.8: icmp_seq=3 ttl=46 time=1853.703 ms
64 bytes from 8.8.8.8: icmp_seq=0 ttl=46 time=4857.091 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=46 time=2854.908 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=46 time=3856.024 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=46 time=855.117 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=46 time=951.458 ms


traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 72 byte packets

1 192.168.0.1 (192.168.0.1) 1.087 ms 1.091 ms 1.385 ms
2 * * *
3 * * tge7-2.austtxk-er01.texas.rr.com (66.68.1.245) 3102.914 ms
4 tge0-11-0-8.austtxa-cr01.texas.rr.com (24.27.13.82) 18.002 ms 25.482 ms 22.500 ms
5 agg22.dllatxl3-cr01.texas.rr.com (24.175.41.46) 19.696 ms 23.425 ms 15.812 ms
6 ae-4-0.cr0.dfw10.tbone.rr.com (66.109.6.88) 20.850 ms 23.006 ms 24.075 ms
7 107.14.17.234 (107.14.17.234) 16.404 ms 16.377 ms 15.339 ms
8 74.125.48.65 (74.125.48.65) 62.360 ms 90.147 ms 63.274 ms
9 72.14.233.67 (72.14.233.67) 15.814 ms 19.638 ms 16.354 ms
10 72.14.237.217 (72.14.237.217) 17.516 ms 17.329 ms 18.501 ms
11 216.239.47.121 (216.239.47.121) 24.035 ms 34.666 ms 24.192 ms
12 216.239.46.61 (216.239.46.61) 23.184 ms 32.404 ms 30.130 ms
13 * * *
14 * google-public-dns-a.google.com (8.8.8.8) 24.035 ms 26.205 ms


Resetting seems to fix things temporarily.

Signal strengths are attached. Is this just a bad modem? I had the same problem with a Surfboard 6121 that I tested.


jimk
Premium
join:2006-04-15
Raleigh, NC

Please post your event log from the modem (blank out any MAC addresses) and the firmware version.

Signals look good so far. However, there are some upstream stats that you can't see on your modem.

What modem did you have previously?


Scotsman

join:2013-01-19
Austin, TX

Thanks. I had some ancient scientific atlanta WebSTAR EPC2203

Firmware info:

Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.3-SCM03-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 7.0
Serial Number: 348781213900943606010001
Firmware Build Time: Aug 18 2011 10:27:53

Event log:

Jan 18 2013 22:01:42 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxx;CMTS-MAC=00:15:f9:2a:29:60;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=xxxxx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 18 2013 21:42:14 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxx;CMTS-MAC=00:15:f9:2a:29:60;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=xxxxx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 18 2013 21:40:46 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxx;CMTS-MAC=00:15:f9:2a:29:60;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=xxxxx;CMTS-MAC=00:15:f9:2a:29:60;CM-QOS=1.1;CM-VER=3.0;
Jan 18 2013 21:34:58 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:xxxxx;CMTS-MAC=00:15:f9:2a:29:60;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=xxxxx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 18 2013 21:33:33 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxx;CMTS-MAC=xxxxx;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=xxxxx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 18 2013 20:46:45 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxx;CMTS-MAC=xxxxx;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=xxxxx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 18 2013 20:28:41 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxx;CMTS-MAC=xxxxx;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=xxxxx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 18 2013 20:17:08 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=20:e5:64:5b:b8:58;CMTS-MAC=00:15:f9:2a:29:60;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=xxxxx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 18 2013 18:46:05 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxx;CMTS-MAC=xxxxx;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=xxxxx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Jan 18 2013 18:22:28 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxx;CMTS-MAC=xxxxx;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:14 6-Notice Cable Modem Reboot due to power reset ;CM-MAC=xxxxx;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;



jimk
Premium
join:2006-04-15
Raleigh, NC
Reviews:
·Time Warner Cable
·voip.ms

How often are you resetting it? I'm assuming that every single "Cable Modem Reboot due to power reset" event is you power cycling the modem, but if that is not the case and it is doing this on its own, you might have a power supply or modem issue.

When you start to have problems, does it eventually start working normally again without being power cycled? Or is a power cycle the only way to fix it?

If possible, it may be necessary to leave the modem on and grab the signal stats & logs during and immediately after the problem happens without rebooting the modem.


Scotsman

join:2013-01-19
Austin, TX

I have been regularly resetting it. Seems to be the quickest way to clear the problem.

And yes, it does eventually start working again after sometime - the pings come back to a more usual 25ms or so.

I'll try and grab those logs at the point of failure as you suggest. Watch this space


Scotsman

join:2013-01-19
Austin, TX

Click for full size
OK in the middle of a slowdown here's the signal levels and a traceroute & ping test

raceroute has started…

traceroute to 8.8.8.8 (8.8.8.8), 64 hops max, 72 byte packets

1 10.0.1.1 (10.0.1.1) 1.319 ms 0.725 ms 1.173 ms
2 * * *
3 tge7-2.austtxk-er01.texas.rr.com (66.68.1.245) 1477.595 ms 19.937 ms 8.302 ms
4 tge0-11-0-9.austtxa-cr01.texas.rr.com (24.175.41.74) 21.381 ms 21.348 ms 31.855 ms
5 agg22.dllatxl3-cr01.texas.rr.com (24.175.41.46) 23.834 ms 23.307 ms 15.972 ms
6 107.14.17.136 (107.14.17.136) 22.158 ms 26.579 ms 23.357 ms
7 107.14.17.232 (107.14.17.232) 15.277 ms 17.415 ms 16.907 ms
8 74.125.48.65 (74.125.48.65) 78.836 ms 75.936 ms *
9 * 72.14.233.67 (72.14.233.67) 371.583 ms 23.716 ms
10 72.14.237.217 (72.14.237.217) 29.557 ms 87.131 ms
72.14.237.221 (72.14.237.221) 37.461 ms
11 209.85.243.178 (209.85.243.178) 52.202 ms
216.239.47.121 (216.239.47.121) 24.709 ms
209.85.243.178 (209.85.243.178) 26.850 ms
12 216.239.46.59 (216.239.46.59) 24.728 ms
216.239.46.61 (216.239.46.61) 69.774 ms
216.239.46.59 (216.239.46.59) 911.212 ms
13 * * *
14 google-public-dns-a.google.com (8.8.8.8) 269.900 ms 152.609 ms 140.605 ms

PING 8.8.8.8 (8.8.8.8): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
64 bytes from 8.8.8.8: icmp_seq=0 ttl=45 time=5592.902 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=45 time=4710.106 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=45 time=3723.132 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=45 time=2834.900 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=45 time=1904.882 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=45 time=909.429 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=45 time=26.834 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=45 time=29.433 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=45 time=3590.248 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=45 time=2606.492 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=45 time=1612.888 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=45 time=614.727 ms
Request timeout for icmp_seq 17
Request timeout for icmp_seq 18
Request timeout for icmp_seq 19
Request timeout for icmp_seq 20
64 bytes from 8.8.8.8: icmp_seq=12 ttl=45 time=9670.297 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=45 time=8670.335 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=45 time=7670.270 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=45 time=6670.812 ms

Seems to get really bad getting beyond my LAN.

I read that the Motorola 6141 was the best, but perhaps I should be try a different one? This never happened with my old modem and slower speed. Called TWC a few times but they have no clue.


jimk
Premium
join:2006-04-15
Raleigh, NC
Reviews:
·Time Warner Cable
·voip.ms

Your previous modem was not DOCSIS 3, so there could be an issue on TWC's side that only impacts DOCSIS 3 devices, but I kind of doubt it in this situation. Are you seeing any T3 or T4 timeouts anywhere in the modem logs?

If everything worked before and the modem is the only thing that changed, I would be inclined to try a different model of modem to rule out any strange firmware bugs or compatibility issues. There have been multiple firmware revisions since the one installed on your modem. Currently, TWC is currently refusing to even talk about pushing firmware updates to customer owned modems on the supported device list. You can't install it yourself either since Motorola won't provide it to customers and there is no interface to flash the update from the customer side.

The Zoom 5341J (note the J - the DOCSIS 3 8x4 model, not the old 5341 which is only 4x4 and not on the approved device list) is a good modem. A small number of people seem to have problems with it dropping the connection for a few seconds every 2.5 days, but that is a lot better than what you are seeing. It always comes back without a power cycle being required.

I assume you have already eliminated your router/firewall as the cause for the issue. I highly doubt that has anything to do with it but it makes sense to check just in case.


gkloepfer
Premium
join:2012-07-21
Austin, TX
reply to Scotsman

I've got a 6141 in Austin as well, and it's working fine (my signal levels are similar to your's). What we really need would be the cable modem log that you see while this is happening, but I suspect there won't be much to speak of in that either.

It looks to me like you have a problem with your router or the connection from the router to the cable modem. All the stats from your modem look good, as well as the logs you provided earlier. It almost looks like you may have some rogue traffic on your line (a LOT of traffic) that is slowing things down. Are you sure nobody else from your household is using the connection at the same time (doing something that's high-traffic), and if not, are you sure nobody has broken into your network somehow? That 1477ms ping time to the first hop on your traceroute when you were having trouble looks suspicious to me.

Also, if you are doing the ping or anything else over a wireless link, it could be interference in the neighborhood or from some appliance in the home, or a failing wireless router. In fact, if this is wireless, the problems you're experiencing (in the absence of any issues in the cable modem log) are almost definitely a wireless issue (router going bad or interference).

That's my two-cents, for what it's worth...


Scotsman

join:2013-01-19
Austin, TX

Thanks guys.

Tried 4 different routers, different cables, direct wire to the router, new SSID, password, and even a surfboard 6121. Same every time. Internal LAN works perfectly. Never seen any T3 or T4 timeouts.

gkloepfer - what firmware is on your 6141?

Only thing I haven't done yet is plugged straight into the modem - it's in the basement and a bit awkward... Might just have to go back to my Scientific Atlanta webstar and 20Mbps. That worked perfectly.

Beats me.


Scotsman

join:2013-01-19
Austin, TX

OK so I have made some progress. I have spent the day with my laptop plugged straight into the Surfboard 6141. What seems to happen is that periodically there is some kind slowdown in the connection, and then it slowly recovers. I ran a ping test continuously for a few hours, and see patterns like this every so often:

64 bytes from 8.8.8.8: icmp_seq=8832 ttl=47 time=21.176 ms
64 bytes from 8.8.8.8: icmp_seq=8833 ttl=47 time=21.478 ms
64 bytes from 8.8.8.8: icmp_seq=8834 ttl=47 time=22.379 ms
64 bytes from 8.8.8.8: icmp_seq=8835 ttl=47 time=22.287 ms
64 bytes from 8.8.8.8: icmp_seq=8836 ttl=47 time=30.688 ms
64 bytes from 8.8.8.8: icmp_seq=8837 ttl=47 time=22.009 ms
64 bytes from 8.8.8.8: icmp_seq=8844 ttl=47 time=2708.377 ms
64 bytes from 8.8.8.8: icmp_seq=8838 ttl=47 time=8714.267 ms
64 bytes from 8.8.8.8: icmp_seq=8846 ttl=47 time=707.489 ms
64 bytes from 8.8.8.8: icmp_seq=8843 ttl=47 time=3709.937 ms
64 bytes from 8.8.8.8: icmp_seq=8845 ttl=47 time=1708.299 ms
64 bytes from 8.8.8.8: icmp_seq=8840 ttl=47 time=6713.109 ms
64 bytes from 8.8.8.8: icmp_seq=8841 ttl=47 time=5712.033 ms
64 bytes from 8.8.8.8: icmp_seq=8839 ttl=47 time=7714.351 ms
64 bytes from 8.8.8.8: icmp_seq=8842 ttl=47 time=4711.284 ms
64 bytes from 8.8.8.8: icmp_seq=8847 ttl=47 time=22.561 ms
64 bytes from 8.8.8.8: icmp_seq=8848 ttl=47 time=22.384 ms
64 bytes from 8.8.8.8: icmp_seq=8849 ttl=47 time=22.307 ms
64 bytes from 8.8.8.8: icmp_seq=8850 ttl=47 time=25.983 ms
64 bytes from 8.8.8.8: icmp_seq=8851 ttl=47 time=22.643 ms
64 bytes from 8.8.8.8: icmp_seq=8852 ttl=47 time=21.477 ms
This situation is made worse when combined with a router (I see it reporting double NAT every time the connection slows).

Somebody from TWC coming out next Friday to have a look. I hope they can shed light on my problem.

cramer
Premium
join:2007-04-10
Raleigh, NC
kudos:9

1 recommendation

Ping your gateway, not something way out on the internet. If it's a problem with the modem or line, that's where you need to be looking. Traffic outside TWC's network isn't going to be fixable by them. (inside their network... well, you have to get them to agree it's broken first.)


gkloepfer
Premium
join:2012-07-21
Austin, TX
reply to Scotsman

I responded privately to Scotsman, but my 6141 is running version SB_KOMODO-1.0.6.3-SCM03-NOSH.

The only gripe I have about this firmware is that the signal levels (and especially the power level) are only displayed as integer (no tenths), and that the power levels display as "0" when the signal levels are <0dBmV. Given that this is one of the compliant modems TW allowed us to buy, I'm hoping that they update the firmware someday with the status page fixed, but I won't hold my breath. I'm OK with this as long as it works properly and they can somehow see the levels accurately if something goes wrong.

I agree with cramer that the place to ping is (in this case) 66.68.1.245, which is the first hop after the cable modem from the traceroutes above.

If, without wireless in play and just connected to the cable modem with a laptop, you're still getting ping times that go up in the 3 second (3000ms) times to the first hop, then that is definitely something TW needs to know about. When you're connected with only the laptop, you may also want to capture packets (using tcpdump or wireshark or whatever your favorite capture program is). Filter out any arp requests, as those are going to be numerous and they can be ignored. There shouldn't be any other significant traffic except for your ping. If there is a large burst of traffic when the slowdown happens, that may explain why the slowdown happens. It won't really give a full explanation, but if you have that information, it could help someone from TW help you out.

The only other TW infrastructure-related explanation I can think would cause this is if your neighborhood node was horribly overloaded. That is also something that TW will want to check out. I think we've all had our negative experiences with TW, but in reality I think TW wants everyone to get good service and will try to fix problems like this once they actually see it happen. Getting them to see it, though, definitely feels futile sometimes...


jeblis

join:2012-10-08
Austin, TX
reply to Scotsman

I'm seeing these same issues with my sb6141 in austin. I've had 4 techs out. Line fixes, power level adjusts, new cable modem, still not working. If they can't debug their own equipment it may be time to move on.


orion6192

join:2010-06-14
Wayland, NY

I've got similar issues here in upstate Western NY.

Read my thread: »[TWC] Wayland, NY - Issues switching to a SB6141 from an

What do the level 3 and 4 errors represent? I get a lot of them...



kw
Premium
join:2004-06-12
New Albany, OH
kudos:6
reply to Scotsman

I picked up a SB6141 last week and it came with a different (newer) version of the firmware and I've had no issues with it.

Firmware Name: SB_KOMODO-1.0.6.8-SCM01-NOSH


orion6192

join:2010-06-14
Wayland, NY

1 edit

This is my info from my modem:

Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.3-SCM03-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.
Hardware Version: 7.0
Serial Number: 3487
Firmware Build Time: Aug 18 2011 10:27:53



kilrathi
Premium
join:2005-04-22
Rockaway Park, NY
reply to Scotsman

t3 and t4 errors are not caused by modem but usually noise on the upstream.

I mean if u have option of leasing modem from tw try it and see if problems are gone just to entertain low very low chance of a faulty modem.



kilrathi
Premium
join:2005-04-22
Rockaway Park, NY
reply to kw

so u have 6141 thats runnning newer firmware than others 6141 on tw network? hmm wtf does tw even care what firmware customer 6141 run on?



Ping

@rr.com
reply to kw

Id like to see the speedtest results from »speedtest.ohiordc.rr.com/



kw
Premium
join:2004-06-12
New Albany, OH
kudos:6

said by Ping :

Id like to see the speedtest results from »speedtest.ohiordc.rr.com/

I have the 30/5 package. I clocked in right where I should:

30.77/4.90

taznumber1

join:2003-12-26
reply to kilrathi

I have a 6141 and I am running the same of SB_KOMODO-1.0.6.3-SCM03-NOSH which I believe is TW default firmware for 6141 customer owned equipment.

I also have the same setup using a 6141 with airport extreme.



Ping

@rr.com
reply to kw

Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.8-SCM01-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3
Hardware Version: 7.0
Serial Number: 374781234224574309020022
Firmware Build Time: Aug 30 2012 15:35:46

I've been talking to tech support for almost a week, I have the extreme package, but I am only getting 2up and 30 down. Three different modems and TWC can't get my upstream speeds up. I'm in northeast Ohio.

Any help folks?



motorola870

join:2008-12-07
Arlington, TX
kudos:3

said by Ping :

Model Name: SB6141
Vendor Name: Motorola
Firmware Name: SB_KOMODO-1.0.6.8-SCM01-NOSH
Boot Version: PSPU-Boot(25CLK) 1.0.12.18m3
Hardware Version: 7.0
Serial Number: 374781234224574309020022
Firmware Build Time: Aug 30 2012 15:35:46

I've been talking to tech support for almost a week, I have the extreme package, but I am only getting 2up and 30 down. Three different modems and TWC can't get my upstream speeds up. I'm in northeast Ohio.

Any help folks?

the only thing I can think of is upstream utilization issues with an overloaded channel or signal issue can you post your signal stats at 192.168.100.1?


Ping

@rr.com

Click for full size
to motorola870


motorola870

join:2008-12-07
Arlington, TX
kudos:3

said by Ping :

to motorola870

hm your upstream is 38dBmv for power level which is a little low but not too far from 40dBmv which is a lower end of the recommended range for upstream power levels. I don't think your having a noise issue which would make your upstream channel change to only QAM16.

I think your problem is an over utilized upstream channel (overcrowded) I think channel bonding would help possibly if your node is not maxing out on all of the channels. My area is bonding 4 upstream channels right now. I would assume that upstream bonding will come to your area sometime this year or next.


Ping

@rr.com

This has gone on for a week. I am paying for 30/5 and getting 30/2. The techs Arris Gold modem did 50/5, but my sb6141 and two other DOCSIS 3 modems will not get me 30/5 - I'm not a techie, and tier 3 tells me I am "the only one with this problem", at last contact ( yesterday ) I was told this was being bumped to engineering. All I know is I'm not getting what I'm paying for - and I own the modem and do not lease it.



kw
Premium
join:2004-06-12
New Albany, OH
kudos:6

Click for full size
My levels look just about the same.


Ping

@rr.com

PROBLEM RESOLVED

SOLUTION: Restored Linksys E2000 to factory defaults.

My thanks and appreciation to the patients techs at Time Warner Cable.


dowop

join:2012-10-30
Cortland, OH

I just had my 6141 installed. It says under configuration IPv4 Only.

Was it configured wrong?



kw
Premium
join:2004-06-12
New Albany, OH
kudos:6

said by dowop:

I just had my 6141 installed. It says under configuration IPv4 Only.

Was it configured wrong?

No