Cant send to MSMQ with 2 DNS names

Question

We're Having an issue with sending an MSMQ message to the second DNS name on a server. If we send the IP for that same server, we're fine, but thats not where we are going architecturally. Any ideas as to why MSMQ would care about which name it receives?

Server Information:

The physical server load-int-01, has a second IP and DNS name associated with it.

• First IP/DNS: load-int-01, with IP 10.0.10.10
• Second IP/DNS: load-intv, with IP 10.0.10.20

Queue Path Formats Used:

• FormatName:DIRECT=OS:load-int-01\private$\MyQueue → Works Fine
• FormatName:DIRECT=OS:load-intv\private$\MyQueue → Returns the error…

  The queue does not exist or you do not have sufficient permissions to perform this operation

We have also tried using the IP addresses instead, and both sets of IPs work fine.

• FormatName:DIRECT=TCP:10.0.10.10\private$\MyQueue → Works Fine
• FormatName:DIRECT=TCP:10.0.10.20\private$\MyQueue → Works Fine

Answer 1

We just got off the phone with Microsoft. This is a limitation of MSMQ. You can not receive on queues with a DNS name different than the server NETBIOS name. You can SEND to queues with an alternate DNS name provided you use the two registry keys mentioned above, OptionalNames and IgnoreOSNameValidation.

Back to virtual ip's for us, or we might keep the virtual name for the sending connection strings (with the reg settings) and use .\ for the receiving servername...that works.

Thanks for the help.

Answer 2

From:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;899611

By default, Message Queuing verifies the message that it receives to determine whether the message is intended for the local computer. If the message is not intended for the local computer, the message is rejected.

So follow the section on "IgnoreOSNameValidation" in this article and I hope it will help.