Home → Supercharger KB → Getting Started → Troubleshooting a Problem Forwarder
2.7. Troubleshooting a Problem Forwarder
Problem: A computer shows up in the Current Forwarders tab for your subscription but is shown as None in the WEC column.
This means that your subscription’s policy’s health assessment basis is Deterministic and that the group(s) you’ve assigned in Allowed Forwarders include this computer as a member. Therefore we expect it to be forwarding events. Yet, WEC has never seen that computer for this subscription and therefore Supercharger reports Absent.
Here are the possible reasons why, with tips on how to investigate
Category |
Problem |
Action on Forwarder |
---|---|---|
Collector targeting |
Forwarder is not targeted at collector |
Run a Group Policy Results report for that computer
|
Collector string for “Configure target subscription manager” is incorrect |
Are other computers successfully targeting this collector via the same group policy object? Check Microsoft-Windows-Forwarding/Operational (Microsoft-Windows-Eventlog-ForwardingPlugin/Operational) on forwarder for errors (see below) |
|
Group policy recently updated and forwarder has not applied or GPO has not replicated |
Run gpupdate on forwarder and verify with Group Policy Results report “GPRESULT /H GPReport.html” and check “Configure target subscription manager” |
|
Connectivity |
Connectivity problem |
Use this command with the DNS name in your collector string “winrm identify -r:http://winrm_server:5985” (or “winrm identify -r:https://winrm_server:5986”) |
WinRM on Forwarder |
Check these event logs for errors:
|
Event ID 102 with error 5004 can mean
Event ID 105 with error 2150859027 with full message "The forwarder is having a problem communicating with subscription manager at address http://COLLECTOR:5985/wsman/SubscriptionManager/WEC. Error code is 2150859027 and Error Message is <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859027" Machine="FORWARDER"><f:Message>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. </f:Message></f:WSManFault>.
|
WinRM service not running on forwarder |
||
WinRM has not been configured on forwarder |
Run “winrm qc” |
|
Collector |
Collector side problem |
Check following logs
|
WinRM issue on Collector |
Run "winrm get winrm/config". In the results of this cmd is "AllowRemoteAccess = true". Check HKLM\Software\Policies\Microsoft\Windows\WinRM\Service
|
|
Active Directory |
Computer was recently added/removed from group and Supercharger collector and source computer are talking to different domain controllers |
Force replication between domain controller if practical |
Computer has not been rebooted since being added to the group |
Reboot or Run this command on the forwarder: klist -lh 0 -li 0x3e4 purge This purges the Kerberos ticket cache and the computer will pick up the new group when it obtains a new ticket. See this article for steps to perform this. |