Network Card Probs...

  • Thread starter Thread starter evil
  • Start date Start date
E

evil

Hi All... wondering if anyone has any clues about the following;

Mate's puter has probs with his network card (Netcomm I think... it's a
realtek chipset of some type), this is what happens;

1. Card stops working, computer doesn't detect card, no 'link' light on
card. Computer doesn't show any error message or anything, it simply doesn't
detect the card.
2. I change the PCI slot where the network card is plugged => computer
detects card and everything works good until....
3. A couple of reboots later exactly the same thing happens

We've swapped the network card with another known to work reliably but have
the same problem. I'm assuming this might be something to do with the
motherboard... but no there's no sign of conflicts or any such thing...
Motherboard's a AOpen KT266 I think. Puter's running windoze xp with all
hotpatches etc.

Any theories out there? I'm just about out of ideas...

cheers in advance
loic.
loic^*^nodamnspam^*^@dart.net.au
 
Seems like a unreliable motherboard. You'd rather try another system to see
if the problem is the same, with the Netcomm card.
If it does, try to get another motherboard (personally I'm very against
AOpen, I had some bad experiences with it, worse motherboard and a CD-ROM
making the same noise (including level) as a boeing 747).

Next we had a failing motherboard, where Win2k actually was more reliable
than WinXP. This made no difference, both didn't work correctly and a
motherboard replacement solved all issues...

- Joris
 
This is why a responsible manufacturer provided diagnostics
- for free. Diagnostics remove the OS as a potential reason
for failure; simplify analysis. Diagnostic first tests,
comprehensively, computer hardware talking to local network
card's 'logic'. Next two computers (must be same NIC
manufacturer) exchange data continuously to test on a worst
case basis.

Had a working network card that only failed after
diagnostic's data exchange ran for minutes - constantly. IOW
diagnostic discovered by computer had to be periodically
rebooted. Manufacturer's diagnostic is should be executed
before doing anything else.

Second, heat is a tool for locating an intermittent part.
For example, while running that diagnostic constantly, then
selectively heat NIC or motherboard ICs with hairdryer on
high. That heat is quite normal operating temperature for
semiconductors AND may turn an intermittent failure into a
hard failure - only while hot. Heat is a powerful tool to
isolate reason for failure. Actually, we did this test by
resting a hot soldering iron right on top of each IC. When
test failed, then IC touching soldering IC was reason for
failure or connected to defective IC. Just another tool to
locate and solve your mystery.
 
This is why a responsible manufacturer
provided diagnostics - for free.
Click to expand...

Mindless pig ignorant drivel, as always from this pathetic clown.
Diagnostics remove the OS as a potential reason for failure;
simplify analysis. Diagnostic first tests, comprehensively,
computer hardware talking to local network card's 'logic'.
Next two computers (must be same NIC manufacturer)
exchange data continuously to test on a worst case basis.
Click to expand...

Wont necessarily see the problem, clown.
Had a working network card that only failed after
diagnostic's data exchange ran for minutes - constantly.
Click to expand...

Proves sweet **** all about his particular situation, clown.
IOW diagnostic discovered by computer had to be
periodically rebooted. Manufacturer's diagnostic is
should be executed before doing anything else.
Click to expand...
Second, heat is a tool for locating an intermittent part.
For example, while running that diagnostic constantly, then
selectively heat NIC or motherboard ICs with hairdryer on
high. That heat is quite normal operating temperature for
semiconductors AND may turn an intermittent failure into a
hard failure - only while hot. Heat is a powerful tool to
isolate reason for failure. Actually, we did this test by
resting a hot soldering iron right on top of each IC. When
test failed, then IC touching soldering IC was reason for
failure or connected to defective IC. Just another tool to
locate and solve your mystery.
Click to expand...

More utterly mindless pig ignorant silly stuff.
 
evil said:
Hi All... wondering if anyone has any clues about the following;

Mate's puter has probs with his network card (Netcomm I think... it's a
realtek chipset of some type), this is what happens;

1. Card stops working, computer doesn't detect card, no 'link' light on
card. Computer doesn't show any error message or anything, it simply doesn't
detect the card.
2. I change the PCI slot where the network card is plugged => computer
detects card and everything works good until....
3. A couple of reboots later exactly the same thing happens

We've swapped the network card with another known to work reliably but have
the same problem. I'm assuming this might be something to do with the
motherboard... but no there's no sign of conflicts or any such thing...
Motherboard's a AOpen KT266 I think. Puter's running windoze xp with all
hotpatches etc.
Click to expand...

Remove the Nic , boot the computer without the Nic , then shut it down and
then install the Nic and reboot again.
 
Hi All... wondering if anyone has any clues about the following;

Mate's puter has probs with his network card (Netcomm I think... it's a
realtek chipset of some type), this is what happens;

1. Card stops working, computer doesn't detect card, no 'link' light on
card. Computer doesn't show any error message or anything, it simply doesn't
detect the card.
Click to expand...

By 'doesn't detect', you mean the card doesn't show up in Device
Manager at all. Correct?
2. I change the PCI slot where the network card is plugged => computer
detects card and everything works good until....
Click to expand...

'Computer' meaning...it shows up in the boot-up CMOS screen?
3. A couple of reboots later exactly the same thing happens

We've swapped the network card with another known to work reliably but have
the same problem. I'm assuming this might be something to do with the
motherboard... but no there's no sign of conflicts or any such thing...
Motherboard's a AOpen KT266 I think. Puter's running windoze xp with all
hotpatches etc.

Any theories out there? I'm just about out of ideas...
Click to expand...

As w_tom pointed out, you need to separate the problem as being a
software problem or a hardware problem.

Since yer workin' with a PCI card, you should have a disk that came
with the card...or should be able to get one. Boot into that
diagnostic floppy (or read the readme to learn how to use it) and run
the diagnostic software that sets up that card.

If the card checks out okay, you simply have a software (xp) problem.

Good luck...let us know.


Have a nice week...

Trent

Follow Joan Rivers' example --- get pre-embalmed!
 
Back
Top