PDA

View Full Version : Need cable modem experts help


Tr1cK
07-15-07, 02:46 PM
I am getting constant random time-outs with my modem. I am about to go postal on Cox. Here are a copy of the logs. All help is appreciated.

http://img394.imageshack.us/img394/2725/statusok8.jpg
http://img241.imageshack.us/img241/7053/logeo7.jpg

grey_1
07-15-07, 04:14 PM
I don't know the exact specs Cox uses in your area, but at a guess I would say your downstream power is low. SNR and upstream look good, but again it's hard to tell. You can be within specs yet still way off from what it "should" be at.

Some things I would check that can interfere.

Are all cable, not just modem, all cable fittings tight?

Do you have Cox video? How are your pictures? Diagonal lines or snowy pics are a dead give away either something is loose, water damaged outside drop or other equipment, etc.

Can you hook the modem up where your service comes into the house, before any splitters? If so see if it stays locked up. Ideal would be to run a long cat5 to your pc and check reading from the 2 locations.

If it's still wonky where your service comes in "chances are" it's either your drop, an outside fitting/splitter or further back in your plant.

Do neighbors have the service? How is thier working?

Not much to go on Tr1ck, but it's a start. :o

mullet
07-15-07, 05:15 PM
The modem levels look awesome!! the downstream is .7 which is almost 0 which is perfect. I will say this after tons of calls with people with a linksys modem they had problems with the modem disconnects, I don't know what the specific problem was but belkin had the same problems. Have you tried to statically adding different DNS address's. I know comcast DNS sux and some times I used different DNS address's and then the pages pop up really fast compared to comcast.

Input to cable modem (Downstream) = -15 to +15 dBmV
From cable modem (upstream) = +8 to +55 dBmV (16 QAM)


T4 timeouts, The CMTS (usually cisco router UBR) sends a Unicast poll transmition ( or keepalives ) to the modem to assign a SID if it can't do this within 30 seconds it gets a T4 timout.

Tr1cK
07-15-07, 07:45 PM
Technician was out a few weeks ago. He said everything was as good as it gets. He replaced the grounding block and splitter too. I'm really trying to find out what causes the time outs.

retsam
07-15-07, 07:54 PM
Technician was out a few weeks ago. He said everything was as good as it gets. He replaced the grounding block and splitter too. I'm really trying to find out what causes the time outs.
post a tracert, pathping and ping -n 50 ...

Tr1cK
07-15-07, 08:04 PM
Tracing route to nvnews.net [70.87.46.147]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.11.1
2 9 ms 9 ms 13 ms 10.64.128.1
3 20 ms 8 ms 8 ms rnkesysj02.rn.hr.cox.net [68.10.11.77]
4 13 ms 14 ms 14 ms nrfkdsrj02-so030.rd.hr.cox.net [68.10.8.245]
5 49 ms 47 ms 47 ms dalsbbrj02-so100.r2.dl.cox.net [68.1.1.194]
6 50 ms 47 ms 49 ms et2-25.ibr05.dllstx3.theplanet.com [70.85.126.225]
7 52 ms 47 ms 58 ms vl32.dsr01.dllstx3.theplanet.com [70.85.127.61]
8 47 ms 47 ms 47 ms po31.dsr01.dllstx4.theplanet.com [70.87.253.74]
9 47 ms 50 ms 48 ms gi1-0-1.car16.dllstx4.theplanet.com [67.18.116.67]
10 48 ms 47 ms 49 ms 93.2e.5746.static.theplanet.com [70.87.46.147]

Trace complete.





Pinging nvnews.net [70.87.46.147] with 32 bytes of data:

