I blew a gasket and decided that there has to be a workaround. So I remembered that back in the day of the first plug & pray OS' that we used more the "Have disk" method of driver install. It's painful, but sometimes it works.
So from Server 2008 R2, I clicked on the unknown network device, and got to the menu that says "Let me pick from a list of device drivers on my computer" . Then you have to choose network adapter, and then 'have disk". This will point to your system32 folder. I pointed it to the Intel 18.8 CD. I knew the name of the adapters so I looked for them. I found the 82579LM. Installed the driver for that. And lo and behold, I suddenly had access to the local network.
So today I went to revisit Server 2012 and Server 2012 R2. I followed the same procedure and installed that driver on both network adapters. And it worked!!!
Of course windows did warn me that this driver was not written for my OS or hardware and did I want to put this driver on, and I did. I've used this method before to catastrophic results where the system either just plainly restarts or blue screens and then your OS is hosed. This was not the case today.
Server 2012 R2 with both network cards using the 82579LM drivers |
This entry is a follow-up of this blog post
Note despite the fact I wrote this on the first of April this is not a joke. This actually did work. [Hence the photo]
No comments:
Post a Comment
Thank-you for leaving a comment!