Windows has the concept of network location awareness (NLA), which means that you can configure a network as "public" (i.e. home/work), "private", etc..
What information does it use to "fingerprint" a network for this purpose?
Windows has the concept of network location awareness (NLA), which means that you can configure a network as "public" (i.e. home/work), "private", etc..
What information does it use to "fingerprint" a network for this purpose?
Source: http://msdn.microsoft.com/en-us/library/ms740558%28VS.85%29.aspx
See http://msdn.microsoft.com/en-us/library/aa480195.aspx
JR
Based on recent experimentation (with Server 2012, but I suspect earlier versions are similar) on non-domain, statically configured networks the NLA service uses the link-layer (MAC) address of the default gateway to identify the network.
The details are unclear, though I suppose they could be worked out with a network analyzer. If the configured default gateway does not respond, NLA does not recognize the network, so it's definitely doing some sort of query. (That is, you can't just put in a dummy gateway address, or even a dummy gateway address plus static arp entry; the gateway MAC address associated with a particular network must actually respond in order for NLA to decide that the adapter is connected to that network.)
See also my blog entry on a way of fooling Windows 2012 into assigning an adapter to a unique network.
If the adapter is assigned an address by DHCP, the logic might be different. I haven't looked into that yet. The logic on a domain network is documented as per the existing answers.