Skip to main content

finding the right nic in server core

a recently deployed server, on windows 2008 server core, start kicking out some replication notifications which when checking the configuration did not seem to jive. i started poking around when i realized the horror: i don’t know where to find what i’m looking for!

long story short, the server suffered from a biological procedural failure to set the nic properly to the right speed. while the nic was set for auto, it was not set for the critical 1gb full auto. the question now is how was this determined, even though netsh is not helpful for this scenario? the answer is … the registry. <sigh>

 

finding the right interface guid

this is a fairly simple and probably routine thing for you if you’ve done any digging around. the idea is to find the nic with the right ip address associated to it. it’s difficult sometimes to do this when you have a server with four nics but only one enabled. this is a smart way to filter them out.

  • navigate to hklm\system\currentcontrolset\services\tcpip\parameters\interfaces.
  • under interfaces, you should find a set of guids which probably looking something like this example: {FD15E5DE-C7D1-4443-9045-3B1E0A884D0F}.
  • either open each one and look at the ipaddress value or just search at the root of services for the ip address.

image

  • when you have found the correct entry, copy the key name. (yes, copy the long guid :( … just right-click and copy key name then grab the guid)

 

finding the right nic to modify

now that you have the right interface guid, it’s time to find the right nic and poke around at setting the link speed correctly.

  • navigate to hklm\system\currentcontrolset\class.
  • there’s only one guid you need to look for here: {4D36E968-E325-11CE-BFC1-08002BE10318}. there’s probably lots of them.
  • search for the interface guid you found above. i would strongly recommend the “search” method i mentioned earlier, starting from the root of class.

you should find yourself at the appropriate area of the registry. most likely, you will see multiple keys named 0000 through something like 0006*. notice the guid you were looking for is the netcfginstanceid? now you’re in the right place to do yet more digging. :(

image

* or however many keys it takes to store the configuration per interface.

 

finding the right value for speedduplex

i mentioned earlier the server had the wrong setting. i was referring to the speed/duplex seen as *speedduplex in the registry. great. how do i know what to set that to? simple. you find the reference table.

  • navigate to hklm\system\currentcontrolset\control\class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0002\ndi\params\*speedduplex\enum.*
  • find the entry with the right description.
  • the name of the entry is the value to set for speed/duplex.

* the 0002 indicates that it might be a different interface number. remember, there’s one for every network configuration stored. yours might be 0003 or 0005 or whatever.

image

 

setting the speedduplex value

now that you have the right value, set the thing and go… :)

  • navigate to hklm\system\currentcontrolset\control\class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0002.
  • locate the value named *speedduplex and change the value to the value you located in the reference table above.

image

obviously you can use this for other settings as well. :) hope that helps.

 

references

http://blogs.technet.com/b/networking/archive/2009/01/08/configuring-advanced-network-card-settings-in-windows-server-2008-server-core.aspx

http://www.pctools.com/guides/registry/detail/269/

Comments

Popular posts from this blog

how to retrieve your ip address with powershell...

update: this is how it’s performed in powershell v3 as demonstrated here.(get-netadapter | get-netipaddress | ? addressfamily -eq'IPv4').ipaddress update: this is by far the easiest.PS C:\temp> (gwmi Win32_NetworkAdapterConfiguration | ? { $_.IPAddress -ne $null }).ipaddress
192.168.1.101
are you laughing yet?  i know you probably find this topic amusing.  it's really interesting though.  whenever you get over it, i'll do this in the standard cmd.exe interpreter and then in powershell to show you what kind of coolness powershell does.done?  okay, good.  this is an interpretation of a demo that bob wells did at our smug meeting.  hope you like it.i should tell you, it's not as simple as the title would lead you to believe.  i like doing that little slight-of-hand thing since it gives the impression that i'm painting a very easy target on my back for your criticism (though it's probably true in other ways)!  the idea is that we want to retrieve just the ip ad…

understanding the “ad op master is inconsistent” alert

i use the term “understanding” loosely.  this is by far no definitive guide on this particular alert, just a few things i have picked up in my attempt to understand it.let’s look at the context of the alert:The Domain Controller's Op Master is inconsitent. See additional alerts for details.
first of all, it gives very little information.  the only particularly useful detail is that it indicates which server is having the issue.  other than that, just a spelling error as there are no additional critical alerts to look at for details.this rule, as you know, comes from a sealed mp.  therefore, we can’t modify anything in it except the overrides.  the couple i’ve tinkered with are:interval (sec) log success event to begin with, interval (sec) is just set way too high.  the default is 60 seconds.  why on earth would anyone want to know that your op master consistency may be off, every minute?  actually, i could think of a few reasons, but really, it’s overkill.  the way the script works…

sccm: content hash fails to match

back in 2008, I wrote up a little thing about how distribution manager fails to send a package to a distribution point. even though a lot of what I wrote that for was the failure of packages to get delivered to child sites, the result was pretty much the same. when the client tries to run the advertisement with an old package, the result was a failure because of content mismatch.I went through an ordeal recently capturing these exact kinds of failures and corrected quite a number of problems with these packages. the resulting blog post is my effort to capture how these problems were resolved. if nothing else, it's a basic checklist of things you can use.DETECTIONstatus messagestake a look at your status messages. this has to be the easiest way to determine where these problems exist. unfortunately, it requires that a client is already experiencing problems. there are client logs you can examine as well such as cas, but I wasn't even sure I was going to have enough material to …