A cluster node with two network cards does not receive messages (329492)



The information in this article applies to:

  • Microsoft Message Queuing 2.0

This article was previously published under Q329492

SYMPTOMS

If a Microsoft cluster node has more than one network adapter, Microsoft Message Queuing, also known as MSMQ, 2.0 may try to use the wrong network adapter.

CAUSE

This problem occurs when 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.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional 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, but it is only intended to correct the problem that is described in this article. Only apply it 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 Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: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 If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor 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:

HKEY_LOCAL_MACHINE\Software\Microsoft\MSMQ\Parameters\BindInterfaceIP.

This registry key can include the IP address that is named www.<xxx.yyy.zzz>. 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) 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 tool 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 "Applies to" section. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.

Modification Type:MinorLast Reviewed:10/5/2005
Keywords:kbWin2kSP4fix kbbug kbfix KB329492 kbAudDeveloper