Event ID - 41030

Event Id41030
SourceMicrosoft-Windows-RasRoutingProtocols-IGMPv2
DescriptionIGMP could not set the IP header include option on the interface with IP address: %1. The data is the error code.
Event Information According to Microsoft :

Cause :

This event is logged when IGMP could not set the IP header include option on the interface with IP address.

Resolution :

Check TCP/IP settings, reinstall or re-enable IGMP, or restart Routing and Remote Access service

Possible resolutions:
  • Check whether there are any communication problems due to incorrect TCP/IP settings. Using administrator credentials, run the ipconfig command in a command prompt to view the TCP/IP configuration information. If TCP/IP configuration information is correct, then use the netstat -a command to show the status of all activity on TCP and UDP ports on the local computer.
  • Remove and reinstall IGMP. For more information, see the "Remove and Reinstall IGMP" section.
  • Dissable and enable the IGMP interface. For more information, see the "Disable and Enable IGMP" section.
  • Stop and restart the Routing and Remote Access service. For more information, see the "Restart the remote access service" section.
To perform these procedures, you must be a member of the Administrators group, or you must have been delegated the appropriate authority.

Remove and reinstall IGMP

To remove and reinstall IGMP:
  1. Open Routing and Remote Access. Click Start , click Run , type rrasmgmt.msc , and then press ENTER.
  2. In the console tree, expand IPv4 , right-click IGMP , and then click Delete .
  3. Click Yes in the confirmation dialog box.
  4. Under IPv4 , right-click General , and then click New Routing Protocol .
  5. Click IGMP Router and Proxy , and then click OK .
  6. Under IPv4 , right-click IGMP , and then click New Interface .
  7. Click the interface for IGMP, and then click OK .
  8. Modify the settings in the IGMP properties dialog box, and then click OK .
Disable and enable IGMP

To disable and enable IGMP:
  1. Open Routing and Remote Access. Click Start , click Run , type rrasmgmt.msc , and then press ENTER.
  2. In the console tree, expand IPv4 , and then click IGMP .
  3. In the details pane, right-click the interface you want to configure, and then click Properties .
  4. On the General tab, click Enable IGMP to clear the check box, and then click OK .
  5. Repeat steps 3 and 4 to enable IGMP.
Restart the remote access service

To restart the remote access service:service:
  1. Open Routing and Remote Access. Click Start , click Run , type rrasmgmt.msc , and then press ENTER.
  2. By default, the local computer is listed as a server. To add another server, in the console tree, right-click Server Status , and then click Add Server . In the Add Server dialog box, click the appropriate option, and then click OK .
  3. In the console tree, right-click the server you want to restart, click All Tasks , and then click Restart .
Verify :

You can verify multicast routing configuration with the mrinfo command. You can use the configuration information to aid in the troubleshooting of multicast forwarding and routing problems.

The mrinfo command queries a specified multicast router with an Internet Group Management Protocol (IGMP) message. The response to the query contains a version number, the list of interfaces and the neighbors on each interface, metrics, Time to Live (TTL) thresholds, and flags. The syntax of the mrinfo command is:

mrinfo [- n ] [ -i address ] [ - r retry_count ] [ - t timeout_count ] multicast_router
  • The - n option displays IP addresses in numeric format.
  • The - i option specifies the IP address of the interface from which you want to send the mrinfo query. By default, the interface from which to send the mrinfo query is determined by the IP routing table.
  • The - r option specifies the neighbor query retry limit. The default value is 3.
  • The - t option specifies how long, in seconds, mrinfo waits for a neighbor query reply. The default value is 4.
The following is an example of the mrinfo command:

C:\>mrinfo 10.1.0.1

10.1.0.1(test1.microsoft.com) [version 18.55,mtrace,snmp]:

10.1.0.1 -> 0.0.0.0 (local) [1/0/querier/leaf]

10.2.0.1 -> 10.2.0.2 (test2.microsoft.com) [1/0]

10.2.0.1 -> 10.2.0.3 (test3.microsoft.com) [1/0]

10.3.0.1 -> 0.0.0.0 (local) [1/0/querier/leaf]

In the preceding example, mrinfo is run against the multicast router at 10.1.0.1. The first line shows the multicast router configuration: version number (for servers running Routing and Remote Access, the version number reflects the build number of the operating system) and flags (mtrace and snmp supported).

Each additional line displays the interfaces on the multicast router and the neighbors on each interface. Interfaces 10.1.0.1 and 10.3.0.1 have no neighbors. Interface 10.2.0.1 has two neighbors, 10.2.0.2 and 10.2.0.3. For each line, mrinfo displays the interface and neighbor, the domain name for the neighbor, the multicast routing metric, the TTL threshold, and flags indicating its role on the network, such as the IGMP querier of the network (querier) or whether it has no neighbors (leaf).
Reference LinksEvent ID 41030 from Microsoft-Windows-RasRoutingProtocols-IGMPv2

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.
 Refresh