I have a Windows 2003 Enterprise server running MSMQ for a proprietary application. With one NIC enabled everything works well and messages route correctly. When I enable the second NIC with an IP to a private network, all messages stop routing. They appear to be routing to the second NIC which is not connected to the WAN where the messages need to go out to get to their destination. How do I tell MSMQ to route to the 1st NIC?

Hi Web Connected,

The real question is what you are trying to achieve with the second NIC on the server.  Generally, this is done for routing or firewall purposes, but application servers rarely have this configuration.  If the majority of the communication is to be over the first NIC, this can easily be handled.  You'll want to set the priority of the NIC so that all traffic hits that NIC's default gateway before others.  Also, if you can rely on NetBIOS and broadcast traffic on the second NIC, you might simply not designate a default gateway to keep the traffic on segment. 

 Ryan Hanisco

Webconnected:

I have a Windows 2003 Enterprise server running MSMQ for a proprietary application. With one NIC enabled everything works well and messages route correctly. When I enable the second NIC with an IP to a private network, all messages stop routing. They appear to be routing to the second NIC which is not connected to the WAN where the messages need to go out to get to their destination. How do I tell MSMQ to route to the 1st NIC?