Server 2016 Unidentified Network

Topic

New Reply

Hi,

Got a Server 2016 system, Standalone DC / DNS / DHCP.

It very often boots with “Unidentified network / Internet access” instead of Domain Network, which of course sets up the Public firewall profile, and wreaks havoc with file sharing and our applications.

Server is a Dell PowerEdge T330 with Broadcom NetXtreme Gigabit Ethernet dual NIC, NIC1 is in use & NIC2 is disabled in Device Manager.

All drivers are up to date. SFC and DISM scans are both clean. Network troubleshooter can’t find the problem. dcdiag & Dcdiag/test:DNS pass (although there are tons of event log entries as a result of the problem which I have to wade through). I did ipconfig/flushdns & ipconfig/registerdns.

Restarting the Network Location Awareness service ‘fixes” the problem, but I need to figure out why this is happening. NLA startup is Automatic. Should it be Delayed?

Can anyone help me troubleshoot the Unidentified Network issue?

Question: On TCP/IPv4 Properties / Advanced / DNS, is “DNS suffix for this connection” required for a DC?

Thanks in advance.

Reply | Quote

Replies

On a DC the domain is the suffix. There should be no need to add another suffix.

dbdan22 wrote:

I did ipconfig/flushdns & ipconfig/registerdns

A DC is the DNS for your domain and does not need to be flushed/registered.

Do you have more than one network card / virtual network?

Is the IP you use for the DC in your domain IP range?

Have you set the netmask correctly for both the network card and the DNS?

cheers, Paul

Reply | Quote

[dbdan22]

Hi,

Only 1 network card, with 2 ports NIC1 & NIC2. NIC1 is in use, NIC2 is disabled in device manager, as I stated. No virtual anything.

Yes, DC IP is in 192.168.1/24 range. Netmask is set correctly for the card. Not quite sure how netmask applies to DNS.

Regarding ipconfig/registerdns: one of the things I did in the process of troubleshooting this is disable and reenable NIC1. Big mistake, as everything went haywire. ipconfig/registerdns forces a DC to reregister its DNS records, which brought things back to its previous (semi broken) state… still “unidentified network” tho… until I restart the NLA service.

Thanks

• This reply was modified 4 years, 2 months ago by dbdan22.
• This reply was modified 4 years, 2 months ago by dbdan22.
• This reply was modified 4 years, 2 months ago by dbdan22.

Reply | Quote

Maybe it’s the second NIC not being disabled at startup?
Enable it and either let it find its own IP or give it a 10.10.10.x one.

cheers, Paul

Reply | Quote

No, the 2nd NIC is disabled. Always has been.

Reply | Quote