dslreports logo
    All FAQs Site FAQ DSL FAQ Cable Tech About DSL Distance DSL Hurdles »»


3.1 Troubleshooting


If there is/is not a Surge Protector presently connected to your network and damage has been done due to a power surge via the cable line, Road Runner is not liable for any damage done to the network hardware (i.e.: PC, router, etc.). Here's a good interpretation 'quoted' by dbmaven See Profile from a thread in the Road Runner Forum:

said by dbmaven:here :

......they are not liable. If lightning strikes the pole outside, that's considered an 'act of nature' - nothing they can do to prevent it. Same thing would be true if the lightning travelled down your electric wires and blew up your TV/Computer(s)/etc, or hit the telephone wire and blew up all your phones.

For this reason, many UPS units, and slightly more expensive surge protectors (electrical) now include surge protection outlets for telephone lines - and ones intended for home theater include co-ax connectors for cable/satellite.

by drake See Profile
last modified: 2005-10-16 15:19:43

If the cable modem is spontaneously re-booting, and there is no evidence of signal-related problems, then you should check on electrical conditions near to the cable modem. Possible causes of these problems are:

•The cable modem itself is faulty.
•Mains wiring to the cable modem is faulty or intermittent.
•Mains spikes arising from e.g. vacuum cleaners, power tools, heating thermostats, refrigerator thermostats.
•Electromagnetic Interference (EMI), e.g. mobile phone, local radio transmitter.

There are plenty of reports of mobile phones disrupting cable modems if kept too close.

If faulty cable modem, you can take a trip down to your local Road Runner/TWC - Brighthouse Center. Locations listed here.

by drake See Profile
last modified: 2005-10-14 19:46:05

This is due to a well known issue with the Road Runner DNS servers.

The resolution is to add a DNS server that will resolve the .tk domain infrastructure properly.

Please follow these steps if you are having this issue:

1) Record your current DNS servers.

1.a) If you are running Windows NT/2000/XP, open a command prompt and run ipconfig /all and write down your DNS servers.

1.b) If you are running a Linux / Unix variant, open a command prompt/terminal and type cat /etc/resolv.conf - write down the IP addresses returned.

1.c) If you running a Mac OSX variant: INFO NEEDED

2) Change your DNS servers.

2.a) If you're running Windows 2000/XP, go into the control panel and bring up the properties of your local area connection. Add one of your main DNS server IP addresses from step one as the "Preferred DNS Server", then use the IP address '' as the "Alternate DNS Server".

2.b) If you are running a Linux / Unix variant, type echo "nameserver >> /etc/resolv.conf"

2.c) If you are running a Mac OSX variant: INFO NEEDED

You should now be able to resolve .tk domains.

by Matt3 See Profile edited by drake See Profile
last modified: 2005-10-20 01:03:04

WFTRACE is available at: »www.r1ch.net/stuff/ftrace/

A handy gui way to get tracert information. Copy/paste buttons for forum code and raw text.

by dbmaven See Profile
last modified: 2006-10-26 22:41:48

Level 3 routers set a low priority on the ICMP and UDP packets during high load that the line quality test uses. As long as there is no packet loss at your address you are fine. Further explanation here.
»Re: Queens/NYC RR slow downs - gathering support ticket numbers

by MysticGogeta See Profile edited by dbmaven See Profile
last modified: 2007-01-13 20:04:20