Posted: 11/20/2007 5:18:21 PM EDT
|
The background... I have wireless set up from a host location beaming hi-speed about 3/4 of a mile away to me. It comes in my house through a bridge then to an AP and wireless throughout the house. On the other end there is a computer running wireless and 1 on a wire. The problem. It locks up at odd times for no reason. To the point the whole set on the other end needs to be rebooted. I had problems in the past and ended up changing on my end to a static IP addy. I am sure the computers on the other end are still allowing theirs to be assigned. When I get locked out I can still get an IP addy whether I change it manual or allow it to be assigned. I am connected to the router but it will pass 1 packet every 5 minutes or so. I am not sure if it is the router on the other end or the cable modem that is locking up. when it locks up for me it does for them as well. At one point I thought it was happening when one of them were connecting but, I have checked and they weren't. The other issues I still haven't encrypted the signal. I know I need to to do it but, anyone have an idea what is causing this? All the big talk I have said above is about the max I know about IT world so go easy on me and type slowly. Thanks. |
|
Since many specifics are being left out, here's a similar scenario I recently faced. Given: Cable internet service provider is Comcast. Modem is a leased Motorola Surfboard SB5101. My modem would lock up and / or drop offline at random. When I logged into my modem via its built-in web browser (http://192.168.100.1), I got the following messages immediately prior to malfunction: 
I Googled the file name and came up with several hits. Apparently, I was not alone. Fishing around those hits, I found that Comcast in their infinite wisdom was trying to cram the wrong firmware down my modem's throat. If you note the file name, "d11_m_sb5100_silver_c01.cm", you will notice that that's a Motorola Surfboard model number. It was nice of them to send me firmware for an SB5100, just too bad that I had an SB5101. First, I went to Comcast's online technician chat. That didn't go so well, when the "tech" said I should "clear cookies and dump cache" and blamed the problem on the one Vista machine on my network. Funny thing is, that the cable modem is independent of the computer, let alone the operating system. I should have told her that I was running Red Hat Linux. About a week later, I called Comcast--on a telephone. That ended up much worse. The immigrant on the other end asked me if my modem was plugged in and just read her script. When she told me to disconnect my router for 24 hours and call back if the problem persisted, I told her something to the effect to pack sand where sand should never be packed. Immediately, I got onto the Comcast Online Chat rigmarole. Here's how that went:
Pregnant women, the elderly, and children should avoid prolonged exposure to Happy Fun Ball. Caution: Happy Fun Ball may suddenly accelerate to dangerous speeds. Happy Fun Ball contains a liquid core, which if exposed due to rupture should not be touched, inhaled, or looked at. Do not use Happy Fun Ball on concrete. Discontinue use of Happy Fun Ball if any of the following occurs: * Itching * Vertigo * Dizziness * Tingling in extremities * Loss of balance or coordination * Slurred speech * Temporary blindness * Profuse Sweating or * Heart palpitations If Happy Fun Ball begins to smoke, get away immediately. Seek shelter and cover head. Happy Fun Ball may stick to certain types of skin. When not in use, Happy Fun Ball should be returned to its special container and kept under refrigeration. Failure to do so relieves the makers of Happy Fun Ball, Wacky Products Incorporated, and its parent company, Global Chemical Unlimited, of any and all liability. Ingredients of Happy Fun Ball include an unknown glowing substance which fell to Earth, presumably from outer space. Happy Fun Ball has been shipped to our troops in Saudi Arabia and is also being dropped by our warplanes on Iraq. Do not taunt Happy Fun Ball. |
|
First Time Last Time Counts Level ID Text Wed Nov 21 01:05:48 2007 Wed Nov 21 01:05:48 2007 1 Critical (3) 68000300 DHCP WARNING - Non-critical field invalid in response. Wed Nov 21 01:05:22 2007 Wed Nov 21 01:05:22 2007 8 Critical (3) 82000200 No Ranging Response received - T3 time-out Wed Nov 21 01:04:52 2007 Wed Nov 21 01:04:52 2007 1 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Un... Wed Nov 21 01:03:38 2007 Wed Nov 21 01:03:38 2007 8 Critical (3) 82000200 No Ranging Response received - T3 time-out Wed Nov 21 01:03:11 2007 Wed Nov 21 01:03:11 2007 1 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Un... Wed Nov 21 01:01:53 2007 Wed Nov 21 01:01:53 2007 12 Critical (3) 82000200 No Ranging Response received - T3 time-out Wed Nov 21 01:00:52 2007 Wed Nov 21 01:00:52 2007 1 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Un... Wed Nov 21 00:59:31 2007 Wed Nov 21 00:59:31 2007 8 Critical (3) 82000200 No Ranging Response received - T3 time-out Wed Nov 21 00:59:04 2007 Wed Nov 21 00:59:04 2007 1 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Un... Wed Nov 21 00:57:47 2007 Wed Nov 21 00:57:47 2007 8 Critical (3) 82000200 No Ranging Response received - T3 time-out Wed Nov 21 00:57:24 2007 Wed Nov 21 00:57:24 2007 1 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Un... Wed Nov 21 00:56:10 2007 Wed Nov 21 00:56:10 2007 20 Critical (3) 82000200 No Ranging Response received - T3 time-out Wed Nov 21 00:53:31 2007 Wed Nov 21 00:53:31 2007 1 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Un... Wed Nov 21 00:52:22 2007 Wed Nov 21 00:52:22 2007 8 Critical (3) 82000200 No Ranging Response received - T3 time-out Wed Nov 21 00:51:53 2007 Wed Nov 21 00:51:53 2007 1 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Un... Wed Nov 21 00:50:32 2007 Wed Nov 21 00:50:32 2007 8 Critical (3) 82000200 No Ranging Response received - T3 time-out Wed Nov 21 00:50:17 2007 Wed Nov 21 00:50:17 2007 1 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Un... Wed Nov 21 00:48:57 2007 Wed Nov 21 00:48:57 2007 8 Critical (3) 82000200 No Ranging Response received - T3 time-out Wed Nov 21 00:48:31 2007 Wed Nov 21 00:48:31 2007 1 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Un... Wed Nov 21 00:47:21 2007 Wed Nov 21 00:47:21 2007 8 Critical (3) 82000200 No Ranging Response received - T3 time-out Wed Nov 21 00:46:58 2007 Wed Nov 21 00:46:58 2007 1 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Un... Wed Nov 21 00:45:36 2007 Wed Nov 21 00:45:36 2007 8 Critical (3) 82000200 No Ranging Response received - T3 time-out Wed Nov 21 00:45:14 2007 Wed Nov 21 00:45:14 2007 1 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Un... Wed Nov 21 00:43:58 2007 Wed Nov 21 00:43:58 2007 8 Critical (3) 82000200 No Ranging Response received - T3 time-out Wed Nov 21 00:43:38 2007 Wed Nov 21 00:43:38 2007 1 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Un... Wed Nov 21 00:42:28 2007 Wed Nov 21 00:42:28 2007 8 Critical (3) 82000200 No Ranging Response received - T3 time-out Wed Nov 21 00:42:07 2007 Wed Nov 21 00:42:07 2007 1 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Un... Wed Nov 21 00:40:49 2007 Wed Nov 21 00:40:49 2007 8 Critical (3) 82000200 No Ranging Response received - T3 time-out Wed Nov 21 00:40:29 2007 Wed Nov 21 00:40:29 2007 1 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Un... Wed Nov 21 00:39:14 2007 Wed Nov 21 00:39:14 2007 12 Critical (3) 82000200 No Ranging Response received - T3 time-out Wed Nov 21 00:37:24 2007 Wed Nov 21 00:37:24 2007 1 Critical (3) 82000400 Received Response to Broadcast Maintenance Request, But no Un... Wed Nov 21 00:36:02 2007 Wed Nov 21 00:36:02 2007 8 Critical (3) 82000200 No Ranging Response received - T3 time-out |
Check all physical cable (CATV / RG-59 / RG-9) connections in entire house as well as check the splitter(s). Last Spring, I had a similar problem. The tech verified all connectors then checked the tap (amplifier) in my front yard. In digital communications, it is understood that there will be some erroneous bits in any given data stream. That is the bit error rate. The BER coming off of the tap (before entering the house) was fluctuating wildly. The problem was being caused by noise being back-fed into the tap by a neighbor. Noise can come from faulty connectors, splitters or even electronic equipment such as TVs. Enjoy dealing with Comcast on this hokey set-up you've got going on. On the bright side, your buddy gets to deal with these monkeys directly. If Century Arms got into the telecom industry, they would be called Comcast. |
