Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
WHS v1 lost access to network - "Media Disconnected" RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    A couple of days ago I couldn't get my machine to wake. Further investigation revealed it had carried out an automatic Windows update and hadn't booted up afterwards (this has happened before). Once I manually started it, it had no connection to my network. ipconfig shows "Media Disconnected".

    I have replaced the network cable, and checked / swapped switch ports. I uninstalled the network interface (on motherboard) from device manager, and did a hardware scan. Windows found the hardware, installed the drivers, but it just showed the same "Media Disconnected" when it came up again.

    I had a spare PCI Express network card, so I installed that. The drivers installed successfully, but it too shows "Media Disconnected". I disabled the internal NIC in the BIOS, but that didn't help the external one.

    I've had a look in the Event Viewer but I can't see anything which appears to be relevant (though that might just be my ignorance...)

    Based on info I've found elsewhere, I've also tried these:

    netsh int ip reset reset.log
    netsh winsock reset catalog

    ...but no joy. I'm now out of ideas, and I'd be very grateful for any suggestions!
    Sunday, July 17, 2011 10:01 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Yep, as mentioned above I've replaced the network cable and I also swapped the cable to a switch port that is working with another PC.

     

    Things have now moved on though, and I'm mighty confused.

    I just realised that I'd be able to finally work out if this was a hardware or software problem by booting a completely different OS on the machine. I've downloaded a Linux "system rescue" Live CD, burned it, and just booted from it in the machine.

    The NIC lights lit up, and it found my network with no problems, so I thought I'd established it as a software problem. I've now taken the CD out and rebooted from the installed WHS, and my network port is now working from that too!

    So, this problem is now an ex-problem, but I wish I understood why it went away!

     

    • Marked as answer by Rick Harnwell Sunday, July 17, 2011 10:48 PM
    Sunday, July 17, 2011 10:47 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Did you try a different cable just to check?  That's my first
    troubleshooting step.  They can go bad...
     
    Next is port on your switch \ router, changing it to a different
    connector..
     
     
    Bob Comer - Microsoft MVP Virtual Machine
    Sunday, July 17, 2011 10:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yep, as mentioned above I've replaced the network cable and I also swapped the cable to a switch port that is working with another PC.

     

    Things have now moved on though, and I'm mighty confused.

    I just realised that I'd be able to finally work out if this was a hardware or software problem by booting a completely different OS on the machine. I've downloaded a Linux "system rescue" Live CD, burned it, and just booted from it in the machine.

    The NIC lights lit up, and it found my network with no problems, so I thought I'd established it as a software problem. I've now taken the CD out and rebooted from the installed WHS, and my network port is now working from that too!

    So, this problem is now an ex-problem, but I wish I understood why it went away!

     

    • Marked as answer by Rick Harnwell Sunday, July 17, 2011 10:48 PM
    Sunday, July 17, 2011 10:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    >Yep, as mentioned above I've replaced the network cable and I also swapped the cable to a switch port that is working with another PC.
     
    Sorry about that, I had read it but forgot by the time I clicked
    respond.
     
    >So, this problem is now an ex-problem, but I wish I understood why it went away!
     
    Hard to tell, but at least it's "fixed".  I've seen a similar thing
    once or twice after an update on WinXP, but once you get it to work
    again, it hasn't happened to the same machines again.  Must be some
    kind of invalid stated in the OS's network stack.
     
    Bob Comer - Microsoft MVP Virtual Machine
    Sunday, July 17, 2011 11:20 PM