MSMQ: Messages That Are Sent By Using the Direct=TCP Syntax Are Rejected (306416)
The information in this article applies to:
- Microsoft Message Queue Server (MSMQ) 1.0
This article was previously published under Q306416 SYMPTOMS
When you use the Direct=TCP syntax to send messages to client computers that are running Microsoft Windows 95 or Microsoft Windows 98 and that are remotely connected to a network, the messages are rejected.
For example:
qinfos1.FormatName = "Direct=TCP:10.10.10.10\testq"
CAUSE
The queue manager binds to IP addresses that are assigned when the queue manager starts, which occurs during the boot process for Windows 95 and Windows 98. If the computer uses a remote access connection, a new IP address is assigned and that IP address may be used by applications that use the Direct=TCP FormatName syntax to send message to the client computer. This IP address is unknown by the queue manager at the time that the message arrives and the queue manager rejects messages that are sent to it that do not belong it.
RESOLUTIONA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone 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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Date Time Version Size File name
-------------------------------------------------------
18-Oct-00 17:06 37Kb Regsvr32.exe x86
31-Dec-00 11:38 318 62Kb Mqac.dll x86
31-Dec-00 11:38 318 34Kb Mqcertui.dll x86
31-Dec-00 11:38 318 23Kb Mqbkup.exe x86
31-Dec-00 11:38 318 52Kb Mqdscli.dll x86
31-Dec-00 11:38 318 14Kb Mqkeyhlp.dll x86
01-Aug-99 14:29 853 59Kb Mqlogmgr.dll x86
31-Dec-00 11:38 318 138Kb Mqoa.dll x86
31-Dec-00 11:38 318 456Kb Mqqm.dll x86
31-Dec-00 11:38 318 99Kb Mqrt.dll x86
31-Dec-00 11:38 5Kb Mqsvc.exe x86
31-Dec-00 11:38 318 114Kb Mqutil.dll x86
31-Dec-00 11:38 318 61Kb Msmq.cpl x86
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Modification Type: | Minor | Last Reviewed: | 10/6/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbfix kbprb kbQFE KB306416 |
---|
|