ASUS Z87 Motherboards Not Supported For Server OS???

Discussion in 'Intel MoBos' started by techSlave, Jul 9, 2013.

  1. techSlave

    techSlave [H]Lite

    Messages:
    74
    Joined:
    Feb 1, 2011
    I purchased an ASUS Z87-PLUS for use as a value server.

    Unfortunately, when installing Windows Server 2012 Essentials, the Intel I217 network controller is not supported. And no driver is available, either from ASUS or from Intel.

    Looking into the issue, I see that ASUS installs the Intel I217V chipset into Z87 motherboards, not the I217UM. And according to Intel, only the 'UM' chip is supported for server operating systems.

    see:http://www.intel.com/content/dam/ww...efs/ethernet-controller-i217-family-brief.pdf

    *sigh* Intel, ASUS, why do you shaft us so? The difference between these chips appears to be microscopic and artificial in order to 'segment' the market and force us server users into upscale (read: high profit-margin) equipment. Don't you guys understand yet that every time new equipment doesn't 'just work' like it should you're only hurting yourself??

    Will the I217V ever be supported by Windows Server 2012 or is it a fool's errand to wait for a proper driver to be released??

    Raja, can you please look into this and help explain why this is so and if there are any workarounds other than being forced into stupid solutions like installing an external NIC??
     
    Last edited: Jul 9, 2013
  2. Kardonxt

    Kardonxt 2[H]4U

    Messages:
    2,804
    Joined:
    Apr 13, 2009
    not to defend asus here but is this an ASUS only thing or are most / all Z87 mobos using the l217v?

    Seems like more of an intel charging more for an identical "server" product type deal. (Looking at you xeons)
     
  3. jkramp

    jkramp Limp Gawd

    Messages:
    179
    Joined:
    Dec 26, 2005
    ASUS will only be able to provide support when Intel does. This is an issue that should be directed toward Intel not the motherboard manufacturer.
     
  4. sKiDmArK

    sKiDmArK 2[H]4U

    Messages:
    2,625
    Joined:
    May 31, 2003
    I had a similar issue running WHS 2011 (basically Server 2008 R2) and a consumer motherboard that had a non-server NIC. I did the following trick to get it to work - not sure if it will work on Server 2012 with that specific NIC though:

    http://communities.intel.com/message/138286
     
  5. Raja@ASUS

    Raja@ASUS ASUS Community Support

    Messages:
    2,390
    Joined:
    Apr 18, 2011
    I've never ran a server OS on these boards and AFAIK support is not claimed by us for them either. Intel don't have such a driver so we can't provide one - I don't think Intel have any plans on that.
     
  6. SolidBladez

    SolidBladez [H]ardness Supreme

    Messages:
    6,272
    Joined:
    Jan 4, 2008
  7. PGHammer

    PGHammer 2[H]4U

    Messages:
    3,324
    Joined:
    Oct 8, 2002
    Have you considered using desktop Windows drivers (since there are no server-specific drivers)? And no - it's FAR from insane; remember, since Windows Vista (in fact, starting with Vista), the desktop and server flavors of Windows use a common code base. That means that desktop drivers will indeed work in Windows Server (Vista drivers for Server 2008, Windows 7 drivers for Server 2008 R2, and Windows 8 drivers for Server 2012). I have been using desktop motherboards (with and without integrated LAN) with the server flavors of Windows since *Windows Server 2003*.
     
  8. d50man

    d50man W[H]iskey Lover

    Messages:
    2,742
    Joined:
    Jan 22, 2002
    plop intel g-e nic and go
     
  9. sKiDmArK

    sKiDmArK 2[H]4U

    Messages:
    2,625
    Joined:
    May 31, 2003

    I didn't try that, but I could see it working. The workaround I linked works well enough though - if I ever need to reformat the server I'll give it a shot.
     
  10. JoeSchmoe007

    JoeSchmoe007 n00b

    Messages:
    29
    Joined:
    Sep 21, 2011
    Yes, this trick works with Z87-Plus and Windows Server 2012. I will post relevant files here later.
     
  11. mda

    mda [H]ard|Gawd

    Messages:
    1,411
    Joined:
    Mar 23, 2011
    As mentioned above, try using Win8 drivers for the Server 2012. Ran into similar issues with an ASUS Z77. Win8 drivers installed without issue.
     
  12. JoeSchmoe007

    JoeSchmoe007 n00b

    Messages:
    29
    Joined:
    Sep 21, 2011
    Win 8 drivers will not install without modifying .INF files - I tried.
     
  13. JoeSchmoe007

    JoeSchmoe007 n00b

    Messages:
    29
    Joined:
    Sep 21, 2011
  14. RottenMutt

    RottenMutt n00b

    Messages:
    16
    Joined:
    Apr 22, 2009
    This worked on a Gigabyte GA-Z87X-UD3H running WHS 2011 64 bit. I edited the W7 file and changed "E153B.6.2.1" to "E153B.6.1.1"

    works great, and thank you.
     
    Last edited: Aug 24, 2013
  15. Abula

    Abula Gawd

    Messages:
    932
    Joined:
    Oct 29, 2004
    Im also having issues with Intel I217V on GENE VI, it doesn't negotiate with my router/switch to a gigabit lan, im stuck at 100. if i force it it wont find a network, sad thing is with the intel nic on GENE IV i had no issues, its just with the new intel that im getting this problems (this is on windows 7 pro), extremely inconvenient in terms of transferring large files, something that i do frequently from my server.... i bet intel will work this out in time with newer drivers... but i don't have the time to wait, im just gona grab a Intel Gigabit CT PCI-E Network Adapter EXPI9301CTBLK, should be stable most server OSs
     
  16. RottenMutt

    RottenMutt n00b

    Messages:
    16
    Joined:
    Apr 22, 2009
    i would take the opportunity to upgrade my router/switch before buying a new network card. but it could be a bad Ethernet port on your MB.
     
  17. razorhard

    razorhard n00b

    Messages:
    1
    Joined:
    Sep 9, 2013
    would be great that you make a backup of these drivers and upload them to a ServerFile (Mega, MediaFire) I would greatly appreciate it! :D
     
  18. Squad-G

    Squad-G n00b

    Messages:
    1
    Joined:
    Sep 14, 2013
    I do not know if it's going to help someone, but I installed Windows Server 2008 R2 x64.

    Of crouse, it didn't work out of the box. I have the Z87X-D3H and it's coming with the NIC "Intel(R) Ethernet Connection I217-V". Intel doesn't provide any driver for this NIC card under a server OS from Windows, yo uneed the LM type NIC.
    The following link will enable the ability to use this NIC card under Windows Server 2008 R2 x64. Install as usual but be sure to disable the driver signature requirement before doing so.

    https://docs.google.com/file/d/0B7KYDK8tigidLUNQQkozZkxuRm8/edit?usp=sharing
     
  19. Justintoxicated

    Justintoxicated [H]ardForum Junkie

    Messages:
    13,953
    Joined:
    Apr 10, 2002
    Anyone know how to build a Server 2003 driver? I'm trying to use my Windows Home Server Restore CD but it does not seem to be able to use the onboard Lan to recover. I really don't want to have to go out and purchase an ethernet card just so I can restore my computer.

    So I need a server 2003 (WHS V1) driver just for recovery, I'm not even trying to install a server OS on this Motherboard. I'm pretty ticked at intel right now.

    Here is the pre-modified driver:
    http://nearlydeaf.com/?p=1145

    Can someone help me to modify the Win 2003 driver to work?

    Ok so I modified the e1c5123.inf as follows:

    [ControlFlags]
    ;ExcludeFromSelect = \
    ; PCI\VEN_8086&DEV_1502,\
    ; PCI\VEN_8086&DEV_1503

    [Intel]

    [Intel.NTx86.5.1]
    ; DisplayName Section DeviceID
    ; ----------- ------- --------
    %E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502
    %E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_00008086
    %E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_00011179
    %E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_00021179
    %E1503NC.DeviceDesc% = E1503, PCI\VEN_8086&DEV_1503
    %E1503NC.DeviceDesc% = E1503, PCI\VEN_8086&DEV_1503&SUBSYS_00008086
    %E1503NC.DeviceDesc% = E1503, PCI\VEN_8086&DEV_1503&SUBSYS_00011179
    %E1503NC.DeviceDesc% = E1503, PCI\VEN_8086&DEV_1503&SUBSYS_00021179


    [Intel.NTx86.5.1.1]
    ; DisplayName Section DeviceID
    ; ----------- ------- --------
    %E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502
    %E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_00008086
    %E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_00011179
    %E1502NC.DeviceDesc% = E1502, PCI\VEN_8086&DEV_1502&SUBSYS_00021179
    %E1503NC.DeviceDesc% = E1503, PCI\VEN_8086&DEV_1503
    %E1503NC.DeviceDesc% = E1503, PCI\VEN_8086&DEV_1503&SUBSYS_00008086
    %E1503NC.DeviceDesc% = E1503, PCI\VEN_8086&DEV_1503&SUBSYS_00011179
    %E1503NC.DeviceDesc% = E1503, PCI\VEN_8086&DEV_1503&SUBSYS_00021179

    WHS Restore CD says it locates the driver ont he USB drive but the card does not show up under network devices, so I still cannot recover my computer.
     
    Last edited: Dec 21, 2013
  20. JoeSchmoe007

    JoeSchmoe007 n00b

    Messages:
    29
    Joined:
    Sep 21, 2011
    The problem with that is that for Win 2003 you need Windows XP network driver for this card. The driver package I used in my other post (guide linked above) doesn't contain such driver - the oldest OS supported is Windows 7.
     
  21. Justintoxicated

    Justintoxicated [H]ardForum Junkie

    Messages:
    13,953
    Joined:
    Apr 10, 2002
    Yea I found a different driver pack that has the XP 2003 drivers. I just tried copying over the files I modified and WHS is not detecting those though. So I need to figure out which file WHS is detecting..

    The executable I'm using is:
    PRO2K3XP_32.exe

    System Path I end up modifying the files in is:
    H:\Installables\WHS Driver\PRO2K3XP_32\PRO1000\Win32\NDIS5x

    e1c5132.inf
    e1e5132.inf
    e1k5132.inf
    e1q5132.inf
    e1r5132.inf
    e1y5132.inf
    e1000nt5.inf
    e1000325.inf

    I tried modifying e1c5123.inf and also coppied over:

    e1c5123.cat
    e1c5123.din
    e1c5123.sys
    e1c5123.dll
    e1cmsg.dll

    ***oops looks like I missed:
    NicInstC.dll not sure if that is needed I'll reboot and try again.
    I'll add nicco2.dll too.

    If this does not work, then WHS must be reading in one of the other driver files.

    YOU SUCK INTEL THANKS ALOT!

    edit: Ok so adding that extra file worked. WHS detected the driver and said it found drivers for me devices. Unfortunately the network card does not show up in the list still (Even though it says it found the driver)... This driver pack must not contain the proper driver either.... I think I'm going to have to get a different motherboard that uses a cheaper more standard network card. Just wasted 6 hours of my life thanks intel, I will never buy another one of your network cards again.
    Meantime I'm stuck with this virus on here before I had even finished installing all the old apps from my previous install (thanks gf for that one), happy holidays indeed.

    Ok I'm recovered now, thanks to my old trust DFI Lanparty UT4 HTPC. It's now the only PC that will register with WHS out of the box. I gave up on my other HTPC, the drivers and card were detected but it kept shutting off the Ethernet jack right after detecting it :(
     
    Last edited: Dec 21, 2013
  22. dahlberg

    dahlberg n00b

    Messages:
    28
    Joined:
    Nov 3, 2013
    I am also having problem with the i217v on a z87 expert. It will not go higher than 100 Mb/s. Is it broken hardware?
     
  23. Abula

    Abula Gawd

    Messages:
    932
    Joined:
    Oct 29, 2004
    The problem with mine end up being the cable, not that its bad, simply its more picky, it runs fine on gigabit on another pc right next to it, so i just bought a new cable and its working fine, not what i wished, but it wasn't defective either.
     
  24. dahlberg

    dahlberg n00b

    Messages:
    28
    Joined:
    Nov 3, 2013
    I tried with a short cables and only the switch (GS105e) connected. No luck. Also tried a RVS4000 with same result. Will try new cable again.

    Built in cable test gives ok result both on NIC, GS105e and RVS 4000.
     
  25. dahlberg

    dahlberg n00b

    Messages:
    28
    Joined:
    Nov 3, 2013
    Solved the problem. It was a bad patch cable for me.