Reply from 70.87.46.147: bytes=32 time=50ms TTL=55
Reply from 70.87.46.147: bytes=32 time=47ms TTL=55
Reply from 70.87.46.147: bytes=32 time=48ms TTL=55
Reply from 70.87.46.147: bytes=32 time=47ms TTL=55
Reply from 70.87.46.147: bytes=32 time=47ms TTL=55
Reply from 70.87.46.147: bytes=32 time=48ms TTL=55
Reply from 70.87.46.147: bytes=32 time=49ms TTL=55
Reply from 70.87.46.147: bytes=32 time=47ms TTL=55
Reply from 70.87.46.147: bytes=32 time=48ms TTL=55
Reply from 70.87.46.147: bytes=32 time=49ms TTL=55
Reply from 70.87.46.147: bytes=32 time=62ms TTL=55
Reply from 70.87.46.147: bytes=32 time=47ms TTL=55
Reply from 70.87.46.147: bytes=32 time=48ms TTL=55
Reply from 70.87.46.147: bytes=32 time=60ms TTL=55
Reply from 70.87.46.147: bytes=32 time=50ms TTL=55
Reply from 70.87.46.147: bytes=32 time=50ms TTL=55
Reply from 70.87.46.147: bytes=32 time=51ms TTL=55
Reply from 70.87.46.147: bytes=32 time=48ms TTL=55
Reply from 70.87.46.147: bytes=32 time=49ms TTL=55
Reply from 70.87.46.147: bytes=32 time=47ms TTL=55
Reply from 70.87.46.147: bytes=32 time=50ms TTL=55
Reply from 70.87.46.147: bytes=32 time=47ms TTL=55
Reply from 70.87.46.147: bytes=32 time=49ms TTL=55
Reply from 70.87.46.147: bytes=32 time=48ms TTL=55
Reply from 70.87.46.147: bytes=32 time=50ms TTL=55
Reply from 70.87.46.147: bytes=32 time=53ms TTL=55
Reply from 70.87.46.147: bytes=32 time=50ms TTL=55
Reply from 70.87.46.147: bytes=32 time=49ms TTL=55
Reply from 70.87.46.147: bytes=32 time=48ms TTL=55
Reply from 70.87.46.147: bytes=32 time=53ms TTL=55
Reply from 70.87.46.147: bytes=32 time=51ms TTL=55
Reply from 70.87.46.147: bytes=32 time=46ms TTL=55
Reply from 70.87.46.147: bytes=32 time=50ms TTL=55
Reply from 70.87.46.147: bytes=32 time=50ms TTL=55
Reply from 70.87.46.147: bytes=32 time=49ms TTL=55
Reply from 70.87.46.147: bytes=32 time=50ms TTL=55
Reply from 70.87.46.147: bytes=32 time=52ms TTL=55
Reply from 70.87.46.147: bytes=32 time=51ms TTL=55
Reply from 70.87.46.147: bytes=32 time=49ms TTL=55
Reply from 70.87.46.147: bytes=32 time=48ms TTL=55
Reply from 70.87.46.147: bytes=32 time=49ms TTL=55
Reply from 70.87.46.147: bytes=32 time=50ms TTL=55
Reply from 70.87.46.147: bytes=32 time=49ms TTL=55
Reply from 70.87.46.147: bytes=32 time=50ms TTL=55
Reply from 70.87.46.147: bytes=32 time=50ms TTL=55
Reply from 70.87.46.147: bytes=32 time=49ms TTL=55
Reply from 70.87.46.147: bytes=32 time=51ms TTL=55
Reply from 70.87.46.147: bytes=32 time=52ms TTL=55
Reply from 70.87.46.147: bytes=32 time=49ms TTL=55
Reply from 70.87.46.147: bytes=32 time=50ms TTL=55

Ping statistics for 70.87.46.147:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 62ms, Average = 49ms


>pathping nvnews.net

Tracing route to nvnews.net [70.87.46.147]
over a maximum of 30 hops:
0 beefcake.rn.hr.cox.net [192.168.11.2]
1 192.168.11.1
2 10.64.128.1
3 rnkesysj02.rn.hr.cox.net [68.10.11.77]
4 nrfkdsrj02-so030.rd.hr.cox.net [68.10.8.245]
5 dalsbbrj02-so100.r2.dl.cox.net [68.1.1.194]
6 et2-25.ibr05.dllstx3.theplanet.com [70.85.126.225]
7 vl32.dsr01.dllstx3.theplanet.com [70.85.127.61]
8 po31.dsr01.dllstx4.theplanet.com [70.87.253.74]
9 gi1-0-1.car16.dllstx4.theplanet.com [67.18.116.67]
10 93.2e.5746.static.theplanet.com [70.87.46.147]

Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 beefcake.rn.hr.cox.net [192.168.11.2] 0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.11.1 0/ 100 = 0% |
2 11ms 94/ 100 = 94% 94/ 100 = 94% 10.64.128.1 0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% rnkesysj02.rn.hr.cox.net [68.10.11.77] 0/ 100 = 0% |
4 16ms 0/ 100 = 0% 0/ 100 = 0% nrfkdsrj02-so030.rd.hr.cox.net [68.10.8.245] 0/ 100 = 0% |
5 49ms 0/ 100 = 0% 0/ 100 = 0% dalsbbrj02-so100.r2.dl.cox.net [68.1.1.194] 0/ 100 = 0% |
6 49ms 0/ 100 = 0% 0/ 100 = 0% et2-25.ibr05.dllstx3.theplanet.com [70.85.126.225] 0/ 100 = 0% |
7 55ms 0/ 100 = 0% 0/ 100 = 0% vl32.dsr01.dllstx3.theplanet.com [70.85.127.61] 0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% po31.dsr01.dllstx4.theplanet.com [70.87.253.74] 0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% gi1-0-1.car16.dllstx4.theplanet.com [67.18.116.67] 0/ 100 = 0% |
10 51ms 0/ 100 = 0% 0/ 100 = 0% 93.2e.5746.static.theplanet.com [70.87.46.147]

