Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have MSMQ running on a two-node Windows 2003 cluster. When I try to send transactional messages to a queue on a Windows 2008 server in another forest, the messages get stuck in the cluster's outgoing queue. The outgoing queue says "waiting to connect" and has the destination server's IP for the next hop.

I can send messages from the cluster to Windows 2008 servers in the same forest. I can also send messages from either node of the cluster to Windows 2008 servers in the same forest and the other forest. I can send messages from a Windows 2008 server in the other forest back to the cluster.

Edit: Running a network capture on the servers shows that the Windows 2008 server is receiving packets from the cluster, but they're not being passed up the layers to the MSMQ process.

share|improve this question
add comment

1 Answer

First thing I would do is make sure the Windows 2008 destination is listening on port 3527. http://blogs.msdn.com/b/johnbreakwell/archive/2010/03/05/port-3527.aspx

[March 5th] I would look at network traffic with Network Monitor or Wireshark.

What does the outgoing queue status do? You can restart the MSMQ service to start the outgoing queue connecting. The outgoing queue may be going through a "connecting - connected - disconnect after idle timeout - waiting to connect" loop. Or it may be "connecting - failing - waiting to connect" loop. Depends what the root cause is.

If it never connects then the 3-way TCP handshake never completes. Can you connect to a network share on the remote server? Basically eliminate all the basic networking issues.

The fact the server is in another forest shouldn't matter too much. The sender just needs to resolve the destination to an IP address, assuming you are not already addressing the messages by IP address.

Cheers

John

share|improve this answer
    
Sorry. According to the article, this only causes a slight delay. Our messages have been sitting in the queue for days. Also, this port is open. This isn't the solution to my particular issue, but good try. –  Jason Dentler Mar 5 '12 at 13:11
    
Edited answer for further suggestions. –  John Breakwell Mar 10 '12 at 23:21
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.