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, then 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.

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.

Open the Registry and browse to the following location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters.
Right-click Parameters and select New > String Value.
Name this new value: BindInterfaceIP.
Right-click the BindInterfaceIP key and select Modify.
Enter 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.

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.
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 data change events as expected. This most likely indicates that Responder PubSub is binding to the wrong interface. There are two different configurations to correct this issue, depending on the machine's operating system.

Windows 7 and later

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

You're using a Windows Operating System version later than XP (e.g., Windows 7, Windows Server 2003/2008)
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 occuring you will need to create the registry key discussed below.

Note that this registry key does not work properly under Windows XP. If you're using Windows XP, there are alternate steps below to control network interface binding.

Open the Registry and browse to the following location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSMQ\Parameters.
Right-click Parameters and select New > DWORD Value.
Name this new value: MulticastBindIP.
Right-click the MulticastBindIP key and select Modify.
Enter 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

Windows XP

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

You're using a Windows XP machine

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 occuring you will need to disable the extra network interfaces. If you're disabling a VMWare network interface, VMware will continue to work as it should.

Note that there is a registry key (discussed above) to control the network interface binding in MSMQ, but it does not work properly under Windows XP.

To disable the extra network interfaces, follow the steps outlined below.

In the Start Menu, go to My Network Places > View Network Connections.

Right-click the network interface and select Disable. In the example below, note the Status column. All extra network interfaces should be disabled.

Repeat this for all extra network interfaces.

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.

Open Miner.Responder.DataServices.exe.config. By default, this file is installed here: C:\Program and Files\Miner and Miner\Responder\Server.

Look for the following XML. It will appear in the <configuration> section for each database you have configured.
Copy Code
      <multicast group="239.254.000.027" port="6679" ttl="2" />
Add to this line, the localInterface attribute with the network interface IP address as its value. For example:
Copy Code
      <multicast group="239.254.000.027" port="6679" ttl="2" localInterface="172.18.224.11" />
Save and close Miner.Responder.DataServices.exe.config.

Perform steps 1-3 for Miner.Responder.PredictionServices.exe.config and Miner.Responder.ArchiveServices.exe.config.