Windows technical support
Podporni forum za uporabnike storitev spletnega gostovanja
This forum is part of windows webhosting service at www.hostmachine.net
 


Domain computer or AD server showing Public Network

To je neaktivna kopija originalnega foruma, prirejena za lazje indeksiranje z iskalnimi roboti.
Klikni tukaj za prehod na aktivni forum.
Click here to go to original active forum.


 
       Windows technical support Forum Index -> Windows server
View previous topic :: View next topic  
Author Message
Pico



Joined: 18 Jan 2004
Posts: 240
Location: HostMachine.net

Posted: 19.2.2020, 07:58    Post subject: Domain computer or AD server showing Public Network  

The problem is very annoying, sometimes all local domain computers and servers are on DOMAIN NETWORK just fine for few months, then all of the sudden some hiccup occurs and a Domain Controller, domain member, even SBS show PUBLIC NETWORK.
Browsing the network is not possible, quite some services go bad.

Causes?

If this happens after REBOOT, then most likely NLA service kicked-in before DNS could resolve, so it helps to restart NLA Network Location Awareness service.

Also very rarely documented, but very likely to happen is this problem on computers, which have MULTIPLE NIC NETWORK ADAPTERS, or MULTIPLE IP addresses setup on single NIC adapter.
In this case windows looks like enumerate NIC adapters by IP also, and when they enumerate by "primary" IP all works fine, network is Domain Network. But when they enumerate NIC adapter by "secondary" IP, then NLA detects conflict between Domain subnet and subnet of secondary IP and consequently sets network location to PUBLIC.
You can see this by entering route print, like in example below. You can see LAN subnet of domain is 192.168.0.0/24, but NIC adapter is identified by 2nd subnet 10.246.8.0/24, which generates conflict:
Code: >route print
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.0.1     10.246.8.242    266

Workaround is temporary removing 2nd IP address, and re-adding it back. Restart NLA Network Location Awarness service if necessary.
This should do maybe for a year!

At the time of writing I have no permanent solution for the problem.
Back to top  
 
       Windows technical support Forum Index -> Windows server
Page 1 of 1


Te strani so generirane samo za lazje indexiranje z iskalnimi roboti.
Prosimo, da uporabite povezavo na glavni forum, kjer lahko aktivno sodelujete s svojimi prispevki