Modem/Cable help... Network issues

[Ross]

As some of you may know, I've been having internet connection problems since moving into my new apartment.

I have tried just about every single combination possible between modem-router-pc, modem-pc, modem-laptop, etc. Basically, I have eliminated all possible errors with the exception of the line coming into the modem.

I've even had the modem itself switched out... I've switched out every piece of hardware I could, save for the one running in from outside.

I don't know what the hell is going on, and I hope one of the networking people on here might be able to find the problem.

Here's some errors I'm getting from my modem (currently Netgear cg814wg):

Time Priority Description
Mon Sep 14 18:33:51 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Mon Sep 14 18:33:38 2009 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Mon Sep 14 18:33:05 2009 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Mon Sep 14 18:28:20 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Mon Sep 14 18:28:08 2009 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Mon Sep 14 18:27:36 2009 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Mon Sep 14 18:14:18 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Mon Sep 14 18:14:10 2009 Critical (3) No Ranging Response received - T3 time-out
Mon Sep 14 18:13:49 2009 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Mon Sep 14 18:13:17 2009 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Mon Sep 14 18:11:55 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Mon Sep 14 18:11:44 2009 Critical (3) No Ranging Response received - T3 time-out
Mon Sep 14 18:11:35 2009 Critical (3) Received Response to Broadcast Maintenance Request, But no Un...
Mon Sep 14 18:11:02 2009 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Mon Sep 14 18:08:52 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Mon Sep 14 18:08:44 2009 Critical (3) No Ranging Response received - T3 time-out

...and that just keeps going.


Here's some specs:

Standard Specification Compliant DOCSIS 2.0
Hardware Version 1.03
Software Version V3.9.26R11-RG


Downstream Channel
Lock Status Locked
Modulation QAM256
Channel ID 6
Symbol rate 5360537
Downstream Frequency 609000000 Hz
Downstream Power 1.1 dBmV
SNR 37.5 dBmV

Upstream Channel
Lock Status Locked
Modulation QAM16
Channel ID 2
Symbol rate 2560 Ksym/sec
Upstream Frequency 33008000 Hz
Upstream Power 43.0 dBmV


And here's a traceroute:

traceroute to google.com (74.125.45.100), 25 hops max, 40 byte packets
1 dom0-10-252-216-163.compute-1.internal (10.252.216.163) 0.108 ms 0.077 ms 0.071 ms
2 10.252.216.2 (10.252.216.2) 0.412 ms 0.426 ms 0.433 ms
3 ec2-75-101-160-48.compute-1.amazonaws.com (75.101.160.48) 0.367 ms 0.377 ms 0.411 ms
4 216.182.224.50 (216.182.224.50) 0.528 ms 0.675 ms 0.656 ms
5 72.21.222.140 (72.21.222.140) 1.726 ms 1.697 ms 1.755 ms
6 72.21.197.35 (72.21.197.35) 1.726 ms 1.429 ms 1.572 ms
7 eqixva-google-gige.google.com (206.223.115.21) 2.009 ms 1.986 ms 1.957 ms
8 209.85.241.50 (209.85.241.50) 3.006 ms 2.979 ms 209.85.240.136 (209.85.240.136) 3.271 ms
9 216.239.48.69 (216.239.48.69) 18.601 ms 18.454 ms 72.14.238.136 (72.14.238.136) 16.956 ms
10 209.85.254.241 (209.85.254.241) 17.491 ms 17.721 ms 72.14.232.215 (72.14.232.215) 17.605 ms
11 209.85.253.145 (209.85.253.145) 19.869 ms 209.85.253.141 (209.85.253.141) 19.403 ms 209.85.253.145 (209.85.253.145) 19.479 ms
12 yx-in-f100.google.com (74.125.45.100) 17.753 ms 17.851 ms 17.732 ms

 

[strawman]

Where are you getting these errors (at the computer, or is the modem giving them?)?

What type of connection (Cable, DSL, ethernet, etc)

Is the modem a router?

Is it configured as a router, and specifically a DHCP server?

What else, if anything, is on your local network?

-Adam

 

[Ross]

I get these errors from the modem itself.

It is a wireless+4-port modem, and it is a router w/ DHCP. HOWEVER, none of this matters, as I was having the problem before with a 4-port (not wireless) modem made by a different company that just acted as a switch (not a router).

The connection is high-speed internet (not turbo), provided by TWC.

I've taken everything off of the network, save for my PC. I've tried just the PC, and just the laptop, and the regular setup (which is supposed to work just fine).

