Posted this sucker on StackOverflow, but I think its probably more germane to this crowd :
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?
Here is our example :
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