The workaround is to turnn off the MessageQueue.EnableConnectionCache =
false.  This will force a new connection each time.

You should do this whenever you are doing remote receives across anything
more than a server room switch.

But MSMQ is designed to work transparently across unstable connections.  But
to take advantage of its reliable messaging capabilities you must follow
proper message queueing procedures.  The rule is "Remote Sends and Local
Recieves".  Have the remote machine send it back to a local queue for you.
This is what the Message.ResponseQueue property is for.

When you send a message to a remote queue, it goes into a local outgoing
queue and is sent as soon as a network connection is available.  So, so long
as all messages are sent to a remote queue to be locally received, you have
guaranteed delivery across unreliable networks.

David