MulticastBindIP

[Markus Frank]

Hi!

I got some questions about multicasting and MSMQ.
We're using MSMQ on a Windows 2003 Server SP1 to distribute messages to
clients ( windows xp sp2 ) with multicast. Sometimes messages get lost and I
stumbled upon the registry value MulticstBindIP and a little article that
says that on hosts that are multihomed one of the network cards gets
randomly chosen to send Multicast-messages. In our server we have three
dfferent network cards but only 2 of them should recieve Multicast-messages
( I might accept only on of them reciveing messages ).

1. How can I configure multicast-messages to be sent on 2 out of 3
networkcard on a multihomed host?
2. In what format do I enter the IP-address?
3. I cannot find the MulticastBindIP registry value in the Windows 2003
server Registry Reference, how come?

[John Breakwell (MSFT)]

Are you referring to the TecxhNet article "IP multicasting"?
http://technet2.microsoft.com/WindowsServer/en/Library/ddd52c31-e288-4aa5-b144-516177a4f72c1033.mspx?mfr=true
This discusses setting a single IP address.

1 I don't think the registry value was designed for this purpose
2 xxx.xxx.xxx.xxx
3 The Registry Reference does not include any innovations during the
product lifetime. MulticastBindIP (and ClusterBindIP) must have been added
post-release.

I will add this to my list of registry values not in the Registry Reference:
http://blogs.msdn.com/johnbreakwell/archive/2007/02/14/tracking-down-msmq-registry-documentation.aspx

Cheers
John

"Markus Frank" <markus...@gabria.se> wrote in message
news:%23dQu$z7ZHH...@TK2MSFTNGP06.phx.gbl...

[Markus Frank]

Yes, I'm referring to that article. This article says that the IP-address
should be entered as a DWORD-value in the usual IP address format, what's
that format?

"John Breakwell (MSFT)" <Jo...@NoSpam.com> skrev i meddelandet
news:%23Qh1nk8...@TK2MSFTNGP04.phx.gbl...

[John Breakwell (MSFT)]

Ah, yes, of course - it would have to be a STRING value for you to type in
an IP address.
I'll get someone to fix the documentation.

Cheers
John Breakwell

"Markus Frank" <markus...@gabria.se> wrote in message

news:eKp$BGWaHH...@TK2MSFTNGP06.phx.gbl...

[Frank Boyne]

"Markus Frank" <markus...@gabria.se> wrote in message

news:eKp$BGWaHH...@TK2MSFTNGP06.phx.gbl...

> Yes, I'm referring to that article. This article says that the
> IP-address should be entered as a DWORD-value in the usual IP address
> format, what's that format?

An IPv4 address is a 32-bit integer. The dotted notation (e.g.,
192.16.1.20) is just a convention to make life easier for humans. The
integer isbroken down into four separate bytes, the contents of each
byte are expressed as a decimal value and the four decimal values are
written down separated by periods (most significant byte first).

In other words 192 = 0xC0 (this is the most significant byte)
16 = 0x10
1 = 0x01
20 = 0x14 (this is the least significant byte)

This would become the integer value 0xC0100114. You can also write a C
or C++ program to call the function inet_addr() to convert a string in
dotted notation into a long.

[John Breakwell (MSFT)]

Thanks for clarifying, Frank.

The article still needs fixing as the use of a DWORD is inconsistent with
other MSMQ registry values.
For example, BindInterfaceIP in KB 895867 uses a string.
So an example of how to set the value in the article would definitely help.

Cheers
John

"Frank Boyne" <frank...@unisys.com> wrote in message
news:OgsNysfa...@TK2MSFTNGP05.phx.gbl...