Cable Modem Falling out

[Skybuck Flying]

Hi,

These last couple of days my cable modem sometimes falls out...

Here is the log:

What can you tell from it ?


Time Priority Code Message
040407103125 8-Debug M579.3 CM Cert Upgrade Disabled. Motorola CM
certificate present
040407103125 8-Debug X501.4 Provisioned Unit Update skipped. Image is
current.
040407103125 8-Debug I503.0 Cable Modem is OPERATIONAL
040407103125 8-Debug F502.1 Bridge Forwarding Enabled.
040407103125 8-Debug F502.3 Bridge Learning Enabled.
040407103125 8-Debug B918.0 Baseline Privacy is skipped
040407103124 6-Notice X518.7 Configuration - MMFMME - Update
Disabled - No valid CVC
040407103124 8-Debug I500.1 DOCSIS 1.0 Registration Completed
040407103124 7-Information I500.4 Attempting DOCSIS 1.0 Registration
040407103124 7-Information D509.0 Retrieved TFTP Config File SUCCESS
040407103124 7-Information D507.0 Retrieved Time....... SUCCESS
************ 7-Information D511.0 Retrieved DHCP .......... SUCCESS
************ 5-Warning D3.0 DHCP WARNING - Non-critical field invalid
in response
************ 4-Error D530.8 DHCP - Invalid Log Server IP Address.
************ 5-Warning D520.2 DHCP Attempt# 1 BkOff: 5s Tot DSC:1
OFF:1 REQ:1 ACK:1
************ 7-Information D0.0 DHCP CM Net Configuration download and
Time of Day
************ 7-Information T500.0 Acquired Upstream .......... SUCCESS
************ 8-Debug T503.1 Acquire US with status OK, powerLevel 48,
tempSid 266
************ 8-Debug T505.0 Acquired Upstream with status OK
************ 7-Information T501.0 Acquired Downstream (140000000
Hz)........ SUCCESS
************ 8-Debug T509.0 Acquired DS with status OK, DS Freq
140000000, US Id 1
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 157750000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 157500000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 157250000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 156750000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 156500000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 156250000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing

 

[BigJIm]

check all your connections, then give your IP a call to complain.

 

[Biff]

One thing that looks a little funny is the DS carriers. According to this
log you have 7 of them. Looks like they might have mapped digital boxes
right above HSD. Kinda blows when they do that since Motorola modems start
their hunt group at 450000000 Hz. You have to go all the way around the
spectrum to lock onto downstream if it doesn't hit 140000000 Hz right away.

140000000
157500000
157750000
157250000
156750000
156500000
156250000

What would be interesting to see is what your upstream/downstream carrier
levels are and also the signal to noise ratio. It might be possible that
they are trying to operate in 64 QAM or even 256 QAM and the signal to noise
ration can't overcome the minimum levels. This happens often in a DOCSIS 1.0
environment anda crappy HFC network.

Take a look at the "signal" page. You should see downstream levels close to
0 dBmV and signal to noise hopefully above 21 dB. The higher the better.
Monitor rhis page with a browser refresh and see if it waivers. Upstream
levels should be above 35 dBmV.

 

[Skybuck Flying]

One thing that looks a little funny is the DS carriers. According to this
log you have 7 of them.

You mean these things ?

Actually there were a whole bunch of em... like hundreds.

It seemed to me the cable modem was searching for a good frequency or
something.

Looks like they might have mapped digital boxes

right above HSD. Kinda blows when they do that since Motorola modems start
their hunt group at 450000000 Hz. You have to go all the way around the
spectrum to lock onto downstream if it doesn't hit 140000000 Hz right away.

140000000
157500000
157750000
157250000
156750000
156500000
156250000

What would be interesting to see is what your upstream/downstream carrier
levels are and also the signal to noise ratio. It might be possible that
they are trying to operate in 64 QAM or even 256 QAM and the signal to noise
ration can't overcome the minimum levels. This happens often in a DOCSIS 1.0
environment anda crappy HFC network.

Take a look at the "signal" page. You should see downstream levels close to
0 dBmV and signal to noise hopefully above 21 dB. The higher the better.
Monitor rhis page with a browser refresh and see if it waivers. Upstream
levels should be above 35 dBmV.

This is signal page:

Downstream Value
Frequency 140000000 Hz Locked
Signal to Noise Ratio 35 dB
Power Level 1 dBmV The Downstream Power Level reading is a snapshot
taken at the time this page was requested. Please Reload/Refresh this Page
for a new reading



Upstream Value
Channel ID 1
Frequency 50480000 Hz Ranged

Power Level 48 dBmV


Everything seems normal to me at the moment.

 

[Biff]

