Saved Bookmarks
| 1. |
Solve : Ethernet Controller Not Working? |
|
Answer» 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. 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.He hasn't tried the card as of yet...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.What on-board chip are you referring to?This is a brand-new motherboard. -- Right? Send it back to the maker or vendor. It has a defect. Trust me."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.Quote from: Geek-9pm on December 25, 2009, 06:26:22 PM 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 ; e.g. 192.168.1.4 c. ping ; 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).Quote Quote from: Geek-9pm on Today at 06:26:22 PMVerified. Board has a history of bad defects. (I do not mean a lot of defects, but a fatal few. Infant mortality.) 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? |
|