At home where I built and tested, everything works fine, no issues from beginning to end.
I deliver the PC to its new owner (family member, luckily) and the onboard LAN won't recognize the cable. A few minutes later, it refreshes and discovers the cable, everything seems fine. I completed a few last minute personalization items and needed a restart. Upon restart, no cable detected, and it remained that way, undetected. After swapping and testing every cable I had with a laptop, all cable were confirmed working, as was the router and broadband connection.
After hours of reinstalling drivers and updating firmwares, wasting time on the phone with ASUS tier 1 support, etc, I decided to RMA the board at the request of ASUS. I get the board back a week later, reinstall again, test it at my home, use different cables, restart numerous times, works perfect.
I then bring the PC back to its new owner, promising a fix, and of course...same damned problem. I told him his house must be built on an old cemetery or something, but he wasn't buying it
The router is a linksys e2500, firmware is up to date, wireless and other LAN devices function with 100% connectivity. All ports tested, confirmed working on other hardware.
Motherboard is an ASUS P8Z68-V/gen3. All of the drivers (chipset, LAN, USB, etc) are current.
I'm stumped...why does it function perfectly in my home, but not his? The two variants, router and modem, seem to function just fine.
What would cause the connection to fail on restart, but eventually, with no user intervention, connect and stay connected until another restart?
I'm going to install a NIC card in the next few days and see if it's simply the onboard. At that point I'll be furious with ASUS, but I'll at least know the source of the issue. But that still wouldn't explain why it functions at my home...
If I were you I would bring your own router to the scene of the crime and see if it works when you substitute it. If so, then his router is to blame. I would start with resetting his router to default. I've had similar issues with the same message you are receiving, it was link speed negotiation with the router. Maybe you could try forcing the new PC to run at 10 or 100 Mb mode, instead of the default Auto or 1000 Mb mode.
Something else to bear in mind, it could be a patch cable problem at his home. My own setup at home is fully gigabit (other than internet router) and I periodically come across bad cables when I move my rigs around. Initially it presents itself as a broken cable until it can negotiate a speed it's happy with, normally 100Mb/s.
I would suggest checking "Task Manager" under the Networking tab to see what link speed he is actually getting.
Check the route of his cabling in case it's getting interference from the mains electrics.
Try your own patch cable on his kit in his home as well.
Thanks guys, it eventually did pick up the cable again. I jumped into his box with RD and sure enough the speed was only 10Mb, and should be a 100Mb connection. I had him swap out the patch cable between his router and modem, and now we've lost the connection to the pc again...
Seems we have narrowed the problem down to speed negotiation, assuming that the previously mentioned cable is not the issue, what are the other possibilities?
Once it's back online I can again RD in and check any onboard nic settings, but since it worked on my gig router, I'm assuming it's not the new box. Which leaves the router...I have remote access to that as well, and after poking around did not see any settings to change connection speed.
Getting closer to a solution though, so thanks guys!
make sure you have the newest network drivers for the mb. the newest drivers are on intel web page. make sure on the mb install cd you did not install Network iControl V1.03.09 for Windows Win7 32bit & Win7 64bit & Win8 32bit & Win8 64bit.
there a big bug in it that is causes the network speed to slow way down...know issue on the rog forum. the last could be a firmware or chipset issue with the onboard intel and the router.
I did, have you tried forcing the duplex/speed settings? Sometimes NICs don't work well with other hardware (Cisco is known for this) and auto-negotiation fails to the lowest speed. Did installing a different nic card help?
Forcing the duplex setting to 10M is the only thing that works, which is probably fine for his needs, but it would be nice if it would run at 100 as it should. Trying to force 100Mb kills the connection and causes the "cable not plugged in" error, along with other system wide errors. This issue is widely reported on a number of boards that have the intel 82579 LAN.
The nic card worked fine, so the error is definitely narrowed down to a bad LAN/driver/router combo that will most likely not be fixed.
what will happend if you install the lan driver from asus and try to see if the network off the owner is been detect by the internal lan card als o if you use win 7 try to create a new network connection with the owner network