Problem with LAN on Asus P5VDC-X

[dfgh11]

I'm Having a problem with the on board LAN adapter. It will not connect to the internet or any of the other computers on my network.Device manager says that everything is ok with it(although it does say it can't start the 1394 net adapter) and the adapter itself seems to have the correct IP addresses assigned to it, but still nothing. I am using windows MCE 2005

[Nelson37]

Seems to have??? Based on what? Tea leaves?

Static the IP. Ping yourself, the gateway, another pc, and the DNS server. Report results.

[dfgh11]

This coming from a guy that under his computer details it says 'Motherboard : I forget' .Yes, tea leaves what else? why what do you use?I have done all the obvious shit, if I hadn't then I wouldn't be here. You should be able to tell me what's wrong from the information I've give you, to justify that attitude.If I were to list everything I've done then I would be here all day.
They all timed out except for pinging myself.

[redwudz]

If you haven't tried this, uninstall the LAN in Device Manager, then reboot and reinstall the LAN driver. Run the networking wizard.

If that doesn't help, try a PCI LAN card to confirm that your problem isn't with the on board LAN. I switched over to Gigabit LAN, so I don't use the on board LAN on my computers.

Then there is always MS: http://www.microsoft.com/windowsxp/using/networking/expert/russel_05sept19.mspx

[dfgh11]

If you haven't tried this, uninstall the LAN in Device Manager, then reboot and reinstall the LAN driver. Run the networking wizard.

If that doesn't help, try a PCI LAN card to confirm that your problem isn't with the on board LAN. I switched over to Gigabit LAN, so I don't use the on board LAN on my computers.

Then there is always MS: http://www.microsoft.com/windowsxp/using/networking/expert/russel_05sept19.mspx

Thanks for the suggestions. I did try a wireless adpater first actually but it kept crashing my system when using MCE 2005. This is what made me switch over to the ONboard LAN. I have tried uninstalling and reinstalling and it takes an absolute age to even access the properties of it in device manager. This leads me to believe that the board is perhaps faulty, or at the very least, the bios;the LAN itself is saying 'connected' and the right adresses in its status window is the thing that's throwing me off here. To make sure it wasn't a conflict in MCE I installed a fresh Vista b2 last night, but I still get the same problem with the onboard LAN. The wireless adapter however, doesn't seem to crash my system anymore.That said, I would still like to figue out what the problem is here. I will trying some of your other suggestions and repost. Thanks.

[dfgh11]

ok, so my continuous efforts to try and get this to work have failed, and I'm convinced now that it must be a fault with the board itself. The LAN adapter has all the correct ip's assigned to it and the status window says that it is sending data but it appears that it's not recieving any.

[redwudz]

I have gotten my network settings so messed up that nothing would work at times. I keep around a couple of old LAN cards and plugging one of them in seems to fix it with a fresh setup.

But if you reinstalled the OS, you should have started with a clean slate. If you have a spare PCI slot, I would just pick up a cheap 10/100 LAN card and see if it works. They are usually less than $10US even when bought locally. My cable company gave me a couple for free. A LAN card can fail, just like a modem if there is a sufficient voltage spike on the line. Or it might have just been it's time to go.

One last thought, though you likely tested it, is a bad CAT5 cable. I had one I could receive and not send. My own fault. I had a sold wire CAT5 cable and the RJ45 ends were for stranded cable. I didn't realize they took different connectors. I changed the stranded versions twice on each end to try to make it work. The cable was in the wall, so I couldn't check the wires for continuity. I located the proper connector in a electronics store and it works fine now.

[InXess]

ok, so my continuous efforts to try and get this to work have failed, and I'm convinced now that it must be a fault with the board itself. The LAN adapter has all the correct ip's assigned to it and the status window says that it is sending data but it appears that it's not recieving any.

If you got the IP's then it works... as IP's are assigned by other devices not your LAN card (unless set by your system: 169.xxx.xxx.xxx - this IP is entered in absence of IP from the network, if this is what you have your pc is probably NOT connecting, for a variety of reasons, not just bad hardware). Since you have little practice with pc's setup issues it would be good to find a friend who can guide you. Your conclusion that it must be a motherboard is premature.

[dfgh11]

Since you have little practice with pc's setup issues

Not sure what you mean by this.
I wouldn't say it is premature at all, I think I've been quite thorough.I've had no problem with the other four computers I've added to my network.I'm not really sure what else there is to try. Even when I disable the the onboard LAN in the bios, it still shows up in windows, which it shouldn't do, for one.Another thing is that I tried a wirless LAN adapter in a spare PCI Slot and it connects fine for a while. That is untill I receive any sort of data , either via the internet or network.During this process the whole computer crashes - I don't think I'm stretching here to relate the two problems.

One last thought, though you likely tested it, is a bad CAT5 cable. I had one I could receive and not send. My own fault. I had a sold wire CAT5 cable and the RJ45 ends were for stranded cable. I didn't realize they took different connectors. I changed the stranded versions twice on each end to try to make it work. The cable was in the wall, so I couldn't check the wires for continuity. I located the proper connector in a electronics store and it works fine now.

thanks for the suggestion. I did think of this and found that it not to be the source of the problem.Thanks for all the suggestions.Luckily, it's still under waranty and they're picking it up tomorrow I should know by the end of the week if they confirm my diagnosis

[redwudz]

That sounds like a good move. In general, networking is not that complicated. Most problems I have had were by my own creation. But a faulty card or MB can mess a lot up. Let us know how it worked out. Good luck.

[Nelson37]

IPCONFIG is the proper tool to determine IP address configuration.

My motherboard is listed that way because I currently have six in operation, and 3 more ready to go, with changes 3 or four times a year. Also because I do not need to ask hardware-related questions.

You have not listed your router or switch, not specified if using DHCP, and are running a beta OS. Multiple possible problems.

Do a point-to-point to another PC using a crossover cable, ping test. Disconnect all devices except router (if present) static code the ip address, ping the router (Gateway). Disconnect the LAN cable and check listed connection status in card's properties.

You could have a chattering card in another PC, conflicting IP or MAC addresses (yes, this is possible), bad DHCP, any number of things.

When you have repaired PC's for over 15 years I will accept your statement that "you have done all the obvious shit". My experience tells me to NEVER, under ANY circumstances, to accept such a statement because they are almost always wrong. Check the number of important data points you have not addressed. Typical.

[dfgh11]

IPCONFIG is the proper tool to determine IP address configuration.

My motherboard is listed that way because I currently have six in operation, and 3 more ready to go, with changes 3 or four times a year. Also because I do not need to ask hardware-related questions.

You have not listed your router or switch, not specified if using DHCP, and are running a beta OS. Multiple possible problems.

Do a point-to-point to another PC using a crossover cable, ping test. Disconnect all devices except router (if present) static code the ip address, ping the router (Gateway). Disconnect the LAN cable and check listed connection status in card's properties.

You could have a chattering card in another PC, conflicting IP or MAC addresses (yes, this is possible), bad DHCP, any number of things.

When you have repaired PC's for over 15 years I will accept your statement that "you have done all the obvious shit". My experience tells me to NEVER, under ANY circumstances, to accept such a statement because they are almost always wrong. Check the number of important data points you have not addressed. Typical.

oh, right....................

That sounds like a good move. In general, networking is not that complicated. Most problems I have had were by my own creation. But a faulty card or MB can mess a lot up. Let us know how it worked out. Good luck.

They confirmed that it was faulty and are sending me a new one.