09-13-2014 04:31 PM
We recently upgraded to the DG1670a for the new speeds TWC is offering. New speeds are great; however, while I play DOTA 2 (or even web browsing), I noticed the connection drops once or twice per hour for a period of about 10 - 20 seconds. I constantly ping 192.168.100.1 and I notice that during these events, there will be 5 - 7 pings that time out.
I called TWC and described the issue. They checked power levels, and they said everything looks fine. I tried putting the device in bridge mode and running it through a router, but I couldn't seem to get that working properly...regardless, I expect the device should work as intended as a router and modem concurrently.
Solved! Go to Solution.
09-13-2014 04:55 PM
Sorry about your issues sir..
I would recommend you disable WPS Settings, change security type to WPA rather then WPA 2, use wireless channel 1, change becan interval from 100 to 50 / use a shorter coax cable / bypass splitter if any, or replace splitter if same issue still occures
09-13-2014 06:59 PM
Turnoff WPS,the WIFI guest account,IP flood detection and it's firewall.
But first copy and paste the modems signal and error log pages.
09-14-2014 05:15 AM
If the disconnects occur every hour, almost exactly to the minute, then I suspect a problem with DHCP lease renewal. When computers are connected to a modem or router that assigns an IP address, the IP address is assigned for a specific amount of time, determined by the modem or router. 1 hour is the default setting for this modem.
The computer attempts to reset the lease time half way through by sending a request to the modem or router, and should normally be transparent to the user, i.e. no disconnect. If the the router or modem doesn't see the request or rejects it, then disconnects may occur.
You can check this in your computers event logs (for Windows, Control Panel > Administrative Tools > Event Viewer > System) and look for DHCP events
If this is the issue and you are unable to resolve it between your computer and the modem, you can work around it by logging into the modem LAN settings page and change the lease time to 604800 (7 days). The problem will still be there, but you will only see it once a week.
09-14-2014 09:21 AM
pinging 192.168.100.1 is stupid, it is the modem and is basicly a ping attack! You should not be doing that constantly as it ties it up. It also can indicate the problem is in your computer All in ones are junk and are plagued with issues unless they're turned back into basic modems and you supply your own router.
I assume you've turned off WPS, the wifi guest account, IP flood detection and firewall in it as well as changed the dhcp address range off the illegal single last digit start to a range of 192.168.x.100 on up...
You may also need to run netstat to see what IP connections and ports your computer has as well as copy and paste the modems signal level pagges here. Marginal signals induce errors.
09-14-2014 07:30 PM
Before posting here, I did disable firewall, change starting IP address, etc (everything as recommended by MsRaye). I called TWC and they mentioned power levels were ok, but I included them below, too.
Before posting, I also suspected it is a DHCP issue. I checked the event viewer in admin tools as suggested. Although a few DHCP events have come up, there isn't an event logged that I could attribute to one of my disconnects.
I decided to ping 192.168.100.1 because I was getting these disconnects, and figured out that when I ping 192.168.100.1, the requests time out during these disconnects. At the same time, 192.168.0.1 does not disconnect.
|Downstream 1||1||705.00 MHz||8.60 dBmV||38.61 dB||256QAM||118838815||12||0|
|Downstream 2||2||699.00 MHz||8.60 dBmV||38.98 dB||256QAM||62447021||11||0|
|Downstream 3||3||693.00 MHz||8.50 dBmV||38.98 dB||256QAM||82037101||5||0|
|Downstream 4||4||687.00 MHz||8.40 dBmV||38.98 dB||256QAM||48019911||8||0|
|Downstream 5||5||681.00 MHz||8.60 dBmV||38.98 dB||256QAM||58040919||9||0|
|Downstream 6||6||675.00 MHz||8.30 dBmV||38.61 dB||256QAM||54169274||10||0|
|Downstream 7||7||669.00 MHz||8.40 dBmV||38.98 dB||256QAM||31775474||6||0|
|Downstream 8||8||663.00 MHz||8.30 dBmV||38.98 dB||256QAM||27285831||7||0|
|Downstream 9||9||657.00 MHz||8.30 dBmV||38.61 dB||256QAM||37384208||7||0|
|Downstream 10||10||651.00 MHz||8.30 dBmV||38.98 dB||256QAM||21874629||5||0|
|Downstream 11||11||645.00 MHz||8.20 dBmV||38.98 dB||256QAM||32104834||6||0|
|Downstream 12||12||639.00 MHz||8.20 dBmV||38.61 dB||256QAM||17609450||1||0|
|Downstream 13||13||633.00 MHz||8.10 dBmV||38.98 dB||256QAM||43869127||16||0|
|Downstream 14||14||627.00 MHz||8.00 dBmV||38.98 dB||256QAM||52910971||5||0|
|Downstream 15||15||621.00 MHz||8.20 dBmV||38.98 dB||256QAM||44481273||0||0|
|Downstream 16||16||615.00 MHz||8.10 dBmV||38.98 dB||256QAM||29819869||11||0|
|Reset FEC Counters|
|UCID||Freq||Power||Channel Type||Symbol Rate||Modulation|
|Upstream 1||9||30.60 MHz||48.00 dBmV||DOCSIS2.0 (ATDMA)||5120 kSym/s||64QAM|
|Upstream 2||12||37.00 MHz||48.50 dBmV||DOCSIS1.x (TDMA)||2560 kSym/s||16QAM|
|Upstream 3||11||23.30 MHz||46.75 dBmV||DOCSIS2.0 (ATDMA)||5120 kSym/s||64QAM|
|Upstream 4||10||18.50 MHz||45.50 dBmV||DOCSIS1.x (TDMA)||2560 kSym/s||16QAM|
09-14-2014 08:43 PM - edited 09-14-2014 08:45 PM
I think you need to either get it in bridge mode and use your own router or exchange it for a different mfg modem, the levels look good... although they're snapshots taken when you hit the page, uncorrectables aren't high, they appear nonexistant. This may be buggy router firmware and not showing up on the modem log.
09-14-2014 09:10 PM
describe your wiring. specifically:
09-14-2014 11:05 PM
No amplifiers or splitters. The TWC cable goes directly into the modem. Our only other cable from the outside is our own antenna (we don't have cable TV).
I just set it in bridged mode and disabled the DG1670s DHCP so my router can assign IP addresses. Everything is functional at the moment, but we'll see if it works. Also, the oddest thing...I can access every website I can think of, except for any google related websites. Why in the world would switching bridge mode make google not work (and only google)?
09-14-2014 11:41 PM
The google thing was a coincidence. It's working now. Maybe google went down for a few minutes...
I noticed a huge speed drop. The router is an old Linksys WRT54G, but instead of getting almost 200 mpbs like before, I'm only getting 30 mbps.
No disconnects so far, though.