Microsoft KB Archive/329492

= A cluster node with two network cards does not receive messages =

Article ID: 329492

Article Last Modified on 8/17/2007

-

APPLIES TO


 * Microsoft Message Queuing 3.0
 * Microsoft Message Queuing 2.0

-



This article was previously published under Q329492



Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
If a Microsoft cluster node has more than one network adapter, Microsoft Message Queuing 3.0 or Message Queuing 2.0 may try to use the wrong network adapter.



CAUSE
This problem occurs when Message Queuing 3.0 or Message Queuing 2.0 uses the first IP address that it establishes from a call to the GetHostByName network API. This is not necessarily the correct IP address.



Message Queuing 3.0
To resolve this problem in Message Queuing 3.0, you must add the following registry key as a string value:

This registry value tells Message Queuing 3.0 the IP address to use.

You must also add the following registry key as a string value to tell the MSMQ clustered resource which IP address to use:

This registry value tells Message Queuing clustering resource the IP address to use. This registry value can include the IP address that is named www.. If this key is present, Message Queuing 3.0 binds only to this address to send and receive messages.

Service pack information
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to obtain the latest Windows 2000 service pack

Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

You must add the following registry key as a string value to tell Message Queuing 2.0 which IP address to use:

This registry key can include the IP address that is named www.. If this key is present, Message Queuing 2.0 binds only to this address to send and to receive messages.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.   Date         Time   Version            Size    File Name --  21-Oct-2002  20:31  5.0.0.759         280,336  Mq1repl.dll 21-Oct-2002 19:38  5.0.0.759          14,096  Mq1sync.exe 27-Aug-2002 22:54  5.0.0.756          74,832  Mqac.sys 21-Oct-2002 20:31  5.0.0.757         215,312  Mqads.dll 27-Aug-2002 01:35  5.0.0.756          21,776  Mqbkup.exe 21-Oct-2002 20:31  5.0.0.750          76,560  Mqdscli.dll 21-Oct-2002 20:31  5.0.0.735          41,744  Mqdssrv.dll 21-Oct-2002 19:38  5.0.0.759          98,064  Mqmig.exe 21-Oct-2002 20:31  5.0.0.759         265,488  Mqmigrat.dll 21-Oct-2002 20:31  5.0.0.740         222,480  Mqoa.dll 21-Oct-2002 20:31  5.0.0.748           8,976  Mqperf.dll 21-Oct-2002 20:31  5.0.0.758         424,208  Mqqm.dll 21-Oct-2002 20:31  5.0.0.756         102,672  Mqrt.dll 21-Oct-2002 20:31  5.0.0.759          70,928  Mqsec.dll 21-Oct-2002 20:31  5.0.0.756          23,824  Mqupgrd.dll 21-Oct-2002 20:31  5.0.0.756         110,352  Mqutil.dll 21-Oct-2002 20:31  5.0.0.748          64,784  Msmq.cpl



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

Message Queuing 2.0
This problem was first corrected in Microsoft Windows 2000 Service Pack 4.

Additional query words: MSMQ

Keywords: kbwin2ksp4fix kbbug kbfix KB329492

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.