Are you talking about sending MSMQ messages using the HTTP protocol or the
MSMQ protocol?
If you are using HTTP then, yes, you can specify the port number just as you
would in an Internet Browser to access a web service not listening on the
default port 80.
http://blogs.msdn.com/johnbreakwell/archive/2008/12/15/sending-msmq-messages-over-http-to-a-web-server-not-listening-on-port-80.aspx
If you are using the MSMQ protocol then this is designed around using port
1801. The MsmqIpPort registry value controls this but the notes say "Do not
change the value of this entry. Changing this value can prevent Message
Queuing computers from exchanging messages."
http://technet.microsoft.com/en-us/library/cc759698(WS.10).aspx
Cheers
John Breakwell (MSFT)
"seb" <s...@discussions.microsoft.com> wrote in message
news:4C7AED84-CCF4-4A06...@microsoft.com...
MSMQ/HTTP messaging is used by those people that want to send messages over
the Internet, for example.
You don't need to know anything about HTTP apart from how to address the
message.
IIS and MSMQ will handle delivery for you to the destination queue.
Limitations? Main one is that this is send-only so no remote reading of
messages.
"Can i still use workgroup accounts to authenticate messages?"
I don't understand - workgroup accounts can't be used to authenticate
anything as there is no shared security database.
Cheers
John Breakwell (MSFT)
"seb" <s...@discussions.microsoft.com> wrote in message
news:0FF26892-74FA-4C02...@microsoft.com...
The *supported* method is restricted to MSMQ/HTTP.
For two-way traffic, you will need IIS at both ends.
You would also need IIS on sender and receiver if you were using
transactional queues as they require acknolwedgement messages to travel back
from the destination.
Why exactly do you want to change the port used by MSMQ?
Cheers
John Breakwell (MSFT)
"seb" <s...@discussions.microsoft.com> wrote in message
news:324BEA11-9C96-4350...@microsoft.com...