Intel(R) 82579V Gigabit Network device issues

[idata]

Dear.

I have recently bought the new sandy bridge core i5 machine and been trying to install Win SBS 2008, but during the process, it asked me for the driver for the ethernet adaptor. I cannot find any whatever online or the driver CD. Can anyone help me to locate a Intel(R) 82579V Gigabit Network driver for Win SBS 2008 please?

Thanks a lot

Larry

[idata]

Please!  

Send the driver to mailto:Adam.Vincent0@gmail.com Adam.Vincent0@gmail.com fast!I recently installed a computer with Asus Sabertooth P67 and Windows 64 Ultimate for a customer.. And the Network device wont work (error code 10)I've tried everything the past 2 hours, Reinstall/delete driver 20times, 5 kind of Driver programs, new install of Windows 7 and still no clue..I am starting to rip my hair off my head....

Edit: I don't want drivers from the driver center.. I need old ones that work or just a working INF file.

[SWRIG]

The problem you are having is nothing to do with the issue in this topic; this was to do with Intel modifying their .inf files so that you could not install their drivers if you tried to put a Server OS on a desktop motherboard.

That said having looked at your motherboard the unmodifed drivers from my post should install; those are the ones I use on all my Win 7 x64 images, the latest ones just for x64 can be downloaded here http://downloadmirror.intel.com/18718/eng/PROWinx64.exe http://downloadmirror.intel.com/18718/eng/PROWinx64.exe , you should be able to double click the .exe .

If running the setup fails to find the driver then extract the .exe and find the ethernet controller in device manager and install that way.

Just another minor thought, you don't have a wireless card in the machine that you could be confusing with the ethernet?

Hope this helps

Simon

[idata]

Thank you for the answer but i'm still having issues..

As I said, i have tried everything.

No im not using any wireless card.

This is a fresh computer that came in today and i installed it.

Asus Sabertooth B3 P67

i7 2600K8GB DDR3 1600Corsair HX750Geforce GTX 570It does not fail to find the driver, it fails to "use" the device properly.

As seen in this image:

http://imageshack.us/photo/my-images/694/devicem.png/ http://imageshack.us/photo/my-images/694/devicem.png/

Edit:

I am using my iPhone as internet right now, it doesn't matter if it is connected or not.

Edit nr2:

I just talked to the support from where i ordered the motherboard, they are going to take it back for RMA (what they are going to look for i have no idea becous i've tried everything that has to do with software)So either it is hardware-faulty or just incompitable with the rig.

[SWRIG]

It looks like the driver is installed ok so that may not be the issue.

Have you got the latest BIOS ; 1801 is the latest stable , have you tried a bios reset/remove battery.

Are there any other cards in the system that could be interfering with the ethernet, could be worth trying a basic video card.

Try less/different RAM

Given that the driver is install ok then this is most likely a hardware issue; we don't sell ASUS motherboards but I've used Intel moterboards with the same chipset and ethernet controller without issue.

Sorry if you have tried all this; I've no idea how experienced you are with this kind of problem , nor do I know exactly what you have tried to be able to think of something you may not have tried.

Simon

[idata]

Thanks again for the tip.

But i have tried everything that is possible... Without any solution.

I went to the store i bought a new Motherboard - Asus P8 P67 B3 and now it works.I am using a Realtek Lan device now.

I have no idea what the problem was on my sabertooth board but as soon as I get a answer from the RMA, ill let you know.

[idata]

Works perfectly! Thanks Simon

Download Modified Driver: http://www.multiupload.com/Z9PW9L2ZEN http://www.multiupload.com/Z9PW9L2ZEN

[idata]

on w2008r2 use drivers LM and working but now

but I found that some services cause problems with certain conditions. LM card because the parameters are not perfectly equal to those of V. and for this reason, some services stop ras. inf should have corrected all of the parameters V

help

[idata]

Simon,

Thanks a lot!!!

I had same problem while installing windows sbs 2011 in a motherboard DH61BE which includes Ethernet Gigabit Intel® 82579V. I followed your instructions with a little difference:

1.- I used the drivers that came in the CD with the motherboard.

2.- The inf file that I modify was: /PRO1000/Winx64/NDIS62/e1c62x64.inf

3.- Here you can see lines after the modification, there are some differences in the Intel.NTamdXX.X.X because of win 7 64-bit and win server 2008 64-bit but basically the procedure is just the same that you already explained...

; e1c62x64.INF (Intel 64-bit extension Platform Only,

; Windows 7 64-bit extension and Windows Server 2008 R2 64-bit extension)

;

; Intel(R) Gigabit Network connections;******************************************************************************;

[Version]

Signature = "$Windows NT$"Class = NetClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}Provider = %Intel%CatalogFile = e1c62x64.catDriverVer = 10/28/2010,11.8.81.0

