Ethernet Controller Not Working

[timrob]

I just setup my Asus P5QC motherboard with Windows XP Home SP3.  Everything works except I can't get an internet connection.  Something's wrong with the Ethernet controller.  I installed the software and drivers using the CD.  I reinstalled both.  I tried the latest version of the driver.  The led's on the back of the Ethernet Controller work.  Running ipconfig from a command prompt returns a blank connection-specific dns suffix and a blank default gateway.  autoconfiguration ip address and subnet mask information is populated.  I had Windows try to fix the connection itself with no luck.  This was under control panel, Network Connections, Support Tab, then Repair button.  Cable and modem are good, I tested them on my laptop.  Under device manager, no errors are listed.  There's nothing in Bios that could turn the Ethernet Controller on and off.  Online tech support says I have a bad motherboard and I should RMA the board.  They say it's bad because there's no ip address, but there is an ip address.

A guy at work said he had similar problems with an ASUS motherboard and it was the drivers causing the problem.  You have to boot in Safe Mode and force it to choose different drivers.

I really don't want to uninstall everything and wait 2 weeks for a new board.  I have an old IDE Ethernet controller laying around that I could use.

Is there anything else I can try? 

[Broni]

Whatever you tried already, skip it....

Turn off computer. Disconnect router, and modem from power source for 30 seconds.
Power them back on.
Restart computer.

If that doesn't work, bypass router, and connect computer straight to the modem.

If that doesn't work...
Go Start>Run (Start search in Vista), type in:
cmd
Click OK (in Vista, while holding CTRL, and SHIFT, press Enter).

In Command Prompt window, type in following commands, and hit Enter after each one:
ipconfig /flushdns
ipconfig /registerdns
ipconfig /release
ipconfig /renew

Restart computer.

If that doesn't work...
Go Start>Run (Start search in Vista), type in:
cmd
Click OK (in Vista, while holding CTRL, and SHIFT, press Enter).

At Command Prompt, type in:
netsh int ip reset reset.log
Hit Enter.
Type in:
netsh winsock reset catalog
Hit Enter.

Restart computer.


If that doesn't work...
Download, install, and run WinSockFix: http://www.softpedia.com/get/Tweak/Network-Tweak/WinSockFix.shtml
Restart computer, and check again.

[timrob]

I just now got around to working on this again.  Just moved houses.  Anyway, I tried your ideas, nothing worked.  I reinstalled windows from scratch, without installing the motherboards drivers, then installed a IDE card.  It didn't work.  I reinstalled all the motherboards drivers, then tried both the onboard controller and the IDE card.  Nothing worked.  I tried the latest drivers and nothing worked.

Do you thinking updating the bios would help?  What about removing the battery which would reset the CMOS and start over?  I'm out of ideas.  I doubt I could RMA the board being so late.

[Broni]

Maybe, you need new network card??

[ale52]

Did you try the old NIC - do you know it works / is the ethernet controller enabled in the BIOS?

Alan <>< 

[patio]

With cards being around 15 Bucks i wouldn't waste time RMA'ing the board and be without a system...

[Geek-9pm]

With cards being around 15 Bucks i wouldn't waste time RMA'ing the board and be without a system...

I would RMA it.
He said he tried an IDE card and it didn't work.
The motherboard is not being nice.

[patio]

He hasn't tried the card as of yet...

[timrob]

It's enabled in bios. 

I tried an old IDE card that I know worked and a brand new one, D-Link and LinkSys.  Nothing out of both of them.  So it's not just the onboard chip, it's something with the system.

[Broni]

What on-board chip are you referring to?

[Geek-9pm]

This is a brand-new motherboard. -- Right?
Send it back to the maker or vendor.
It has a defect.
Trust me.

[timrob]

"What on-board chip are you referring to?" The Ethernet chip or whatever controls it.  It has onboard Ethernet.

"This is a brand-new motherboard. -- Right?"  It's 8 months old, I just never got around to setting it up.

If I could get just a regular card working, I'd be happy.  I don't know why it won't work either.  It must be something related.

[dahlarbear]

Trust me.

Trust, but verify...

timrob:  You're all over the place.  Pick one configuration and stay with it until you've proven it doesn't work.  Keep it simple.  Use the "ping" command and pick a "local" node to test against (laptop or home router?).  Manually set the TCP/IP configuration parameters of your network connection (IP address, subnet mask) to be compatible with your test node.  Then "ping" it.  But "disable" any software firewalls first.  From a command prompt window:

     a.  ping 127.0.0.1
     b.  ping <your_own_ip_address>    ; e.g. 192.168.1.4
     c.  ping <test_node_ip_address>    ; e.g. 192.168.1.3

Then attempt to "ping" from test node computer back to the problem computer.

You should use "cross-over" ethernet cable for computer to computer connection.  A "straight-through" ethernet cable for computer to LAN switch port of home router.

I'd delete all the existing network connections, pull the add-in ethernet cards out and go with the built-in one.  Reboot and establish a new LAN connection.  Not sure whether you'd have problem with old drivers lying around.  If that doesn't work, I guess I'd go with one of the newer NIC cards.  Check for resource conflicts (IRQs).

[Geek-9pm]

Quote from: Geek-9pm on Today at 06:26:22 PM
Trust me.
Trust, but verify...

Verified.
Board has a history of bad defects.
(I do not mean a lot of defects, but a fatal few. Infant mortality.)

[timrob]

I found the boards Ethernet Utility.  It didn't tell me anything I didn't know.

Anybody want to buy a barely used board, cheap?