Control Network Interface Binding

Network interface binding determines which network interface (e.g., network card) Responder uses on the local machine (or in the cluster) to communicate with external Responder components. If you have multiple network interfaces, the network interface binding must be set for MSMQ .NET Remoting Channel, PubSub and Responder Events on each machine. The binding points to a particular network interface address. In most instances, all three of these will use the same network interface address.

This configuration is necessary if you have more than one network interface (including VMware virtual interfaces. If you have multiple network interfaces, there is a possibility that MSMQ may bind to the wrong interface and Responder components will not communicate with one another as expected. 

NOTE: Responder uses two different multicast communication protocols: MSMQ (aka PGM) and IP (aka UDP — User Datagram Protocol). You may see both of these protocols if you are monitoring your network.

This page discusses how to set up network interface binding for all three:

  • MSMQ .NET Remoting Channel

  • Responder PubSub (MSMQ Multicast)

  • Responder Events (IP Multicast) 

MSMQ .NET Remoting Channel

If MSMQ is binding to the wrong interface, Responder components will not be able to communicate. In this case, the user will not be able to open Responder Explorer. Follow the steps below to prevent this issue.

  1. Open the Registry and browse to the following location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters.
  2. Right-click Parameters and select New > String Value.
  3. Name this new value: BindInterfaceIP.
  4. Right-click the BindInterfaceIP key and select Modify.
  5. Type the IP address for the network interface to which MSMQ should bind.

     

    If you're working in a clustered environment, you will also need to set a registry key for each resource in the cluster. To do this, follow the steps outlined below.

  6. Open the Registry and browse to the following location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Clustered QMs\MSMQ$ResourceName\Parameters\. Replace $ResourceName with an MSMQ resource name.
  7. Just as you did in the previous steps, create a String Value named BindInterfaceIP and modify its value to be the network interface address to which MSMQ should bind.

Responder PubSub (MSMQ Multicast)

It is possible you may find that you’re not seeing Responder change events as expected. This most likely indicates that Responder PubSub is binding to the wrong interface. The following configurations will help correct this issue for Windows 7 and later.

Windows 7 and later

This configuration is only necessary if you meet all of the following criteria:

  • All Operating Systems later than Windows 7.

  • You have more than one network interface (including VMware virtual interfaces).

If you meet the criteria listed above, there is a possibility that MSMQ may bind to the wrong interface and you will not see Responder data change events as expected. To prevent this issue from occurring you will need to create the registry key discussed below. 

  1. Open the Registry and browse to the following location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters.

  2. Right-click Parameters and select New > DWORD Value.

  3. Name this new value: MulticastBindIP.

  4. Right-click the MulticastBindIP key and select Modify.

  5. Type the IP address for the network interface to which MSMQ should bind. This must be in a hexidecimal format.

For example: 172.18.224.11.

Decimal

Hex

172

AC

18

12

224

E0

11

0B

DWORD Value = AC12E00B

Responder Events (IP Multicast) 

If IP Multicast is using the wrong network interface, you will not see Responder events as expected. This means ArcMap won't refresh with updated data from Responder. To prevent this issue, you will need to set the network interface binding in the configuration files:

  • Miner.Responder.DataServices.exe.config

  • Miner.Responder.PredictionServices.exe.config

  • Miner.Responder.ArchiveServices.exe.config

The network interface binding must be set for each database configuration. In most instances all database configurations on a single machine will use the same binding IP address. To perform this configuration, follow the steps outlined below.

  1. Open Miner.Responder.DataServices.exe.config. By default, this file is installed here: C:\Program and Files (x86)\Miner and Miner\Responder\Server.
  2. Look for the following XML. It will appear in the <configuration> section for each database you have configured.
          <multicast group="239.254.000.027" port="6679" ttl="2" />
  3. Add to this line, the localInterface attribute with the network interface IP address as its value. For example:
          <multicast group="239.254.000.027" port="6679" ttl="2" localInterface="172.18.224.11" />
  4. Save and close Miner.Responder.DataServices.exe.config.
  5. Perform steps 1-3 for Miner.Responder.PredictionServices.exe.config and Miner.Responder.ArchiveServices.exe.config.
QR code for this page

Was this helpful?