Event ID 41036 — RRAS IGMP MGM Operation

Updated: December 16, 2008

Applies To: Windows Server 2008 R2

red

Internet Group Management Protocol (IGMP) maintains host group membership on a local subnet. Hosts use IGMP to communicate multicast group membership requests with their local multicast router. Routers receive the group membership requests and periodically send queries to determine which host groups are active or inactive on the local subnet. This protocol is required to support Level 2 multicasting. 

Event Details

Product: Windows Operating System
ID: 41036
Source: Microsoft-Windows-RasRoutingProtocols-IGMPv2
Version: 6.1
Symbolic Name: IGMPLOG_MGM_REGISTER_FAILED
Message: IGMP router failed to register with Multicast Group Manager (MGM). The data is the error code.

Resolve

Restart the remote access service

Registration with the internal application failed.

Possible resolutions:

  • Restart the remote access service.
  • Stop the remote access service, restart the computer, and then start the remote access service.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To restart the remote access 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).

Related Management Information

RRAS IGMP MGM Operation

Routing and Remote Access Service Infrastructure

Community Additions

ADD
Show: