Share via

Windows Defender Firewall Connected to Public Instead of Domain

Henoch Setiadi 66 Reputation points
2023-07-05T00:16:08.0066667+00:00

Hi,

Suddenly our PC that Joined to a Domain has Incorrect Network Profile on Windows Defender Firewall:

User's image

--

But Connection Profile in Network Settings is Correct:

User's image

--

I also has tried to delay Network Location Awareness on Startup:User's image

This is happening Randomly and usually fixed when PC Rebooted after Issue happening.

Please be kindly advise, Thanks in advance.

Windows 10 Security
Windows 10 Security
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Security: The precautions taken to guard against crime, attack, sabotage, espionage, or another threat.
2,780 questions
Accepted answer
  1. Dave Patrick 426.2K Reputation points MVP
    2023-07-08T14:53:49.2066667+00:00

    Sorry we can't remove that DNS IP Address as it is recommended configuration by our ISP.

    You can add the ISP DNS as public forwarders but they cannot be on the connection properties of your domain controller or members. Public DNS servers know nothing of your domain.

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

3 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dave Patrick 426.2K Reputation points MVP
    2023-07-05T00:18:24+00:00

    I'd check the problem one has the ip address of domain controller listed for DNS and no others such as router or public DNS.

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

  2. Dave Patrick 426.2K Reputation points MVP
    2023-07-05T00:25:36.19+00:00

    Please run;

    Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log (run on PDC emulator)
    repadmin /showrepl >C:\repl.txt (run on any domain controller)
    ipconfig /all > C:\%computername%.txt (run on EVERY domain controller)
    ipconfig /all > C:\problemworkstation.txt (run on problem pc)

    Also check the domain controller System and Replication (DFS or FRS) event logs for errors since last boot. Post the Event Source and Event IDs of any found. (no evtx files)

    then put unzipped text files up on OneDrive and share a link.

  3. Dave Patrick 426.2K Reputation points MVP
    2023-07-05T14:37:10.45+00:00

    On SHILOH remove the public and unknown DNS addresses (122.144.1.1, 122.144.2.2, 8.8.8.8, 8.8.4.4) and replace with server's own static ip address (192.168.1.200) then do ipconfig /flushdns, ipconfig /registerdns, and restart the **netlogon service.

    On GPDIPTPC001 remove the public DNS from connection properties.

    If problems persist, then put up a new set of files to look at.

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