I'm also experiencing this issue, and the only work around is to set 10mbit full duplex.  Seeing as there's a linux patch which seems to identify this issue, hopefully a windows one isn't too far off.

I've already tried to change the router, without much luck. Under Windows it cannot connect at all on more than 10 Mbit/s. On Kubuntu it connects on 100 Mbit/s but with huge losses (up to 50% of the packets).

I have also upgraded my Kubuntu to the last version (11.10), but the problem persists.

I have found and fixed the issue. My cable was not crimped properly - the ordering of White/Green and White/Blue was reversed (with the B standard).

It is to note that I didn't had any issue when using my old network adapter with the same cable, or when using other computers with it. So, it appears that the Intel adapter is somehow stricter and more vulnerable to standard breaking. Keep it in mind.

If you go into Device Mng. check prop. of NIC there should be a test you can run to check cabling .

I too have had this issue for the past two weeks since windows update updated my drivers on me. This is definitely an issue with the latest drivers. I'm using windows 7 and have th ASUS P8P67 motherboard. Both onboard adapters give me the lost-connection issue described here many times in this thread.

I am using a linksys(I would never buy linksys - I'm in an office where someone else bought the router from staples across the street >.<) WRT610N router and I have a dLink switch in between my computer and it. I hate this router with a passion but, I can tell that it is the latest network adapter driver that is the problem. There are several other computers(PC & MACs) that are connected to the same switch without a problem. There are computers(and phones) connected directly(wired and wireless) to the router without a problem.

Intel needs to fix this issue.

I'm glad I found this thread.  I have an ASUS P8Z68 Mobo, and this was driving me nuts.  Turns out I had the ethernet cable plugged in the wrong LAN port on back of board.  There are two identical ports, they are not marked, but if you look in the manual it shows that one is the RealTek LAN and the other is the Intel LAN.  I could still get connection through RealTek (barely), but moved back over to Intel and you're up and running.  PS, each of the LAN ports have a seperate Mac address.

I recently bought an ASUS P8Z68-V PRO motherboard and have been having similar problems with the NIC as well. My router is a Linksys WRT120N. When set to auto-negotiate its speed is limited to 10mbps/Full Duplex, but works fine. When I set it to 100mbps/Full Duplex sometimes it stays disconnected, sometimes it will find a connection after 30 seconds. Once it is connected my Internet works fine and I can see other computers on the network, but for some reason I cannot access my router's admin page on this one PC. Other PCs on the network do not have these issues.

My main concern is that while I can make the NIC work at 100mbps, it doesn't work all the time and I have to fiddle with it constantly. Setting the speed to 10mbps is too slow to be considered a solution. Plus not being able to access my router's settings is odd, but that's probably a topic on another forum.

Edit:I should add that I'm using Windows 7 Ultimate 64-bit.

worlann wrote:

 

I recently bought an ASUS P8Z68-V PRO motherboard

I don't mean to be funny about this but it IS an Asus motherboard so why not ask Asus about this? If this is going to be discussed on the Intel Community forums, the thread should really be in the Wired Ethernet related section IMO as it doesn't principally relate to Intel branded motherboards. The only (2?) Intel branded motherboards I've seen referenced here with this issue have extenuating circumstances (multiboot for one where a new linux driver and correct network cable wiring seems to have solved things and even a different brand of discrete NIC didn't solve the problem for the other - meaning it's likely a software/configuration issue in the latter case).

Remember people, your support should come from the board supplier or otherwise the board manufacturer because who knows how they have chosen to implement Intels design into their own product.

My suggestion regading your situation worlann is to take your base unit to the position where the other PCs that work fine all are, unplug one of those base units and plug your above base unit in instead - ie using all the same cables and switch ports etc that were known good with other PCs. Failing this making a difference - it's time check for correct network cable internal wiring (as mentioned earlier in the thread). If that still isn't to blame then its time to ask Asus tech support for some help.

My apologies. When searching for solutions on this specific Intel NIC, this was the only thread that looked relevant to my issue.

Don't worry, you're far from the only Asus user who's posted here but really Asus (or their forums) should be where you go for support for this board due to the fact the OEM may implement the Intel hardware in a way that differs to Intels reference design.

If it was a discrete card, I'd agree with youre sentiments about Intel content but in these cases it's an integrated part of the (non-Intel brand) motherboard. It therefore shouldn't be in the Desktop Boards section which is reserved for Intel branded motherboards. Asus probably have their own community for such discussion about their boards.

There is a dedicated forum for Intel Wired Ethernet and I can't see why THAT couldn't be used in this case for the reasons you've given. If all the users with Intel branded boards using this ethernet chip were posting about similar problems I wouldn't be so concerned but that's not the case. Can you guarantee this Intel Ethernet chip has been incorporated into these other brand motherboards using Intel reference designs for their integration, without any alteration?

How about intel motherboards with the exact same issue?

http://forums.techarena.in/motherboard-processor-ram/1444292.htm

Reason why it's mostly people with Asus boards posting? because it was the only 3rd party vendor (I can see at least) that used this particular chipset.  and we all know the volume of intel branded motherboards is vastly lower then most.

The fact of it is, this issue is fixed under linux.  It's a timing issue, and it's nothing to do with how the motherboard vendors implemented it.

I'm trying to be nice, but I'll be honest man, its pretty frustrating when you're having a problem and you don't know how to fix it, and its even more frustrating when someone complains about having to hear about your problem on a support forum.  If our difficulties are bothering you, then by all means go through channels and ask a moderator or admin to make a ruling to move/delete the topic.  I don't think we're going to run the intel forum out of space here; pitch in or mosey along.

shads wrote:

 

How about intel motherboards with the exact same issue?

That link you provided is for boards using Intel Ethernet Chips but not Intel boards ie like the numerous Asus boards already posted about. There is no such thing as an Intel 82579V motherboard - only motherboards that contain that chip/Ethernet hardware. There may be more Asus branded boards out there but there are still pleanty of Intel branded ones too and if this was an issue with the Intel branded boards, we'd be seeing alot more than 2 posts about it (one of which cured the issue with newer Linux drivers and the other who still had network issues even after installing a totally different brand of network card - ie not specific to that hardware). If you don't believe me about this not being an Intel branded motherboard issue, look at the number of posts which do crop up here when Intel has got something wrong (like bugs with some recent BIOS updates for example). The forum was deluged with posts relating to some common issues but this definitely isn't such an issue for Intel branded boards. If all of those people are going to the trouble to post about problems with graphics after BIOS updates etc, I can't see why they wouldn't post about any network problems they may encounter as well but there's been zilch that stands up to closer inspection/hasn't already been fixed.

I don't have access to Asus motherboard design specifics (the only other brand I've seen referred to here apart from the two Intel board owners posts) so I can't say it's nothing to do with how it's been implemented. I suspect only Asus staff would have access to that and it's certainly not safe to assume reference designs have been used throughout by OEMs.