[Manufacturer]

%Intel% = Intel, NTamd64.6.1, NTamd64.6.1.1

[ControlFlags]

[Intel]

[Intel.NTamd64.6.1.1]

; DisplayName Section DeviceID; ----------- ------- --------%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_00011179%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&SUBSYS_00011179

[Intel.NTamd64.6.1]

; DisplayName Section DeviceID; ----------- ------- --------%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502%E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_00011179

%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503

%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&SUBSYS_00011179

Regards

Martin

[idata]

I've got alot of inputs to solve my problem from this tree. But the whole answer isn't here. The answers and tips is for older network adapters that I've got. So if you SBS 2011 installation still don't recognize your intel network adapter do like this.

Use the filetree and find elc62x64.inf. Open it with the texteditor.

Rightclick the unistalled network adpater in the devicelist and click the tab information.

(I only have swedish version so I don't know the english names)

Second option in that list give you the id's of your card and probably thos are missing in the file.

Third option gives you compatible id's that probably also is missing.

I took all of them and added in the file. Just to be shure that SBS2011 installation should find the driver. (I was pissed after trying 12 hours)

And vola, heureka it did. My complete (probably totally incorrect) working list looked like this.

; Intel(R) Gigabit Network connections

;******************************************************************************;

[Version]

Signature = "$Windows NT$"Class = NetClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}Provider = %Intel%CatalogFile = e1c62x64.catDriverVer = 10/28/2010,11.8.81.0

[Manufacturer]

%Intel% = Intel, NTamd64.6.1, NTamd64.6.1.1

[ControlFlags]

[Intel]

[Intel.NTamd64.6.1.1]

; DisplayName Section DeviceID; ----------- ------- --------%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_00011179%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&rev_05%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&cc_020000%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&cc_0200%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\cc_020000%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\cc_0200%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&SUBSYS_00011179%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&SUBSYS_849c1043&rev_05%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&SUBSYS_849c1043%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&cc_020000%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&cc_0200

[Intel.NTamd64.6.1]

; DisplayName Section DeviceID; ----------- ------- --------%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502%E1502NC.DeviceDesc% = E1502.6.1.1, PCI\VEN_8086&DEV_1502&SUBSYS_00011179%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&rev_05%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&cc_020000%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&cc_0200%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\cc_020000%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\cc_0200%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&SUBSYS_00011179%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&SUBSYS_849c1043&rev_05%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&SUBSYS_849c1043%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&cc_020000%E1503NC.DeviceDesc% = E1503.6.1.1, PCI\VEN_8086&DEV_1503&cc_0200

[idata]

Ups... I did it again... Sorry, I wanted to delete my first message, and as I can see this was the false step, because all the other messages were connected to it.

