gerbargains.blogg.se

I just now got the MMC crash on the other machine. How can I track this down and fix it so I can remotely manage the server's firewall? No relevant event log entries are produced there. When I try this from another machine on the network, MMC doesn't crash-but the Inbound/Outbound rule lists stay empty. The Windows Defender Firewall Remote Management rules are enabled: Name : RemoteFwAdmin-In-TCP DisplayName : Windows Defender Firewall Remote Management (RPC) Description : Inbound rule for the Windows Defender Firewall to be remotely managed via RPC/TCP.

and here's the Application event log entry:Īs expected, the Security and Maintenance control panel is useless for this. Object reference not set to an instance of an object.Īt .FirewallRules.Reload(String ruleIdFilter)Īt .Refresh()Īt .EnhancedMmcListView`1.ForceRefresh()Īt .EnhancedMmcListView`1.OnShow()Īt (Notification notification)Īt (Notification notification)Īt .ProcessNotification(Notification notification)Īt .ProcessNotification()Īt .OnThreadTransfer(SimpleOperationCallback callback) Not that it helps much, but here's the stack trace info: FX: However, when I click the Inbound Rules node, MMC crashes: (65536)ĭisplayName : Windows Defender Firewall Remote Management (RPC-EPMAP)ĭescription : Inbound rule for the RPCSS service to allow RPC/TCP traffic for the Windows Defender Firewall. Steps At the Windows Server Core command prompt, enter the following command: netsh advfirewall firewall set rule groupRemote Administration new enableyes. Status : The rule was parsed successfully from the store.

The Windows Defender Firewall Remote Management rules are enabled: Name : RemoteFwAdmin-In-TCPĭisplayName : Windows Defender Firewall Remote Management (RPC)ĭescription : Inbound rule for the Windows Defender Firewall to be remotely managed via RPC/TCP.ĭisplayGroup : Windows Defender Firewall Remote Management Using MMC, I'm attempting to remotely manage the Windows Defender Firewall on our Hyper-V Server 2019 instance (no GUI, CLI only).