Messages Sent with Direct=TCP May Be Rejected After IP Change on Target Computer

Article translations Article translations
Article ID: 271646 - View products that this article applies to.
This article was previously published under Q271646
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

A computer that is running Microsoft Message Queuing does not accept messages that are sent by using a Direct=TCP format name if the TCP/IP address has changed. This problem occurs most frequently when a computer connects to a network through Remote Access Service (RAS).

CAUSE

MSMQ binds to the available IP addresses on a computer when the service is started. The Message Queuing queue manager does not recognize IP addresses that change after the service is started. When a message is passed to the Message Queuing queue manager, the queue manager checks the target IP address in the message to determine if the queue manager recognizes that IP address. If the IP address is not known, the message is not accepted.

RESOLUTION

To resolve this problem, obtain the latest service pack for 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
Message Queuing no longer checks the known IP address table when a message that was sent by using a Direct=TCP format name arrives. Message Queuing assumes that the message belongs to the computer.

Message Queue Server 2.0

The English version of this fix should have the following file attributes or later:
   Date        Time    Version    Size     File name
   ----------------------------------------------------
   08/23/2000  11:44a  5.0.0.709  277,264  mq1repl.dll
   08/23/2000  11:44a  5.0.0.709  213,264  mqads.dll
   08/23/2000  11:44a  5.0.0.709   29,456  mqcertui.dll
   08/23/2000  11:44a  5.0.0.709   49,424  mqclus.dll
   08/23/2000  11:44a  5.0.0.709   29,968  mqdbodbc.dll
   08/23/2000  11:44a  5.0.0.709   75,536  mqdscli.dll
   08/23/2000  11:45a  5.0.0.709   41,232  mqdssrv.dll
   08/23/2000  11:45a  5.0.0.709  262,416  mqmigrat.dll
   08/23/2000  11:45a  5.0.0.709  223,504  mqoa.dll
   08/23/2000  11:45a  5.0.0.709    7,952  mqperf.dll
   08/23/2000  11:45a  5.0.0.709  409,872  mqqm.dll
   08/23/2000  11:45a  5.0.0.709    8,464  mqrperf.dll
   08/23/2000  11:45a  5.0.0.709   90,384  mqrt.dll
   08/23/2000  11:45a  5.0.0.709   69,392  mqsec.dll
   08/23/2000  11:45a  5.0.0.709  400,144  mqsnap.dll
   08/23/2000  11:45a  5.0.0.709   24,336  mqupgrd.dll
   08/23/2000  11:45a  5.0.0.709  107,792  mqutil.dll
   08/23/2000  11:45a  5.0.0.709   64,784  msmq.cpl
				

Message Queue Server 1.0

The English version of this fix should have the following file attributes or later:
   Date      Time    Version      Size    File name     Platform
   -------------------------------------------------------------
07/16/2000   07:43AM  310       227,088   mqis.dll     Windows NT4.0
07/16/2000   07:43AM  310       504,080   mqqm.dll     Windows NT4.0
07/16/2000   07:43AM  310       106,768   mqutil.dll   Windows NT4.0
				

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.

MORE INFORMATION

For additional information about how to install Windows 2000 and Windows 2000 hotfixes at the same time, click the article number below to view the article in the Microsoft Knowledge Base:
249149 Installing Microsoft Windows 2000 and Windows 2000 Hotfixes

Properties

Article ID: 271646 - Last Review: February 28, 2014 - Revision: 3.2
APPLIES TO
  • Microsoft Message Queue Server 1.0
  • Microsoft Message Queuing 2.0
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix kbqfe kbwin2000presp2fix KB271646

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com