|
Posted by Ed Stevens on February 19, 2006, 4:53 pm
If you were Registered and logged in, you could reply and use other advanced thread options
My ISP is Comcast, in the middle Tennessee area.
Some time ago I began to get sporadic connections -- would not be able
to get to the internet for a couple of hours, then could. Finally got
a service tech to come out. He first said the cable modem had gone
bad, and replaced it. But the new one 'won't synch up', so he went
through a couple of more, then decided it must be the line. Put a
test instrument on it, and said the signal was "too hot." Called
another tech out to go up the pole. They futzed around some more, an
finally said they'd come back the next morning. (This was getting into
the evening on Friday, and they were way over on their shift.)
Well, as you can guess, they never came back. I've not had any
service interruptions since, BUT ...... ever since that visit, the
'data' LED on the modem is consantly flashing at a very high rate.
Even when the computer is turned off. (This is a Teradyne modem, with
the LED's labeld 'Power', 'Cable', 'PC', 'Data', and 'Test'. I'm
presuming the Power, Cable, and PC are exactly what one would expect,
and the Data and Test are really Send and Receive.
I've not called Comcast, because I *DO* have service, but it still
seems that something "just ain't right."
Thoughts?
|
|
Posted by on February 19, 2006, 5:13 pm
On Sun, 19 Feb 2006 15:53:15 -0600, Ed Stevens
>My ISP is Comcast, in the middle Tennessee area.
>
>
>Some time ago I began to get sporadic connections -- would not be able
>to get to the internet for a couple of hours, then could. Finally got
>a service tech to come out. He first said the cable modem had gone
>bad, and replaced it. But the new one 'won't synch up', so he went
>through a couple of more, then decided it must be the line. Put a
>test instrument on it, and said the signal was "too hot." Called
>another tech out to go up the pole. They futzed around some more, an
>finally said they'd come back the next morning. (This was getting into
>the evening on Friday, and they were way over on their shift.)
>
It's normal "background " cable activity. Can't explain any better.
Mine goes nuts also.
|
|
Posted by Gene S. Berkowitz on February 19, 2006, 6:23 pm
> On Sun, 19 Feb 2006 15:53:15 -0600, Ed Stevens
>
> >My ISP is Comcast, in the middle Tennessee area.
> >
> >
> >Some time ago I began to get sporadic connections -- would not be able
> >to get to the internet for a couple of hours, then could. Finally got
> >a service tech to come out. He first said the cable modem had gone
> >bad, and replaced it. But the new one 'won't synch up', so he went
> >through a couple of more, then decided it must be the line. Put a
> >test instrument on it, and said the signal was "too hot." Called
> >another tech out to go up the pole. They futzed around some more, an
> >finally said they'd come back the next morning. (This was getting into
> >the evening on Friday, and they were way over on their shift.)
> >
> It's normal "background " cable activity. Can't explain any better.
> Mine goes nuts also.
It's called Address Resolution Protocol, or "ARP", and it's how the
network associates hardware, which only has a MAC address, with the IP
addresses handed out by the cable co's DHCP server, and yes, it's very
normal, and means things are actually working...
--Gene
|
|
Posted by DLR on February 20, 2006, 9:21 am
Gene S. Berkowitz wrote:
>>> My ISP is Comcast, in the middle Tennessee area.
>>> Some time ago I began to get sporadic connections -- would not be able
>>> to get to the internet for a couple of hours, then could. Finally got
>>> a service tech to come out. He first said the cable modem had gone
>>> bad, and replaced it. But the new one 'won't synch up', so he went
>>> through a couple of more, then decided it must be the line. Put a
>>> test instrument on it, and said the signal was "too hot." Called
>>> another tech out to go up the pole. They futzed around some more, an
>>> finally said they'd come back the next morning. (This was getting into
>>> the evening on Friday, and they were way over on their shift.)
>>>
>> It's normal "background " cable activity. Can't explain any better.
>> Mine goes nuts also.
>
> It's called Address Resolution Protocol, or "ARP", and it's how the
> network associates hardware, which only has a MAC address, with the IP
> addresses handed out by the cable co's DHCP server, and yes, it's very
> normal, and means things are actually working...
>
It is also the various internet bots, viruses, etc... walking the IP
addresses pissibilities looking for unpatched systems to infect. Which
is why you always run a router these days.
|
|
Posted by DLR on February 20, 2006, 9:23 am
Gene S. Berkowitz wrote:
>>> My ISP is Comcast, in the middle Tennessee area.
>>> Some time ago I began to get sporadic connections -- would not be able
>>> to get to the internet for a couple of hours, then could. Finally got
>>> a service tech to come out. He first said the cable modem had gone
>>> bad, and replaced it. But the new one 'won't synch up', so he went
>>> through a couple of more, then decided it must be the line. Put a
>>> test instrument on it, and said the signal was "too hot." Called
>>> another tech out to go up the pole. They futzed around some more, an
>>> finally said they'd come back the next morning. (This was getting into
>>> the evening on Friday, and they were way over on their shift.)
>>>
>> It's normal "background " cable activity. Can't explain any better.
>> Mine goes nuts also.
>
> It's called Address Resolution Protocol, or "ARP", and it's how the
network associates hardware, which only has a MAC address, with the IP
addresses handed out by the cable co's DHCP server, and yes, it's very
normal, and means things are actually working...
>
It is also the various internet bots, viruses, etc... walking the IP
addresses possibilities looking for unpatched systems to infect. Which
is why you always run a router these days.
|
| Similar Threads | Posted | | Intermittent Service Interruptions | May 23, 2005, 11:52 am |
| Charter Pipeline service | July 30, 2005, 7:09 pm |
| fixed IP for DHCP service at cox.net? | September 7, 2006, 5:31 pm |
| comcast business service, teaming | February 20, 2006, 8:18 pm |
| Cox Business Service and my Linksys BEFCMU10 ver.3 | February 27, 2006, 10:43 pm |
| Cox Business Service and my Linksys BEFCMU10 ver.3 | February 27, 2006, 11:30 pm |
| Cox Business Service and my Linksys BEFCMU10 ver.3 | February 27, 2006, 11:40 pm |
| Wireless Cable Service Info | October 5, 2006, 4:35 pm |
| Wireless Cable Service Info | November 3, 2006, 3:29 pm |
| Cable Modems and Internet Service | May 2, 2008, 8:27 am |
|
|
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML site map