MultiCast not receiving on machine with 2 network cards

[Kitog]

I have a Windows XP machine which has 2 Ethernet network cards. I am
sending a multiCast MSMQ message to the 234.1.1.1:80 address but it
isn't being picked up on any of the 3 MultiCast queues configured on
the machine.

The machine is not connected to a network and is configured to use a
workgroup.

The MultiCasting did work before on the machine but I don't know what
changed, other than a restart, to cause the problem.

I've used Wireshark to look at the PGM traffic and I can see the data
(ODATA) being sent on one adapter, however there is no PGM traffic on
the other network adapter. Also the message can be seen in the
outgoing queue for 234.1.1.1:80.

Any ideas on what the problem is or how I can debug this ?

Thanks,
CJ.

[John Breakwell (MSFT)]

Hi CJ,

Have you applied any hotfixes recently? The ability to send multicast
messages over 64kb was affected.
http://blogs.msdn.com/johnbreakwell/archive/2009/02/17/64kb-limit-on-the-size-of-msmq-multicast-messages.aspx

You may want to check this article to see if you need to set the
MulticastBindIP registry value.

IP multicasting
http://technet.microsoft.com/en-us/library/cc756156(WS.10).aspx
Multicast messaging with multiple network interface cards

Cheers
John Breakwell (MSFT)

"Kitog" <cjb...@gmail.com> wrote in message
news:6b350d08-9b0e-483d...@r24g2000yqd.googlegroups.com...

[Kitog]

On Jan 9, 4:52 pm, "John Breakwell \(MSFT\)" <J...@nospam.com> wrote:
> Hi CJ,
>
> Have you applied any hotfixes recently? The ability to send multicast

> messages over 64kb was affected.http://blogs.msdn.com/johnbreakwell/archive/2009/02/17/64kb-limit-on-...

>
> You may want to check this article to see if you need to set the
> MulticastBindIP registry value.
>

> IP multicastinghttp://technet.microsoft.com/en-us/library/cc756156(WS.10).aspx

> Multicast messaging with multiple network interface cards
>
> Cheers
> John Breakwell (MSFT)
>
> "Kitog" <cjb...@gmail.com> wrote in message
>
> news:6b350d08-9b0e-483d...@r24g2000yqd.googlegroups.com...
>
> >I have a Windows XP machine which has 2 Ethernet network cards. I am
> > sending a multiCast MSMQ message to the 234.1.1.1:80 address but it
> > isn't being picked up on any of the 3 MultiCast queues configured on
> > the machine.
>
> > The machine is not connected to a network and is configured to use a
> > workgroup.
>
> > The MultiCasting did work before on the machine but I don't know what
> > changed, other than a restart, to cause the problem.
>
> > I've used Wireshark to look at the PGM traffic and I can see the data
> > (ODATA) being sent on one adapter, however there is no PGM traffic on
> > the other network adapter. Also the message can be seen in the
> > outgoing queue for 234.1.1.1:80.
>
> > Any ideas on what the problem is or how I can debug this ?
>
> > Thanks,
> > CJ.

Thanks for the reply John,

I don't think that the size of the message is the problem as they are
very small (~500 Bytes).
I've read that article on setting MulticastBindIP and I've tried
setting it to the IP address of both network adapters but with no
luck. BTW, do you know if that MulticastBindIP registry setting should
a DWORD or string entry?

[John Breakwell]

Hi

You want to convert the IP address to Hex and put it in a DWORD.

How to put an IP address into a registry DWORD value
http://blogs.msdn.com/johnbreakwell/archive/2009/05/21/how-to-put-an-ip-address-into-a-registry-dword-value.aspx

Cheers
John Breakwell (MSFT)

"Kitog" <cjb...@gmail.com> wrote in message

news:89e1b0a7-fa6b-493d...@35g2000yqa.googlegroups.com...

[John Breakwell (MSFT)]

Hi Kitog,

Unfortunately, I've just discovered that MulticastBindIP is not present in
Windows XP.
Only Windows 2003 and above can use this registry value.
Currently I have no workarounds to recommend to make multicasting work as
you need it to.

You said in an earlier post:

"The MultiCasting did work before on the machine but I don't know what
changed, other than a restart, to cause the problem."

Is it possible that the network drivers were updated or some other change
that affected the order that the interfaces initialised?

Cheers
John Breakwell (MSFT)

"John Breakwell" <john...@msft.com> wrote in message
news:Om9gU4rk...@TK2MSFTNGP05.phx.gbl...

[John Breakwell]

Hi Kitog,

There is a workaround that I had missed in my haste ((Thanks, Paul)).
The registry value BindInterfaceIP (whiuch predates MulticastBindIP) exists
in Windows XP and is documented here:

A cluster node with two network cards does not receive messages
http://support.microsoft.com/kb/329492

Add the String and restart MSMQ to get Multicast traffic (in fact all MSMQ
traffic) associated with the chosen IP address.
Sorry for the confusion.

Cheers
John Breakwell (MSFT)

"John Breakwell (MSFT)" <Jo...@nospam.com> wrote in message
news:OI3xH6uk...@TK2MSFTNGP04.phx.gbl...