Got a customer that for whatever reason has two NIC's both residing on the same subnet and both have the same gateway defined (Yes, windows warns you about this but it does "work" for lack of a better term). They have this setup so OWA and other protocols coming from the inside can have one NIC while inside clients hit the other NIC. I'm not saying it's best practices and I'm not saying I'd configure it like that, but it is what it is.
The problem is that when the server boots, Network Location Awareness changes the profile from a "domain" to a "Private" network category and when it's private a lot of resources are cut off at the local firewall level (ie: RDP, Exchange features, HTTP, etc.) I've looked around and have messed with local policy, GPO's, etc. and cannot make this quit reverting to that private network. Any ideas aside from telling the customer that he's best to just use one NIC?
We are currently going to try disabling NLA altogether and see what happens. Any thoughts at all?
dt