onboard lan chips...

  • Thread starter Thread starter BARRY DONOVAN
  • Start date Start date
B

BARRY DONOVAN

I just purchased a pci lan card..
I have a recurring problem with mid-atx and full atx size mobos and onboard
lan chips, I was curious to know if it was common.
The only success I've had error free is a small micro-Atx (versus the bigger
micro-Atx size having same problems)
I always count on purchasing a plug-in lan card, due to these unexplainable
problems. What is my error with the past half-dozen mobos?
 
I just purchased a pci lan card..
I have a recurring problem with mid-atx and full atx size mobos and onboard
lan chips, I was curious to know if it was common.
The only success I've had error free is a small micro-Atx (versus the bigger
micro-Atx size having same problems)
I always count on purchasing a plug-in lan card, due to these unexplainable
problems. What is my error with the past half-dozen mobos?


You haven't told us what they are or aren't doing, and what
you are or aren't doing.

In general onboard lan works fine, have you tried the newest
drivers from the chipset manufacturer? And/or, motherboard
drivers from the chipset manufacturer if the network adapter
has southbridge-integral support?
 
You haven't told us what they are or aren't doing, and what
you are or aren't doing.

In general onboard lan works fine, have you tried the newest
drivers from the chipset manufacturer? And/or, motherboard
drivers from the chipset manufacturer if the network adapter
has southbridge-integral support?

Of course, up to date. Remembering an older explanation a few years ago: If
the chip wasn't maximized (ie: 10mbit mode, versus the 100mbit it could do)
It auto sensed into not quite an error but random auto checking, and it
possibly kicked itself out of smooth operation. Hard setting it to the speed
I want worked a bit better. Now i've got 1000mbit option and running at 100
mbit, auto sense.It is hard to believe that would be the case to this day. I
even stopped allowing it to shut off to save power if idle, didn't work. Now
on the pci card, assigned identical IP, I stay online, no disconnects in the
middle of doing something. This problem of "suddenly no net" happens a month
or so on most of the problem scenarios,coincidentally, after new system
setups with onboard LAN chip only. Why I remember these things brings me a
headache....
 
Of course, up to date. Remembering an older explanation a few years ago: If
the chip wasn't maximized (ie: 10mbit mode, versus the 100mbit it could do)
It auto sensed into not quite an error but random auto checking, and it
possibly kicked itself out of smooth operation. Hard setting it to the speed
I want worked a bit better.

It's an interesting theory, but usually not necessary. I
can't recall the last time I've had to do that and have,
have had, and sold plenty of systems with integrated lan.
Now i've got 1000mbit option and running at 100
mbit, auto sense.It is hard to believe that would be the case to this day. I
even stopped allowing it to shut off to save power if idle, didn't work. Now
on the pci card, assigned identical IP, I stay online, no disconnects in the
middle of doing something. This problem of "suddenly no net" happens a month
or so on most of the problem scenarios,coincidentally, after new system
setups with onboard LAN chip only. Why I remember these things brings me a
headache....

I suspect you blame the network adapter when it isn't a
problem. Reset ALL network adapter settings to their
defaults. Next time the "net" goes down, determine
what/where it goes down. Open a command prompt and ping
that system (from itself), then ping something else on the
lan. If you have a router or broadband modem, try to access
them too. What exactly does "suddenly no net" mean? Be
very specific.
 
Yea I vagualy remember a problem with the autosensing feature. I seem to
remember that 3com (it was their cards I was using) recomended choosing a
matched setting (matched to the nearest router or switch speed)

We did this and recieved no other problems. Eventually these cards were
worked out of the system, and we have not had he problem re-occur.
 
Back
Top