This tutorial will show you how to accept multicast traffic on a specific adapter. Windows NT doesn't allow for Multicast traffic on a multi-homed system on all adapters - only the first one to boot.  This is a problem for people who have applications that require multiple networks but need multicast on a specific network.  In my field of work, this happens in surveillance systems where many NVR/DVR providers multicast packet delivery to hosts.

The FASTEST way to get multicast traffic is to plug the Ethernet cable that will contain the multicast traffic into the first network adapter on your server.  This tutorial is going to show you how to switch the boot priority of the Ethernet without the need to be onsite, without having to modify the registry manually, without having to use RAS (Routing and Remote Access).

Open up your network connections. You should see something like this:
Quick Command: Start->Run->ncpa.cpl

Notice how my network named "Pelco" network was listed second. This is because someone plugged the cable into port 2 on the server. Unfortunately, Port 2 now is the adapter where multicast traffic will come from.

To change the boot priority so that the "Pelco" network boots first, click on that "Advanced" tool bar option. (I know, I never noticed it there before ether).

Click "Advanced Settings"

Now, Change the Adapter and Bindings - the top most item boots first, and next down the line boots next:

Now, I am not sure if its needed or not, but the boot priority seems like I would need to reboot it.  Maybe they don't call it "boot priority" but, that's how I look at it.  Once you reboot, you should now be getting Multi-cast traffic on that first adapter (well, 2nd adapter made to boot first).

Happy Multi-casting!