I've also checked for overheating problems... that isn't the problem, either.

Also, the problems seem to occur more often during peak hours, which further leads me to conclude that there's something wrong on their end somewhere.

EDIT:

Also, I should clarify my problem, which is that the signal going into the modem will randomly cut off for a minute or so at random intervals.

 

[strawman]

If you use a different computer does the problem occur with that computer?

-Adam

 

[GeneralOrder24]

How many splitters occur between where the line comes into the building and the cable modem? Too much signal degredation might cause this.

I'd reccomend calling tech support. They'd at least be able to tell you the signal strength to the modem. If it's low, it sounds like a wiring/splitter issue.

 

[Ross]

If you use a different computer does the problem occur with that computer?

-Adam

Same problems. I have tried EVERYTHING on my end, using all sorts of different combinations and configurations with all accessible pieces of hardware. I've basically reduced it to some sort of cable or connection coming from outside, and I was wondering if anyone here could confirm/deny my conclusions.

 

[crono1224]

I'de second the possible excessive degeneration of power through the cable cord, possibly even cut or worn at a certain point. If switching modems doesn't seem to fix it then i wouldn't say its an improperly configured modem.

I'm not sure if there is a tool that can check signal strength of the cord going into the modem, but that would be one of the first causes.

 

[Cuyval Dar]

Just steal your neighbors Wi-Fi, and don't worry about it.

 

[Andromache]

Same problems. I have tried EVERYTHING on my end,

apply fire to the problem. Go get a drink.

 

[PatrThom]

I'm also going to suggest it may be due to signal degradation. It's common with cable runs, especially if there are multiple things on the line.

Another thing to check is to see if your modem is set to refuse ping requests. Some companies ping your modem occasionally to see if you're still there. If you aren't, they'll cut you off and give your bandwidth to someone else.

--Patrick

 

[Ross]

I'm also going to suggest it may be due to signal degradation. It's common with cable runs, especially if there are multiple things on the line.

Another thing to check is to see if your modem is set to refuse ping requests. Some companies ping your modem occasionally to see if you're still there. If you aren't, they'll cut you off and give your bandwidth to someone else.

--Patrick

It is set up to respond to ping requests. I'm going to get a Time Warner person (with a request for a specialist with the cable degradation stuff) out here later this week to look at the outside lines and signals.

 

[Dusty668]

Ok, upstream 43 downstream 1.1, signal seems fine, SNR of 35.7 is well within specs. I can't speak about Raleigh, but in Charlotte I would say don't tell TWC you have this info, as they are not set up in their 'process' for the consumer to have this information. If you say they will have it that will just sidetrack them, and cause them to 'need to address' this issue which will solve nothing.
The traceroute looks good as all are well below 20 ms.
Cable line issues would be my first guess on this, the intermittent part will play merry hell in getting this solved. Especially since it is most likely 2 or more components in a near fail state causing one larger ambiguous problem.

 

[Shannow]

Ok, upstream 43 downstream 1.1, signal seems fine, SNR of 35.7 is well within specs. I can't speak about Raleigh, but in Charlotte I would say don't tell TWC you have this info, as they are not set up in their 'process' for the consumer to have this information. If you say they will have it that will just sidetrack them, and cause them to 'need to address' this issue which will solve nothing.
The traceroute looks good as all are well below 20 ms.
Cable line issues would be my first guess on this, the intermittent part will play merry hell in getting this solved. Especially since it is most likely 2 or more components in a near fail state causing one larger ambiguous problem.

Working for Time Warner myself, I can wholeheartedly agree with this. Good luck, especially with it being intermittant.

 

[Joe Johnson]

Since you never directly answered the question, I'm assuming you DON'T have a splitter in the mix.

I had a similar issue - intermittant issues, bypassed every piece of equipment, still had the issue. I replaced the cheap splitter I had with a decent one (they aren't even that cheap, just look online for the recommended specs of what to look for), and the problem went away immediately.

 

[Ross]

Since you never directly answered the question, I'm assuming you DON'T have a splitter in the mix.

I had a similar issue - intermittant issues, bypassed every piece of equipment, still had the issue. I replaced the cheap splitter I had with a decent one (they aren't even that cheap, just look online for the recommended specs of what to look for), and the problem went away immediately.

No splitters on my end... there's a separate connection off of the modem into each room (which I unplugged all but my own for the time being). The ONLY way that the signal can be dropping is from the lines coming into the building. I have had my laptop connected directly to the modem, and I was still getting the drop-outs.