Event ID - 20175

Event Id20175
SourceRemoteAccess
DescriptionMulticast scope: %1 is non-convex (the shortest path between two nodes within the zone passes outside the zone) since border router: %2 appears to be outside.
Event Information According to Microsoft :

Cause :

This event is logged when multicast scope is non-convex (the shortest path between two nodes within the zone passes outside the zone) since border router appears to be outside.

Resolution :

Configure multicast scope, boundaries, or heartbeat

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

Follow the procedures in the order in which they appear until the problem is resolved.

Configure multicast scopes

To configure multicast scopes:

A scope is a range of IP multicast addresses and is defined by specifying the address range as an IP address and mask. Multicast addresses in the range of 239.0.0.0 to 239.255.255.255 (239.0.0.0/8) are used to specify administrative scopes, as defined in RFC 2365. However, the range of 239.255.0.0/16 is defined as a local scope and cannot be divided further.
  1. Open Routing and Remote Access. Click Start , click Run , type rrasmgmt.msc , and then press ENTER.
  2. In the console tree, double-click the server name.
  3. Double-click IPv4 , right-click General , and then click Properties .
  4. On the Multicast Scopes tab, click a multicast scope, and then click Edit .
  5. Review the settings, and then add or delete the scope, as appropriate.
Configure multicast boundaries

To configure multicast boundaries:

Multicast boundaries are administrative barriers that can be configured to limit how far routers can forward multicast traffic across a network. Without boundaries, a multicast router forwards all multicast traffic throughout the network. With boundaries, a multicast router forwards multicast traffic over a limited area of the network only.
  1. Open Routing and Remote Access. Click Start , click Run , type rrasmgmt.msc , and then press ENTER.
  2. In the console tree, double-click the server name.
  3. Double-click IPv4 ,and then click General .
  4. In the details pane, right-click the interface on which you want to configure multicast boundaries, and then click Properties .
  5. On the Multicast Boundaries tab, review the scope boundary settings.
Note : Only scopes configured as multicast scopes are listed in Scope .

Configure multicast heartbeat

To configure multicast heartbeat:

Multicast heartbeat is the ability of a server running Routing and Remote Access to listen for a regular multicast notification to a specified group address to verify that IP multicast connectivity is available on the network. If the heartbeat is not received within a configured amount of time, the server running Routing and Remote Access sets the multicast heartbeat status of the configured interface to inactive.
  1. Open Routing and Remote Access. Click Start , click Run , type rrasmgmt.msc , and then press ENTER.
  2. In the console tree, double-click the server name.
  3. Double-click IPv4 ,and then click General .
  4. In the details pane, right-click the interface on which you want to configure multicast boundaries, and then click Properties .
  5. On the Multicast Heartbeat tab, select the Enable multicast heartbeat detection check box.
  6. Add a multicast heartbeat group, and configure a quiet time.
Verify :

To verify that multicast traffic is being forwarded to the multicast group address, on a receiving host, open a multicast-enabled application and verify streaming content is being received.
Reference LinksEvent ID 20175 from RemoteAccess

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