Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Other security for Windows, Mac, Linux
How would you protect a Local Primary Domain Controller
Message
<blockquote data-quote="Victor M" data-source="post: 1024283" data-attributes="member: 96560"><p>Hit a brick wall.</p><p></p><p>I am trying to implement Defender Firewall > Connection Security Rules on my trial version of Win Server.</p><p></p><p>On the workstation I have done this:</p><p>New Rule > Isolation > Request authentication for inbound and outbound connections > Computer (Kerberos VS) , all profiles checkmarked</p><p></p><p>On the Domain Controller I have done this:</p><p>New Rule > Isolation > Require authentication for inbound and outbound connections > Computer (Kerberos VS) , all profiles checkmarked</p><p></p><p>Both Win11 22H2 and Win10 22H2 workstations failed to connect to PDC, it says 'Unidentified Network', instead of 'MyDomain.box' when looking at the network adapter systray and gpupdate fails to connect to PDC.</p><p></p><p>When I remove the Connection Security Rule on the PDC, the client workstations can connect properly.</p><p></p><p>Network isolation for the PDC is important because it cuts connection to any PC which is not part of the domain.</p><p></p><p>Anyone have any ideas? Surely MS would have done regression testing and tested that this feature is working?</p><p></p><p>Before hastily testing this, I will ask that if this seems to work, then reboot the client workstation and see that it still works. The workstation fooled me by seemingly able to connect to the PDC right after I built the firewall rule but upon reboot it says Unidentified network because the server and the workstation are not connected to the gateway. And if it truly is working you should be able to do 'gpupdate' on the workstation after a reboot.</p></blockquote><p></p>
[QUOTE="Victor M, post: 1024283, member: 96560"] Hit a brick wall. I am trying to implement Defender Firewall > Connection Security Rules on my trial version of Win Server. On the workstation I have done this: New Rule > Isolation > Request authentication for inbound and outbound connections > Computer (Kerberos VS) , all profiles checkmarked On the Domain Controller I have done this: New Rule > Isolation > Require authentication for inbound and outbound connections > Computer (Kerberos VS) , all profiles checkmarked Both Win11 22H2 and Win10 22H2 workstations failed to connect to PDC, it says 'Unidentified Network', instead of 'MyDomain.box' when looking at the network adapter systray and gpupdate fails to connect to PDC. When I remove the Connection Security Rule on the PDC, the client workstations can connect properly. Network isolation for the PDC is important because it cuts connection to any PC which is not part of the domain. Anyone have any ideas? Surely MS would have done regression testing and tested that this feature is working? Before hastily testing this, I will ask that if this seems to work, then reboot the client workstation and see that it still works. The workstation fooled me by seemingly able to connect to the PDC right after I built the firewall rule but upon reboot it says Unidentified network because the server and the workstation are not connected to the gateway. And if it truly is working you should be able to do 'gpupdate' on the workstation after a reboot. [/QUOTE]
Insert quotes…
Verification
Post reply
Top