WEC won't forward events to self if WinRM GPO doesn't include IPv6 filter

[ghost]

My WEC is installed on Server 2016, for reference.

Problem:

Without the IPv6 Filter enabled on this GPO

Computer Configuration -> Administrative Templates -> Windows Components -> Windows Remote Management (WinRM)/WinRM Service:
Allow Remote Server Management through WinRM: Enabled
IPV4 filter: *

The Windows Event Collector won't forward events to itself. You will see event ID 105 in the event channel Microsoft-Windows-Eventlog-ForwardingPlugin/Operational with the message:

The forwarder is having a problem communicating with subscription manager at address http://<server name>:5985/wsman/SubscriptionManager/WEC. Error code is 2150859027 and Error Message is The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Management protocol.

Cause:

This is due to the fact that when a Windows machine looks itself up local DNS records are used (instead of your DNS server records) which returns the IPv6 address ::1 for localhost. This is still true even when IPv6 networking is disabled.

You can ping your WEC FQDN from the localhost and see:
Reply from ::1: time<1ms

Then run winrm e winrm/config/listener and see:

Listener
    Address = *
    Transport = HTTP
    Port = 5985
    Hostname
    Enabled = true
    URLPrefix = wsman
    CertificateThumbprint
    ListeningOn = 127.0.0.1, 192.168.100.100

WinRM isn't listening on an IPv6 interface.

Solution:

Enable the IPv6 filter in the previously mentioned GPO.

[hilltechde]

Hello,

it would seem I am encountering the same issue. However, the IPv6 filter was actually enabled. As there is not v6 routed at my client's in general, I have thus turned the filter off, however also to no avail.

Anyone else out there with the same problem?

[Bit-Bot-B]

Hello Guys,

we have the same problem we disabled the IPV6 Protocol and enabled it again but we still have the same Issue.

The ::1 is by us present when we disable IPV6, also when we have it enabled.

I see the computer needs a windows update maybe it will solve the Problem after this update.

Windows Upadetes are in now.

Still same issue

[Bit-Bot-B]

We solved it with this Articel:

the importent thing was in our case:

Step 3: Perform the following steps on the ATA Gateway (the normal Windows Server as WEF)
Open an elevated command prompt and type wecutil qc

Here is the hole Documentation

https://docs.microsoft.com/en-us/advanced-threat-analytics/configure-event-collection
Configuring Windows Event Forwarding
Article
12/26/2021
2 minutes to read
14 contributors

Applies to: Advanced Threat Analytics version 1.9

Note

For ATA versions 1.8 and higher, event collection configuration is no longer necessary for ATA Lightweight Gateways. The ATA Lightweight Gateway now read events locally, without the need to configure event forwarding.

To enhance detection capabilities, ATA needs the following Windows events: 4776, 4732, 4733, 4728, 4729, 4756, 4757, 7045. These can either be read automatically by the ATA Lightweight Gateway or in case the ATA Lightweight Gateway is not deployed, it can be forwarded to the ATA Gateway in one of two ways, by configuring the ATA Gateway to listen for SIEM events or by configuring Windows Event Forwarding.

Note

If you are using Server Core, wecutil can be used to create and manage subscriptions to events that are forwarded from remote computers.

WEF configuration for ATA Gateway's with port mirroring
After configuring port mirroring from the domain controllers to the ATA Gateway, use the following instructions to configure Windows Event forwarding using Source Initiated configuration. This is one way to configure Windows Event forwarding.

Step 1: Add the network service account to the domain Event Log Readers Group.

In this scenario, assume that the ATA Gateway is a member of the domain.

Open Active Directory Users and Computers, navigate to the BuiltIn folder and double-click Event Log Readers.
Select Members.
If Network Service is not listed, click Add, type Network Service in the Enter the object names to select field. Then click Check Names and click OK twice.
After adding the Network Service to the Event Log Readers group, reboot the domain controllers for the change to take effect.

Step 2: Create a policy on the domain controllers to set the Configure target Subscription Manager setting.

Note

You can create a group policy for these settings and apply the group policy to each domain controller monitored by the ATA Gateway. The steps below modify the local policy of the domain controller.

Run the following command on each domain controller: winrm quickconfig

From a command prompt type gpedit.msc.

Expand Computer Configuration > Administrative Templates > Windows Components > Event Forwarding

Local policy group editor image.

Double-click Configure target Subscription Manager.

Select Enabled.

Under Options, click Show.

Under SubscriptionManagers, enter the following value and click OK: Server=http://:5985/wsman/SubscriptionManager/WEC,Refresh=10

(For example: Server=http://atagateway9.contoso.com:5985/wsman/SubscriptionManager/WEC,Refresh=10)

Configure target subscription image.

Click OK.

From an elevated command prompt type gpupdate /force.

Step 3: Perform the following steps on the ATA Gateway

Open an elevated command prompt and type wecutil qc

Open Event Viewer.

Right-click Subscriptions and select Create Subscription.

Enter a name and description for the subscription.

For Destination Log, confirm that Forwarded Events is selected. For ATA to read the events, the destination log must be Forwarded Events.

Select Source computer initiated and click Select Computers Groups.

Click Add Domain Computer.
Enter the name of the domain controller in the Enter the object name to select field. Then click Check Names and click OK.
Event Viewer image.
Click OK.
Click Select Events.

Click By log and select Security.
In the Includes/Excludes Event ID field type the event number and click OK. For example, type 4776, like in the following sample.
Query filter image.

Right-click the created subscription and select Runtime Status to see if there are any issues with the status.

After a few minutes, check to see that the events you set to be forwarded is showing up in the Forwarded Events on the ATA Gateway.

For more information, see: Configure the computers to forward and collect events