Finally, please understand, the reason I'm posting here is precisely because I do want to contribute to helping those experiencing problems - that's always one of my main motivators for posting here! If I thought for one moment that posting in the Intel Motherboard forum was the best place for Asus motherboard owners to get such issues resolved I'd be all ears but having worked as a computer technician (and dealt with the tech support depts for many brands and used their forums), I know, from experience its important to direct your energies to those responsible for the product you have. This means that in the first instance it's the supplier/retailer and then it's the manufacturer - in this case an OEM. Please understand that I'm not saying this because I'm 'bothered' by your posts and I'm not 'complaining about having to hear this' it's also not that I'm concerned about the Intel forum filled up with posts from Asus board owners - I've already suggested it could be discussed in the Wired Ethernet Intel forum. While I understand your annoyed about this problem that you don't fully understand Arch_Stanton, you've totally misinterpreted my motivation for posting here however and it feels like you're putting words in my mouth that simply aren't me. Even if it turned out that there was a problem with that chip that Intel provided to OEMs (and I hasten to add that I have no reason to believe this is what's causing these problems), who do you think you'd contact to get your board replaced/fixed - again it's the OEM. If you don't beleive me, look at what happened over the Sandybridge SATA issue.

I truely hope that those so affected contact either the Asus people (where it'd be best dealt with IMO) or failing that, use the wired ethernet Intel forum - if you know what's in your best interests you will. As this thread is already quite long and 'established', I don't know if the moderators would move it.