You Cannot Browse a Remote Access Client from the Message Queuing Service After You Establish the Connection (292812)


The information in this article applies to:

  • Microsoft Message Queuing 2.0
This article was previously published under Q292812

SYMPTOMS

You may experience the following symptoms:
  • If you try to look at the queues of a remote computer to which you are connected by using remote access, you receive the "Remote machine not available" error message.
  • If you try to read remotely from a computer that is running the Message Queuing service that has connected to the network through a remote access connection, you cannot do so successfully and you receive the "Remote machine not available" error message.

CAUSE

During the startup process, the Message Queuing service enumerates all of its IP addresses and binds a remote procedure call (RPC) listener to each one. If you are using remote access or if you acquire an IP address after the Message Queuing service is initialized, the service is not aware of the new address and it does not dynamically bind RPC listening ports to the new address.

The enumeration code that the Message Queuing service uses is needed only in a clustered environment to make sure that each node and that each virtual server binds only to its own addresses and not to everything on the computer. For a stand-alone computer, the enumeration is not needed.

RESOLUTION

The Message Queuing service now performs a bind to all addresses on non-clustered computers, which allows the Message Queuing service to accept data on any new addresses that are assigned after the initialization process.

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

The English version of this fix should have the following file attributes or later: 28-Feb-01 
   Date           Time  Version    Size       File name     
   -------------------------------------------------------
   28-Feb-01   18:54  5.0.0.720    273kb  Mq1repl.dll
   28-Feb-01   18:47  5.0.0.720     14kb  Mq1sync.dll
   28-Feb-01   18:47  5.0.0.733     70kb  Mqac.sys
   28-Feb-01   18:54  5.0.0.721    210kb  Mqads.dll
   28-Feb-01   18:47  5.0.0.720     22kb  Mqbkup.exe
   28-Feb-01   18:54  5.0.0.720     29kb  Mqcertui.dll
   28-Feb-01   18:54  5.0.0.720     49kb  Mqclus.dll
   28-Feb-01   18:54  5.0.0.720     30kb  Mqdbodbc.dll
   28-Feb-01   18:54  5.0.0.720     74kb  Mqdscli.dll
   28-Feb-01   18:54  5.0.0.720     41kb  Mqdssrv.dll
   28-Feb-01   18:47  5.0.0.720     96kb  Mqmig.exe
   28-Feb-01   18:54  5.0.0.720    258kb  Mqmigrat.dll
   28-Feb-01   18:54  5.0.0.720    219kb  Mqoa.dll
   28-Feb-01   18:54  5.0.0.720      8kb  Mqperf.dll
   16-Mar-01   18:33  5.0.0.734    406kb  Mqqm.dll
   28-Feb-01   18:54  5.0.0.720      9kb  Mqrperf.dll
   28-Feb-01   18:54  5.0.0.733     90kb  Mqrt.dll
   28-Feb-01   18:54  5.0.0.720     69kb  Mqsec.dll
   28-Feb-01   18:54  5.0.0.720    391kb  Mqsnap.dll
   28-Feb-01   18:48  5.0.0.720     14kb  Mqsvc.exe
   28-Feb-01   18:54  5.0.0.720     24kb  Mqupgrd.dll
   28-Feb-01   18:54  5.0.0.720    106kb  Mqutil.dll
   28-Feb-01   18:54  5.0.0.720     64kb  Msmq.cpl
   28-Feb-01   18:54  5.0.0.720    156kb  Msmqocm.dll

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 3.
Modification Type:MinorLast Reviewed:9/26/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix kbWin2000sp3fix KB292812
©2004 Microsoft Corporation. All rights reserved.