Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Just found a fault with a server, other users have had problems connecting to it. The setting on the network card had changed from Private (domain) network to Public (the other option being Home).

The switch to the network interface would have caused the firewall to block a lot of normal functions.

I am guessing that since the event log showed no reason for the change that it might be due to a complete shutdown we had recently where someone powered up the machines, however the domain controllers might not have been booted up first. Any confirmation that this might be the case?

share|improve this question
up vote 1 down vote accepted

That is likely what happened. Because of the possibility that a given machine can connect to multiple different networks over the course of its life that share the same IP range, but are not the same network, Windows looks for other clues as to the identity of the network. That includes querying the DNS servers.

Now why MS thinks a SERVER would be doing that as opposed to a laptop is anyone's guess.

share|improve this answer
1  
You can set the network to always default to a specific type of network (i.e. Domain) and to not prompt. – Top__Hat Nov 22 '11 at 17:42
    
I must confess to hating that feature. – Matt Aug 18 '15 at 0:09

protected by Michael Hampton Aug 17 '15 at 23:33

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?

Not the answer you're looking for? Browse other questions tagged or ask your own question.