Microsoft KB Archive/328729

= Message Queuing 1.0 remote access server client cannot send transactional messages =

Article ID: 328729

Article Last Modified on 10/18/2005

-

APPLIES TO


 * Microsoft Message Queue Server 1.0

-



This article was previously published under Q328729



SYMPTOMS
When a Microsoft Message Queuing 1.0 client is connected through a remote access server, the Message Queuing 1.0 client cannot send transactional messages to other Message Queuing servers or Message Queuing clients.



CAUSE
This problem occurs because when the Message Queuing 1.0 client connects through a remote access server, it obtains its IP address through the remote access server. The IP address is not updated in Domain Name System (DNS), and the Message Queuing server lists the client's IP address as 0.0.0.0 in the Message Queue Server Information Store (MQIS) database as a remote access server client. When the Message Queuing 1.0 client tries to send messages, the server that sends an acknowledgment back does not receive the correct IP address of the remote access server client because it is not registered in DNS.



RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, 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:

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.

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 ---  23-Sep-2002  10:27  1.0.0.336          61,584  Mqac.sys 23-Sep-2002 10:27  1.0.0.336          34,064  Mqcertui.dll 23-Sep-2002 10:27  1.0.0.336          34,064  Mqdbmgr.dll 23-Sep-2002 10:27  1.0.0.336          59,152  Mqdscli.dll 23-Sep-2002 10:27  1.0.0.336          56,592  Mqdssrv.dll 23-Sep-2002 10:27  1.0.0.336         227,088  Mqis.dll 23-Sep-2002 10:27  1.0.0.336          16,144  Mqkeyhlp.dll 23-Sep-2002 10:27  1.0.0.336         142,096  Mqoa.dll 23-Sep-2002 10:27  1.0.0.336           8,464  Mqperf.dll 23-Sep-2002 10:27  1.0.0.336         509,712  Mqqm.dll 23-Sep-2002 10:27  1.0.0.336         110,352  Mqrt.dll 23-Sep-2002 10:45  1.0.0.336       1,831,320  Mqsetup.dll 23-Sep-2002 10:27  1.0.0.336          14,096  Mqsvc.exe 23-Sep-2002 10:27  1.0.0.336         106,768  Mqutil.dll 23-Sep-2002 10:27  1.0.0.336          62,224  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 of this article.



MORE INFORMATION
After you apply the hotfix, add the  registry key to the remote access server clients. Use the following information when you add the registry key:
 * Data Type: REG_DWORD
 * Value: 1

After you apply the hotfix and add the registry key, the remote access server client registers its IP address in MQIS when the Message Queuing service on the remote access server client is started and the client is connected through the remote access server.

Keywords: kbbug kbfix kbqfe kbhotfixserver KB328729

-

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

© Microsoft Corporation. All rights reserved.