Well your levels are quite nice. The modem is not looking for a good
frequency it is looking for one frequency. Don't worry about the No FEC.
That is No Forward Error Control. You might have had a bad modem day. It is
possible that ingress was on the HFC plant and messes you up. The part that
was interesting is that the modems saw every downstream frequency as a
possible match.

 

[Skybuck Flying]

Well your levels are quite nice. The modem is not looking for a good
frequency it is looking for one frequency. Don't worry about the No FEC.
That is No Forward Error Control. You might have had a bad modem day. It is
possible that ingress was on the HFC plant and messes you up. The part that
was interesting is that the modems saw every downstream frequency as a
possible match.

Why is that interesting and what could it mean ?

Is someone trying to hack my cable modem or trying to listen in on it ?

 

[Biff]

no..... you are not even connected at this point. You can put the gun down
now.

 

[Skybuck Flying]

I am connected.

The log was taking after the connection came back online....

 

[Skybuck Flying]

Well

The cable modem fell out again.

I thought it might be wise to sent a e-mail to @home support... in case the
cable modem died later on

First I received a auto-reply stating that I could expect a e-mail from them
within 3 days.

Then I received a e-mail that this problem can not be solved via e-mail.

So today I called the company. (Their support phone number was in the e-mail
as well I think I have it on disk as well )

I talked to the dude... told him what I was thinking. He could see the cable
modem log up to 7 days.

He did see it went down... but he could not tell the problem.

So he offered to send a engineer who will come and take a look at the cable
modem and if he can't find the problem then the cable modem will be replaced


So that will happen in a few days... All in all nice service from the
essent@home company as usual =D

Though I thought I'll take another look at the cable modem log... and indeed
it's starting to look to me like it's slowly dieing

Here is the log:


Time Priority Code Message
040409010314 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010314 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010314 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010314 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010312 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010312 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010312 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010312 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010311 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010311 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010311 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010311 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010310 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010310 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010310 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010310 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010309 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010309 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010309 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010309 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010308 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010308 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010308 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010308 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010307 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010307 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010307 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010307 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010305 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010305 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010305 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010305 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010303 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010303 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010303 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010303 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010300 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010300 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010300 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010300 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010258 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010258 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010258 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010258 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010252 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010252 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010252 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010252 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010249 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010249 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010249 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010249 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010245 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010245 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010245 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010245 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010245 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010245 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010245 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010245 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010244 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010244 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010244 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010244 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010242 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010242 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010242 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010242 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010240 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010240 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010240 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010240 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010237 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010237 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010237 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010237 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010236 7-Information H501.6 HFC: TRC SYNC Recovery OK
040409010236 3-Critical H501.4 HFC: LOST TRC SYNC- trying to recover
040409010236 7-Information H501.12 HFC: FEC LOCK recovery OK
040409010236 3-Critical T5.0 SYNC Timing Synchronization failure -
Loss of Sync
040409010231 8-Debug M579.3 CM Cert Upgrade Disabled. Motorola CM
certificate present
040409010231 8-Debug X501.4 Provisioned Unit Update skipped. Image is
current.
040409010231 8-Debug I503.0 Cable Modem is OPERATIONAL
040409010230 8-Debug F502.1 Bridge Forwarding Enabled.
040409010230 8-Debug F502.3 Bridge Learning Enabled.
040409010230 8-Debug B918.0 Baseline Privacy is skipped
040409010229 6-Notice X518.7 Configuration - MMFMME - Update
Disabled - No valid CVC
040409010229 8-Debug I500.1 DOCSIS 1.0 Registration Completed
040409010229 7-Information I500.4 Attempting DOCSIS 1.0 Registration
040409010229 7-Information D509.0 Retrieved TFTP Config File SUCCESS
040409010218 7-Information D507.0 Retrieved Time....... SUCCESS
************ 7-Information D511.0 Retrieved DHCP .......... SUCCESS
************ 5-Warning D3.0 DHCP WARNING - Non-critical field invalid
in response
************ 4-Error D530.8 DHCP - Invalid Log Server IP Address.
************ 5-Warning D520.2 DHCP Attempt# 4 BkOff: 5s Tot DSC:4
OFF:1 REQ:1 ACK:1
************ 3-Critical D1.0 DHCP FAILED - Discover sent, no offer
received
************ 5-Warning D520.2 DHCP Attempt# 2 BkOff: 6s Tot DSC:2
OFF:0 REQ:0 ACK:0
************ 3-Critical D1.0 DHCP FAILED - Discover sent, no offer
received
************ 5-Warning D520.2 DHCP Attempt# 1 BkOff: 4s Tot DSC:1
OFF:0 REQ:0 ACK:0
************ 3-Critical D1.0 DHCP FAILED - Discover sent, no offer
received
************ 7-Information D0.0 DHCP CM Net Configuration download and
Time of Day
************ 7-Information T500.0 Acquired Upstream .......... SUCCESS
************ 8-Debug T503.1 Acquire US with status OK, powerLevel 48,
tempSid 266
************ 8-Debug T505.0 Acquired Upstream with status OK
************ 7-Information T501.0 Acquired Downstream (140000000
Hz)........ SUCCESS
************ 8-Debug T509.0 Acquired DS with status OK, DS Freq
140000000, US Id 1
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 322000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 314000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 306000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 298000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 290000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 282000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 274000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 266000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 258000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 250000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 242000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 234000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 226000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 218000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 210000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 202000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 194000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 186000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 178000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 170000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 162000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 154000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 146000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 138000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 130000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 122000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 114000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 106000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 98000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 90000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 858000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 850000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS
Freq 842000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure -
Failed to acquire FEC framing
Event Log has reached maximum size. Older log entries are lost.


