Share via

Non-identified network

Andrea Vironda 816 Reputation points
2021-01-24T07:32:50.813+00:00

Hi,
in my WS2012 I notice i have this message above the little network icon
59832-image.png

This is my static IP configuration: 59917-image.png

Is it possible the problem is DNS configuration? I make it pointing to himself because my server has also the DNS configured

Windows Server 2012
Windows Server 2012
A Microsoft server operating system that supports enterprise-level management, data storage, applications, and communications.
1,538 questions
0 comments
Accepted answer
  1. Gloria Gu 3,891 Reputation points
    2021-01-25T02:36:56.643+00:00

    Hi,

    Thank you for posting in Q&A!

    Can the server can access the internet?

    According to our experience, Primary DNS should be address of local DNS server and then use 127.0.0.1 as secondary.

    What's more, please try to editing the properties of NIC. Please put in your domain information in the "DNS suffix for this connection".

    59976-12.png

    Hope you have a nice day : )
    Gloria

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
    https://learn.microsoft.com/en-us/answers/articles/67444/email-notifications.html

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dave Patrick 426.2K Reputation points MVP
    2021-01-24T13:39:35.81+00:00

    Assuming a domain controller? If so also add the server's own ip address (192.168.1.8) listed for DNS in addition to loopback. If a single DC also try restarting the Network Location Awareness service.

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments
  2. Dave Patrick 426.2K Reputation points MVP
    2021-02-01T13:45:20.217+00:00

    it's not a domain controller, I only use it in a WORKGROUP environment

    Regardless if the server runs the DNS role then also add the server's own ip address (192.168.1.8) listed for DNS in addition to loopback. If a single DNS server also try restarting the Network Location Awareness service.

    --please don't forget to Accept as answer if the reply is helpful--