Chassis intrusion

[jayjay66]

Hi,

I'm really hoping somebody can help with this one. I always leave my computer on (I never turn my computer off). I had a power failure during the night last night and when I started my computer up this morning it said "CHASSIS INTRUSION - Press F1 to continue". I pressed F1 and my computer booted-up but "Houston we have a problem". I don't have internet anymore. It says that the network cable is unplugged. But, it's not!!... Arggghhh, I've never seen "CHASSIS INTRUSION" before in my life. I've Googled the CHASSIS INTRUSION error and it says to replace the Jumper and reboot. I did that but I still get the same error. My mobo is Asus 7N8X-VM/400.

Can somebody please help me with this one.

Thanks,
JJ

 

[ski]

Does the network card show up in Device Manager?
If so, are there any problems with it in Dev. Mgr.?
If there are no problems with it, then its cable may be bad.

If the card does not show up in Dev. Mgr., then it may be bad.

 

[jayjay66]

Hi,

Yes, the network card shows up in device manager. You think it's the cable? Why would the PC say "CHASSIS INTRUSION" if it's the cable? I really don't think the cable would give the error of CHASSIS INTRUSION on the mobo.

Anybody else can help with this one please?

 

[jayjay66]

Hi,


Can somebody please help me with this one.

Thanks,
JJ

 

[ski]

If you do not have a chassis intrusion setup installed on your computer(microswitch, wiring, etc.), then the power failure may have triggered the 'Chassis Intrusion' feature in the MB's BIOS, and it's causing the message to display.

If you're using a cable ISP for Internet service, and the ISP's system was not affected by the power failure, then make sure that everything is properly configured in TCP/IP Properties.
If things are ok in TCP/IP, then the network card may have been damaged.

 

[ski]

Also, make sure the cable modem is working properly.

 

[jayjay66]

Hi,

Everything is OK in the TCP/IP. I'm SURE that the power failure did this. I do not have a chassis intrusion setup installed on my computer (microswitch, wiring, etc.).

If the network card was damaged, why would the error come out as "CHASSIS INTRUSION"?? Which is a mobo error, right?

Anybody's help would be greatly appreciated. Please.

Thanks,
JJ

 

[jayjay66]

It's dsl and yes it's properly connected. Ugghhhhh.... what the heck can it be?

 

[ski]

If you have a chassis intrusion setup, then a power failure would trigger the "Chassis Intrusion" message because a power failure simulates the opening of the microswitch.

Did you check to see if there are any problems with your DSL provider's service?

Power failures can cause strange things to happen to a computer, the worst of which is damaging components.
Insert the network card in another slot.
If no luck, then borrow another network card, and see if it works.
If not, then have your DSL modem checked.

 

[edfair]

Chassis intrusion setup and clearing is in the CMOS settings. And since there was a power failure and CMOS is evidently corrupted it would not be too much of a stretch to assume that other things in CMOS may be corrupted.
You may want to clear CMOS per the M/B manual, then set up the variables again.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[KevinADC]

this is a tuff lesson, you should not leave your computer running all the time unless you have it hooked up to an uninterruptible power supply that kicks in during power failures or brown outs. During power failures the power can kick on and off rapidly several times, this is very hard on a computers sensitive electronics. Plus you can have a very big power surge when the electricity does come back online and that can also damage the computer.

 

[jayjay66]

Hi

OK, I cleared the CMOS and reset all the variables. The "CHASSIS INTRUSION" error is gone However, the computer keeps telling me "Network cable is unplugged. Acquiring network address. Network cable is unplugged. Acquiring network address. Network cable is unplugged. Acquiring network address." in a loop at the bottom in the WINXP taskbar. The onboard LAN (integrated in the mobo) light is on in the back of the computer and the cable is plugged in properly.
Any idea on what to do? Please help. Any ideas?
I'll try resetting the CMOS AGAIN, but I'm sure it won't work. Please help.

Thanks,
JJ

 

[electronicsfreak]

Check in bios to be sure onboard lan is not disabled. It should be set to enabled and probally was disabled when you reset it.

 

[jayjay66]

Hi,

Onboard lan is enabled. still have the same problem unfortunately.

Any other suggestions please. I can't believe this darn thing. Any help would be greatlt appreciated. Please help.

Thanks,
JJ

 

[electronicsfreak]

go to command prompt and type ipconfig/release, now type ipconfig/renew . See if that helps, if not right click on my computer left click on manage and make sure network card is enabled and also make sure no yellow or red marks are beside it.

 

[edfair]

And the next step is to remove all networking components, then reinstall.
If this doesn't help you may have a blown LAN setup on the M/B. Solution there is to kill the on-board LAN and install an expansion card.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[jayjay66]

Hi,

OK, so this is what I've done. I've disabled the onboard LAN, & put in another NIC. However, I still get the "Network cable is unplugged. Acquiring network address. Network cable is unplugged. Acquiring network address. Network cable is unplugged. Acquiring network address." in a loop at the bottom in the WINXP taskbar. The NIC light is flashing in the back of the computer and the cable is plugged in properly.
Any idea on what to do? Please help. Any ideas?

Many thanks,
JJ

 

[electronicsfreak]

Try the cable on another computer. I know you said it lights up fine at the router end but the jack or wires going from that end to the other might be messed up. So try the cable on another pc and see if it still does it.

 

[jayjay66]

Hi,

I've changed the cable as well.

Any idea on what to do? Any ideas?

Please

Many thanks,
JJ

 

[electronicsfreak]

Wait for other suggestions but I think you got a bad motherboard.