Someone had answered to my prays (OrangeWing: http://communities.intel.com http://communities.intel.com here it is once again

DRIVER Intel(R) 82579V Gigabit Network (Windows Server 2008 R2 + Windows Server SBS 2011)

http://dc195.4shared.com/download/JNkvfzJe/intel_r__82579v_gigabit_networ.rar?tsid=20120226-171945-e5f9f02d http://dc195.4shared.com/download/JNkvfzJe/intel_r__82579v_gigabit_networ.rar?tsid=20120226-171945-e5f9f02d

Unzip the file, and go to:

APPS/

SETUP/

SETUPBD/

Winx64/

SetupBD.exe (double click)

I'm terrible sorry, Orange Wings, and thanks again!

It works perfect...

[idata]

+1 for Simon's solution - you're a magician sir!

(Actually I took the gist of his post - the filenames are slightly different in the latest versions, but the crux is to add 1503 lines and remove the lines from Control).

[idata]

Thanks a lot! Poor intel - next board is surely without any intel chipset!!!

[schau13]

Hi Simon,

Do you think this driver will work on server 2012?

if not, would it be possible to modify it for server 2012?

[José_Andrés]

Hi I switched to Win 8.1 and my Intel 82579V GNC doesn't work properly. I download your latest PROWinx64.exe but the problem still there. After a sleep mode the card won't start unless I forced it manually.

I went through multiples forums and it shows clearly that Windows 8.1 manage Energy Efficient Ethernet connection. So, when my desktop goes in sleep mode, Win 8.1 set the Ethernet connection off. So far, everything's fine but when I wake up the system the device won't respond and keep resting in sleep mode. I must open again the devices manager to force it to open. I founded something yesterday that seems to operate properly. In the configuration board, I go to the Power Management Tab and modify the standard setup to delay the sleep mode to one hour. It seems to works…so far!

I'm not an expert but I can manage some average situations. Honestly, I must confessed this one took me some days to find even if I'm not really sure it's the right thing to do!

Please help.

[PStiv]

L.S.,

We have a similar problem with a DH77EB motherboard an the Intel 92579V NIC.

After an update to newer 64-bit LAN drivers we ran into the same problem.

After a restart the NIC device does not start.

When I disable and enable the NIC in Device Manager the device is working properly.

We tried a few versions of the driver. Our latest is 12.10.28.0 but no result.

Is there anybody familiar with this problem en how can we solve this.

Please advise,

Paul

[DFowl1]

Hi All,

Here is the thing, I have tried to do the same as discussed with altering the files for Server 2008 but for server 2012 R2 / Win 8.1 aka in the NDIS64 folder of the ver 19.5 version of the ProWinx64 driver package because the older drivers are no longer available. No go because the catalog checksum for the inf is now bad. i have to go and do a convoluted thing to disable and re-enable driver signing to get it to work as described here. http://www.systemcentercentral.com/win-2012-r2-nic-drivers-for-asus-p8z68-v-intel-82579-gig-card/ http://www.systemcentercentral.com/win-2012-r2-nic-drivers-for-asus-p8z68-v-intel-82579-gig-card/ Which now poses an issue with windows updates and so forth.

Sorry but this is now a bit of a whine at Intel.

I have been in the IT industry since 1993, worked with all sorts of servers and desktops and OSes and have ALWAYS punted Intel CPU and Chipset regardless of Mainboard brand as drivers are ALWAYS available and ALWAYS work especially with MS Windows before and after WHQL came into play. Now it seems to be changing. I am from and live in South Africa where IT things are NOT cheap! There are a few areas where Intel falls short in my books lately but primarily these two.

1. Blade Server Support - no sooner does one buy R500,000 (~US$250,000 current forex) worth of 1 x MFSYS25 and 1 x MFSYS25v2 Blade chassis and its been discontinued.

- sold with redundancy in mind, documentation and Indian call center support is lacking on installing and configuring any of the secondary storage and embedded Ethernet modules

2. Chipset driver support for Server OSes as discussed in this thread and other issues.

Here is the thing, Intel Management want to sell more Intel Servers, rack mount or otherwise, great!

Problem is this is decided directly by businesses NOT consumers. Businesses will go for the best bang for buck and if they are continuous customers (which Intel would want) they will stick with a brand they feel confident in where they know they will get support and spares from for years to come, hence DELL, HP, IBM and all the rest of your competitors are main stream in Server rooms and data centers alike. So, number 1, STOP discontinuing support and spares on some of your most expensive server products after just a couple of years from inception. You can still get drivers for the latest OSes and spares support on some HP Proliant server hardware which are more than 5 years old! THAT is what you are competing against and THAT is what is expected by businesses for their investment.

Consumers on the other hand can't afford to purchase server equipment so are forced to use cheaper desktop equipment instead. I am not talking about a 1 man show business needing some server for his business. I am talking about the guys and gals who need equipment to study and become IT technicians and the like, the people with the brains but not the R30,000 to fork out for a 10 day theory, 2 day practical coarse on windows hyper-v at some fancy institution for instance, but do have R5000,00 for a decent desktop box and Google, Technet and MSDN as their study guides. (These guys generally have the best training because they are motivating themselves to learn, have free reign to experiment and not limited to one point of view - IMO) So, they can't get Server software to work on desktop boards because of driver issues (i refuse to purchase anything HP/COMPAQ to this day because of this in my early days) but they get by. Now they have a job at big company X, move through the ranks quickly and now make the decisions on what is best to buy for the business. Intel Servers and Desktop solutions are cheaper but... Guess who will be trying to avoid dealing with "difficult" Intel and HP embedded drivers as much as possible and rather go with DELL?

Back to this topic: On top of all this you sell these "desktop consumer" chipsets to all and sundry OEMs such as ASUS, Gigabyte, etc. You put a disclaimer that the OEM must provide the correct drivers for the right operating system and that one must contact the OEM... Catch 22 if its an Intel Desktop Motherboard...

Here is the funny thing with Windows though: you have to qualify your drivers for Windows Workstations such as Windows 7, 8, 8.1 etc where the underlying hardware driver architecture is EXACTLY the same as their Server counterpart versions. You even go so far as to write binary files, catalogs and inf files with ALL the various bits and pieces in it then go and put an IGNORE statement to NOT load the correct drivers if the installer finds its a Server OS that it is running on. However with all the workarounds and hacking that happens to your "proprietary" files it can be made to work.

What gives? Again, you are not forcing businesses to purchase server hardware in this manner, you are forcing the future buying influence to instead shy away from Intel, 5 ~10 years from now Intel server sales drop even more and no one can figure out why... The name of the game is positive user experience no matter WHO it may be. Perhaps one day in America, some young collage persons (like Bill Gates/Steve Jobs clones) who want to study some intricate IT thing that would in theory revolutionise the Datacentre as we know it. They get together and find that the "network" they are trying to build and experiment with is only being hindered by these "cheap driver shots". Instead of fiddling with a hundred pcs (as they must re-install/ reconfigure for every experiment) they decide to sue the big corporation imposing the driver limitations for the money lost on the desktops, time, and costs involved for equivalent server hardware they would require to carry out their experiments. And what ever cost any tuition costs to boot.....and win. What would happen then?

Think about it a little, then change our customer experience to being the best again by going BACK to being the best and most stable chip and driver OEM. (P.S> give the person who came up with this idea and all management who approved it a big hard fat flat hand slap along side the ear to boot)

[IIosi]

Maybe is too late for my reply, but is possible install drivers for card Intel 82579V even in Windows Server 2012 R2 (my case) but i have tested it in Windows Server 2008 R2 as well...Hope it helps ppl that still try to find an answer to this.

Follow the below steps:

1. Download drivers from Intel. For all 82579 (Generic).:

https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=23773&lang=spa&OSVersion=Windows%20Server%202012*&DownloadType=Controladores https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=23773&lang=spa&OSVersion=Windows%20Server%202012*&DownloadType=Controladores

2. Uncompress it with Winrar or another and find "PRO1000" folder (in my case inside PROwinx64)

3. Device Manager (Windows) >> Other devices >> right click in Network Controller >> Update driver >> Browse my computer for driver... >> Let me pick from a list >> Network Controller >> use disk >> and find "PRO1000" folder.

4. Choose "...82579LM"

5. Accept warning.

6. Test connection

[AJors]

Though I won't want to recommend 3rd party driver finder tool, in your case, you don't know which driver to download and even don't know what to search for the driver, 3rd party utility is somehow an effortless and time-saving option. If you don't want to cost money on this, just try free software. Here I searched one for you: http://www.drivethelife.com/ DriveTheLife.

Just have a try, I won't promise it would work!