Bye,
Skybuck.

 

[Skybuck Flying]

Oh...

Reading somebodies other thread I now have a theory how the cable modem
could have died:

Sometimes when I would be offline for a while I would just pull out the UTP
cable.

( To prevent hackers/worms/fbi lol from taking a peek )

I can remember sometimes the speakers would make weird sounds when I did it.

So to make a long story short:

I think some eletricity might have leaked into the cable modem via the UTP
cable...

Ouch that's bad.

Actually it's their own damn fault... since the connector of the UTP cable
is of metal !

If the UTP connector was of plastic this would probably not have happened !
=D

( Also I somebody would invent a switch to turn off/on utp cable that would
be cool )

Bye,
Skybuck.

 

[Biff]

Actually.... the new models of Moto modems has a switch on top that loows
you to turn off the Ethernet portion of the modem and the RF stays
connected. Like a "sleep mode" If you have electricity sparking off of your
Ethernet cable I don't think a metal casing is your main concern.

Besides...... a spark would have just toasted the modem. Not give it errors.

 

[Skybuck Flying]

Hmmm...

Well call me paranoid but I did not use the sleep button because I don't
trust it.

What if hackers found a way to awaken the cable modem ?

( Like ethernet cards... wake on lan activity or something like that (I
never really tried it though) )

So pulling the cable was my safest option =D

Next time I need to stop all activity I will consider to just press the
sleep button

And hopefully my trust in it isn't betrayed lol

( Going to standby mode works fast, Awaken works fast as well, though doing
it repeatedly requires at least one second between it )

Skybuck.

Hmmm my cable modem does have a sleep mode... but euhm I dont use it...
because I think when it'

Actually.... the new models of Moto modems has a switch on top that loows
you to turn off the Ethernet portion of the modem and the RF stays
connected. Like a "sleep mode" If you have electricity sparking off of your
Ethernet cable I don't think a metal casing is your main concern.

Besides...... a spark would have just toasted the modem. Not give it

errors.

 

[Jerry]

I think some eletricity might have leaked into the cable modem via the UTP
cable...

Ouch that's bad.

Actually it's their own damn fault... since the connector of the UTP cable
is of metal !

If the UTP connector was of plastic this would probably not have happened !
=D
Skybuck.

Use an AC Volt meter and unplug the ethernet cable to the modem. Then take
a reading with the meter from the metal jacket on the ethernet cable plug to
the
metal case on the modem. If AC voltage is present, then you have a fault
with
the electrical system in your residence (which can be a fire hazard). If you
have
a 3-prong wall outlet that your PC plugs into, then, using the voltmeter,
take
a measurement (reading) between the third (ground) hole of the outlet and
the
shielding of the coax cable for the modem. Be sure the coax cable is
disconnected
from the modem first. Again, if AC voltage is measured, then you have a
fault in
your house wiring. There is no AC voltage present on the coax cable entering
your home. If you are using "cheater" (3-prong to 2-prong adapter) plugs
anywhere
in your home, then one may be plugged in backwards which can electrify the
ground of the house. I have come across this. To point out the danger
involved,
I showed the owner the 120Volts that I measured from the metal chassis of
his
PC to the copper baseboard heat pipes in the room. Told the owner that
touching his metal kitchen faucet and the metal toaster at the same time
could be dangerous.
Jerry

 

[Maarten Andriessen]

Hi,

These last couple of days my cable modem sometimes falls out...

Een ding is zeker. Engels is niet zijn eerste taal )) Een kabelmodem dat
"uitvalt" wordt absoluut niet vertaald naar "falls out"