Trace complete.

rflair
07-15-07, 08:27 PM
Have you tried a different NIC.

Tr1cK
07-16-07, 08:38 AM
Have you tried a different NIC.
I really don't think that's an issue here as it's on the other side of a wireless router.

retsam
07-16-07, 09:56 AM
2 11ms 94/ 100 = 94% 94/ 100 = 94% 10.64.128.1 0/ 100 = 0% |your problem seems to be at your first hop after your routerm, notice the high drop rate? you dropped 94 packets our of 100...so its either the router or there (cable co's) node....i would call your isp and tell them of your findings...

Tr1cK
07-16-07, 11:16 AM
your problem seems to be at your first hop after your routerm, notice the high drop rate? you dropped 94 packets our of 100...so its either the router or there (cable co's) node....i would call your isp and tell them of your findings...

The only problem is they want to give me the same idiotic canned response with disconnecting my router and power cycling the modem...what idiots.

Sycario
07-16-07, 01:42 PM
10.64.128.1 would be his cable modem. I would try a different modem. I've read bad things about the linksys cable modems, I bought my own Motorola SB5100 for $30 (with rebate) and have never had any problems. All I had to do was call charter and tell them I got a new modem, they put the MAC in, and I hooked mine up and connected. I'm no expert on cable modems, though. You may want to try going over to DSLReports (http://www.dslreports.com/).

SLippe
07-16-07, 04:08 PM
They may be updating their system/network/cables/fibres etc. in your area. They did this in my area recently. However, I was still getting the timed out errors. What did I do? I ran the Event ID 2446 Patch and set it to the highest possible number, which resets the connections to unlimited now in WinXP. A recent SP2 updated changed this to a limit of only 10! Boo! Also, I changed my DNS' to www.opendns.com's settings as of last night. I was only pulling around 100kb/s from a certain site when downloading and now it's back up to 1Mb/s. :D Also, I downloaded the 162.18 driver from NVIDIA's site at no less than 3.6MB/s...took like 8 seconds. :D

http://img237.imageshack.us/img237/2540/nvidiadownloadspeedhc3.jpg

SpeedTest.net results as of last night;
http://img209.imageshack.us/img209/6729/154935853jq2.png

Cox's own test;
http://img232.imageshack.us/img232/7379/coxspeedtest070807if2.jpg

Tr1cK
07-16-07, 04:30 PM
My net is blazing fast when it isn't timing out. Pings average nice and low and download speeds topping out around 1.2mbs up to 2.4mbs if powerboost is kicking.
I just bought the Linksys as I had a SB5100 that was getting to be about 4 years old and was told it was the culprit. It had more restarts than the Linksys.
This **** has been happening since the middle of May. It happens at anytime of day. The other night was once at 1:58 then again at 2:08.
I always run that patch too, Slippe.

rflair
07-16-07, 06:24 PM
I really don't think that's an issue here as it's on the other side of a wireless router.



Well last year my cable modem was dropping for no reason, sometimes it would happen every 10-20 minutes sometimes last longer, hours. Calls to cable company said everything was fine, diagnostic software said everything was fine, even up to the drop and after the software wasn't picking it up, turned out the on board NIC was screwed.

Why wouldn't you try a different NIC anyways? Try every variable its the best way to problem solve.

retsam
07-16-07, 06:36 PM
Well last year my cable modem was dropping for no reason, sometimes it would happen every 10-20 minutes sometimes last longer, hours. Calls to cable company said everything was fine, diagnostic software said everything was fine, even up to the drop and after the software wasn't picking it up, turned out the on board NIC was screwed.

Why wouldn't you try a different NIC anyways? Try every variable its the best way to problem solve.
he should try but if you look at his pathping you will see its dropping from his router to the cable CO's nod, not from his pc to his router. it would drop friom the nic to the router if it was a bad nic but he should try anyways...

SLippe
07-16-07, 09:04 PM
Hey, Tr1cK, what did you type in at the cmd screen to get that list in Post #6?

EDIT: Nevermind, found them.

Tr1cK
07-17-07, 08:41 AM
I'm trying OpenDNS right now. I haven't been able to sit at my PC long to test it cause of some other things going on. The only problem I have with OpenDNS is that my router doesn't have an option for to get the IP thru DHCP while using only the DNS servers I specify. So it now has 5, I think, DNS IPs listed.