What's new

ASUS RT-N66R and Motorola SB6141 Connection Dropouts

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

cinnamonbits

New Around Here
Hello,

Yesterday I had purchased a Motorola SURFboard SB6141 modem and an ASUS RT-N66R router to replace the combination modem/router supplied to me by Time Warner. I plugged everything in, gave Time Warner a call, and was up and running in short order. Soon after having everything set up, I noticed a short dropout of internet service about once every half hour to hour. After some searching, I stumbled upon Merlin's wonderful firmware and updated to the most current release (3.0.0.4.374.32) which seemed to alleviate the problem. However, so far three times today I've noticed very short dropouts, but they are occurring much less frequently. This brings me to my current situation.

I had just experienced a dropout and I had a Terminal window with an active ping to google going, as well as a window open to the ASUS Traffic Monitor. Attached is a screenshot of the Traffic Monitor during the dropout.

The following is a clip from the ping I had going, showing roughly how many seconds the connection went out for:

Code:
64 bytes from 74.125.239.116: icmp_seq=13343 ttl=50 time=24.212 ms
Request timeout for icmp_seq 13344
Request timeout for icmp_seq 13345
Request timeout for icmp_seq 13346
Request timeout for icmp_seq 13347
Request timeout for icmp_seq 13348
Request timeout for icmp_seq 13349
Request timeout for icmp_seq 13350
Request timeout for icmp_seq 13351
Request timeout for icmp_seq 13352
Request timeout for icmp_seq 13353
Request timeout for icmp_seq 13354
Request timeout for icmp_seq 13355
Request timeout for icmp_seq 13356
Request timeout for icmp_seq 13357
Request timeout for icmp_seq 13358
Request timeout for icmp_seq 13359
Request timeout for icmp_seq 13360
Request timeout for icmp_seq 13361
Request timeout for icmp_seq 13362
Request timeout for icmp_seq 13363
Request timeout for icmp_seq 13364
Request timeout for icmp_seq 13365
Request timeout for icmp_seq 13366
Request timeout for icmp_seq 13367
Request timeout for icmp_seq 13368
Request timeout for icmp_seq 13369
Request timeout for icmp_seq 13370
Request timeout for icmp_seq 13371
Request timeout for icmp_seq 13372
Request timeout for icmp_seq 13373
Request timeout for icmp_seq 13374
Request timeout for icmp_seq 13375
Request timeout for icmp_seq 13376
Request timeout for icmp_seq 13377
64 bytes from 74.125.239.116: icmp_seq=13378 ttl=50 time=19.927 ms

As of right now, the System Log currently reads an uptime of 16 hours and 23 minutes, and there don't seem to be any relevant entries other than a DHCPREQUEST that occurred during the same minute as the dropout. However, during the previous dropouts there were no entries at all during the time.

During the dropout, I took a look at the lights on the modem and they were exactly as they are now, with the connection light blinking at a steady rate just as it's doing now. Also, the lights on the router did not seem to change either, but I can't be perfectly sure.

EDIT: I'd like to add that I'm using a Mac Pro connected to the router via a Cat 5e cable I believe. It actually doesn't have any markings on it, so I'm not positive. However, I'm not sure this is an issue with the cable because I noticed an earlier dropout on my Xbox as well, which is also connected directly to the router via a cable.

Are there any common causes for this kind of issue? If this isn't an adequate amount of information, are there other tools I can use to gather more helpful information during a dropout like this?

I'd just like to say thank you in advance to all of you who invest your time into helping people like myself.
 

Attachments

  • Screen Shot 2013-09-01 at 3.45.06 PM.png
    Screen Shot 2013-09-01 at 3.45.06 PM.png
    41.6 KB · Views: 304
Last edited:
Check the router's System Log - if you see any "Ethernet link is down" messages at about the same time the connection drops, it usually means the problem is with either the Ethernet cable between the router and the modem (which must be Cat5e or Cat6), or the modem itself.

Also, try setting DHCP to "Normal" instead of "Aggressive" on the router WAN page.
 

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top