SOLVED! Server 2008 won't start with Network Discovery on for Local Network

[Ketchup]

Cliffs: Windows Server loses it's network settings whenever I reboot.
Resolution: Had to edit network list manager policies to allow access for my unidentified network.

Last weekend I was able to upgrade my home file/media server to some new hardware, and upgraded the OS from MS Server 2003 to Server 2008 (not R2).

It is doing fine as long as I don't reboot it. After applying Windows Updates to current, I assigned it an IP address and no default gateway. I don't want it on the Internet. Server 2003 says "no problem." Server 2008 says, "ok for now, but I will lose network discovery as soon as you reboot me."

OK. So I select "Enable NetBIOS over TCP/IP" but see the same behavior. I tried a few Services mentioned on the net, but none of them change the status.

Most of what I am reading over the net is folks who can't get network discovery to stay on. Mine stays on fine. It just loses my preferences as soon as I reboot it. If I switch it back to auto IP, we are back in business.

So, what am I missing when taking this off the Internet (which Server 2003 didn't seem to have a problem with)?

Thanks for any input.

 

[Ketchup]

Hmm, possibly this needs to go in Networking?

Maybe Server 2008 needs a fake default gateway for this to work. I have a headache already.

 

[imagoon]

What exactly is the problem again?

 

[Ketchup]

If I ever reboot my server, network discovery and file sharing turn off until I turn I log in directly and turn them back on again.

 

[imagoon]

What state does location awareness get set to when this happens? What happens if you set it to home? Is the firewall enabled?

 

[wangotango]

lol

 

[Ketchup]

Ah, thanks! You gave me my trigger word. It won't let me change it from unidentified network. This person has a similar issue:

http://social.technet.microsoft.com...-7-for-unidentified-network?forum=winserverPN

Doing some reading now.

 

[imagoon]

In local policy go in to the Network Location Awareness section and assign "Unidentified Networks" to "private." My guess that will fix your issue.

 

[Ketchup]

In local policy go in to the Network Location Awareness section and assign "Unidentified Networks" to "private." My guess that will fix your issue.

YUP! Thanks so much! I can see a reason there I suppose, but I think it's interesting that one has to jump through such hoops to make my server one that is, in my opinion, more secure.

To do this on your local server , follow these steps:

1. Start --> run --> MMC --> press enter

2. In MMC console , from menu file select Add/Remove Snap-in

3. Select Group Policy Object editor --> Press Add --> select Local computer --> press OK -->press OK

4. Open Computer configration -->Windows Settings -->Security Settings -->select Network list manager policies
on the right Side you will see options for :

double click -->Unidentified networks

Then you can select the option to consider the Unidentified networks as private and if user can change the
location.

 

[imagoon]

Yeah, the feature is actually a security tool. For those of us with laptops on work domains, it allows us to set the firewalls differently for domain vs public etc. Per best practice, MS fails to "public" which is locked down since it has no idea where it is.