02-24-2013 08:49 PM
@ylime1984 - This morning the problem is back with a vengeance. The kids were trying to watch National Geographic and it was choppy and kept stopping. We needed to wait for a minute or two and then reload the page and re-position the video playback. Finally I just disconnected the router, plugged the modem directly into the computer and we watched 4 National Geographic episodes without a single incident.
If you have tried the MTU also and still having the same problem then it might really be a hardware issue. MTU for DSL is 1472 or 1400 just in case you have not tried that.
02-25-2013 06:46 AM
Because I've got an Linksys E4200 v1 I was able to install Tomato (it doesn't work with v2).
I found a helpful discussion here: http://tomatousb.org/forum/t-441228
And found the firmware here: http://www.4shared.com/file/8-9fjw2o/tomato-K26USB-12804971MIPSR2-T.html
I downloaded this file:
and installed it with the default Cisco firmware under Administrive.
I then did a 30-30-30 reboot, changed the admin password, enabled DHCP, configured PPPoE and everything - including the 5GHz - is working wonderfully.
The DHCP is working, which it wasn't with the built-in firmware.
02-25-2013 07:03 AM
02-28-2013 03:15 AM
hope this works for you... for me it didn't. I spent multiple sessions with Cisco support, also spent a couple of days troubleshooting and monitoring.
In short, tried everything I could possibly try.
Except PPPoE though, these are solid routers with good perfomance. It is indeed strange why Cisco has not corrected this flaw which exists across multiple models.
02-28-2013 05:16 AM
02-28-2013 10:18 AM
I had actually tried lowering the MTU without success.
This may be a firmware or hardware issue for E4200 v1 since other users are saying that PPPoE in v2 is working fine as well as using tomato firmware, the connection is fine. To isolate further, if the router is still within warranty, have it replaced. Configure the replacement unit the same way and observe if the same problem is experienced. If yes then we can say this is a firmware issue.
02-28-2013 10:32 AM