Zit hier een Nederlander in het Engels te lullen (ofwel: verliezer!) of zit
hier iemand van een andere nationaliteit die toevallig in Nederland
woont..... en waarvan Engels ook niet de eerste taal is. Een Duitser
mischien

Maarten

 

[Skybuck Flying]

Well

Let me clearify what happened exactly:

Pc

PC netcard [ ] <= metal jacket --- utp cable --- metal jacket => cable
modem.

I unplugged the metal jacket at the PC.

The metal jacket his the casing of the PC.

The soundspeakers started making a weird sound.

I see a couple of possibilities:

1. PC casing is under power.

2. UTP metal jacket is under power from the cable modem.

3. Statical eletricity from the ground maybe ? or maybe me. (probably not).

I am not a technician... I dont have a volt meter...

Maybe the technician that is coming to replace the cable modem has a volt
meter...

I dont understand quite what you are saying.

All plugs in my appartment have only 2 holes.

I am also using what I'll call a "power distributor" because I have too
little power plugs...

So this power distributor makes more power plugs available.

My TV, cable modem and soundspeakers are plugged into that.

I also have a second power distributor.

My PC, a lamp and a printer are plugged into that.

The cable modem is ofcourse plugged into a 'kei' or called 'cable splitter'

That's where the TV and the cable modem or plugged in to watch tv and surf
the net

The ground is of a kind of plastic

So I don't think I am grounded ? I don't think the
devices/machines/equipment are grounded ?

Is not being grounded unsafe ?

I dont know.

Thanks for your concern,

Skybuck.

 

[Noozer]

All plugs in my appartment have only 2 holes.

Then how are you plugging in all your three pronged computer equipment? This
is going to be a major problem for more than just your cable modem.

My TV, cable modem and soundspeakers are plugged into that.

I also have a second power distributor.

My PC, a lamp and a printer are plugged into that.

Same outlet or different outlets? If these are on different electrical
circuits it can be DANGEROUS to your equipment. Everything connected to your
PC should be on the same electrical circuit.

The ground is of a kind of plastic

You can't ground equipment with plastic.

So I don't think I am grounded ? I don't think the
devices/machines/equipment are grounded ?

Is not being grounded unsafe ?

Very!

 

[Skybuck Flying]

Then how are you plugging in all your three pronged computer equipment?

The power distributor as I call it... has like these special holes where the
'black computer cable plugs' go into.

This is going to be a major problem for more than just your cable modem.

Why is that ?

Same outlet or different outlets? If these are on different electrical
circuits it can be DANGEROUS to your equipment. Everything connected to your
PC should be on the same electrical circuit.

Oh my printer is unplugged.

PC and Monitor and Lamp go into power distributor 1.

PC Speakers, TV and cable modem go into power distributor 2.

Power distributor 1 is connected to wall power plug 1.

Power distributor 2 is connected to wall power plug 2.

Printer is connected to pc via parallel cable but I rarely use it.

Cable modem is connected to PC via utp cable.

Speaksers go ofcourse into PC as well.

So I simply do not have enough power holes to connected everything to one
circuit as you say.

Computer, Monitor, Speakers, Cable Modem. ( That's at least 4 devices )

The power distributor only has room for 3.

I talked to my dad. He said like every aparment has like a 'aardlek
schakeler' (in dutch) literally in english: 'earthleak switch'

I am not sure if my appartment has that It probably does... <- wishfull
thinking

You can't ground equipment with plastic.

Yeah but the plastic could rub against my plastic shoes and create like euhm
statical eletricity.

So all the eletricity in my body gets euhm summed up is that right ? I can't
escape to the ground...

So sometimes when I for example wash my hands and I am standing om some sort
of clothing (I dont know the english word for it.. like a drag... piece of
cloath on the ground against cold feet ) with my shoes on I think... I
get like a little shock... so maybe me touching the cable modem metal jack
had the same effect... or maybe it was the pc casing... or maybe my statical
eletricity went into the pc casing and then into the cable modem

As you can see I am totally stupid about eletricity

Very!

Well I am alive so far... so nothing to worry about =D

Skybuck.

 

[BR]

Why is that ?

You're not grounded. Let's say your PSU has a fault and a hot wire touches
the chassis. Now the chassis is at the same potential as the line. Now if
you touch a ground path and touch that chassis, the power will flow though
you. You don't want that. At best you'll get a tingle, at worst...well
call the paramedics.

I talked to my dad. He said like every aparment has like a 'aardlek
schakeler' (in dutch) literally in english: 'earthleak switch'

GFCI:
http://www.codecheck.com/gfci_principal.htm

They work, but you're still putting your faith in their continous correct
operation e.g. they don't fail.

Well I am alive so far... so nothing to worry about =D

Better safe than sorry.