none
Replaced onboard NIC with Gigabit NIC RRS feed

  • Question

  • I replaced the onboard NIC with an intel pro/1000 GT card.  I disabled the onboard NIC and assigned the oriiginal IP to the new NIC. After a reboot the new NIC works at full speed and server fully accessable (remote also).  After a time my server will be inaccessable on the network, restarting the server uses the new NIC again but continuous reboots are unacceptable.  What do I need to do to keep the server up and running on the new NIC? I am currently back on the old NIC so my server will be up 100% of the time.

     

    Thanks for any assistance.

    Thursday, July 17, 2008 7:17 PM

Answers

  • Disabling your onboard NIC shouldn't cause this issue. Since it's pretty easy to test, though, you could always turn it back on. Just don't reconnect it to your network. Smile

    Honestly, though, what you describe sounds like a network hardware or driver issue. Since it all worked with your onboard NIC, that takes everything except your new NIC out of the equation. Infantile failure isn't exactly unheard of in the industry...

    The only other thing that comes to mind is your motherboard. I haven't seen it, but I'm sure some manufacturer out there somewhere requires you to make configuration changes in the CMOS if you're not going to use the onboard NIC.
    Friday, July 18, 2008 1:32 AM
    Moderator
  • I disabled the onboard NIC in the BIOS, 24 hrs so far looks good. currently running a full 1.0gb network.

     

    Saturday, July 26, 2008 7:19 PM

All replies

  • Have you checked event logs on the server? It sounds like there's a problem with either the hardware or the driver; sometimes you'll get events that will point you in the correct direction. Also, have you installed any additional software or add-ins on your server? What about changes to the system configuration (other than those that you can make using the Windows Home Server console)?
    Thursday, July 17, 2008 8:16 PM
    Moderator
  • These are the only events I could find, but this has happened 4 times and only found these events once.

     

    Event Type: Warning
    Event Source: E1000
    Event Category: None
    Event ID: 27
    Date:  6/27/2008
    Time:  7:11:10 PM
    User:  N/A
    Computer:xxxxx
    Description:
    Intel(R) PRO/1000 GT Desktop Adapter Link has been disconnected.
    Data:
    0000: 00 00 04 00 02 00 54 00   ......T.
    0008: 00 00 00 00 1b 00 04 a0   ....... 
    0010: 00 00 00 00 00 00 00 00   ........
    0018: 00 00 00 00 00 00 00 00   ........
    0020: 00 00 00 00 00 00 00 00   ........
    0028: 1b 00 04 a0               ...    

    and then:

     

    Event Type: Information
    Event Source: Tcpip
    Event Category: None
    Event ID: 4202
    Date:  6/27/2008
    Time:  7:11:18 PM
    User:  N/A
    Computer: xxxx

    Description:
    The system detected that network adapter Intel(R) PRO/1000 GT Desktop Adapter was disconnected from the network, and the adapter's network configuration has been released. If the network adapter was not disconnected, this may indicate that it has malfunctioned. Please contact your vendor for updated drivers.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 00 00 00 00 02 00 50 00   ......P.
    0008: 00 00 00 00 6a 10 00 40   ....j..@
    0010: 02 00 00 00 00 00 00 00   ........
    0018: 00 00 00 00 00 00 00 00   ........
    0020: 00 00 00 00 00 00 00 00   ........

     

    Could this be because I only disabled the local area connetion to my motherboard NIC and enabled the new NIC'slocal internet connection?

    Thursday, July 17, 2008 10:27 PM
  • Disabling your onboard NIC shouldn't cause this issue. Since it's pretty easy to test, though, you could always turn it back on. Just don't reconnect it to your network. Smile

    Honestly, though, what you describe sounds like a network hardware or driver issue. Since it all worked with your onboard NIC, that takes everything except your new NIC out of the equation. Infantile failure isn't exactly unheard of in the industry...

    The only other thing that comes to mind is your motherboard. I haven't seen it, but I'm sure some manufacturer out there somewhere requires you to make configuration changes in the CMOS if you're not going to use the onboard NIC.
    Friday, July 18, 2008 1:32 AM
    Moderator
  • I'm using an Intel board DQ965GF with an onboard  82566DM nic. My network is all gigabit. All CAT5E or CAT6. Every 3-4 days the nic drops speed from 1Gb to 100. Disabling and re-enabling the nic gets it back to full speed, of course so does a reboot. This was noticed after updating the drivers to version 9.12.12.0 recently. I have a second nic in the machine, a Broadcom, also gigabit, and it's always running full speed, never had an issue. I'm going to roll back the Intel driver this weekend and see if this fixes it. I suspect it's a driver issue or the driver isn't too happy with PP1?
    Friday, July 18, 2008 4:23 AM
  • The driver and Power Pack 1 shouldn't have any problem coexisting. As far as I know, PP! made no changes to the network stack.

    If you can't get the Intel NIC working (and I think from what you say that it was the drivers you installed recently, so you should be able to) just drop back to the Broadcom NIC. It's just as fast.
    Friday, July 18, 2008 4:35 AM
    Moderator
  • Thanks, I agree.  My next step is to fully disable the NIC on the motherboad i'll see how that works.  Just wanted to see if I was missing something simple.  I'll post again with the result.

    Friday, July 18, 2008 2:33 PM
  • I disabled the onboard NIC in the BIOS, 24 hrs so far looks good. currently running a full 1.0gb network.

     

    Saturday, July 26, 2008 7:19 PM