We have a Server 2008 R2
Primary Domain Controller that seems to have amnesia when it comes to working out what kind of network it is on. The (only) network connection is identified at startup as a 'Public Network'.
Yet, if I disable and then re-enable the connection, it happily figures out that it is actually part of a domain network.
Is this because AD Domain Services is not started when the network location is initially worked out?
This issue causes some headaches with Windows Firewall Rules (which I am more than aware can be solved in other ways) so I am mostly just curious to see if anyone knows why this happens.