Howdy all -- apologies in advance for the longish post...I'm trying to be as descriptive as possible.
We have the following components:
1. SBS 2003 server, running Exchange 2003 (sp2), AD, DNS, file/print. IP: 192.168.1.11
2. a *NEW* Netgear FVS336G dual-WAN router. LAN IP: 192.168.1.1
3. a Snow Leopard Server (Mac Mini) running Postfix, Apache, etc. All the usual suspects. IP: 192.168.1.12
All was humming along until we installed our new router last weekend, to increase our bandwidth from our split T1 (Logix) to add a new broadband connection (EasyTel). Our public server IPs are on the T1 side, so we've left this 768Kbps stream purely for server traffic in and out. Our users go out over the faster broadband 99% of the time as it has less latency.
The problem involves mail delivery from Exchange to Postfix - no. It just sits in the queue, waiting. Other mail sending directions are as follows:
Mail from Postfix to Exchange - yes
Mail from Internet to Exchange - yes
Mail from Internet to Postfix - yes
Mail from Postfix to Internet - yes
Mail from Exchange to Internet - yes, but with some sites (msn.com, yahoo.com, me.com) there's a bit of volume there waiting too. Under 30 messages, but still enough to concern me.
Prior to this weekend our ISP (Logix) did our LAN creation stuff (gateway, dhcp,) on their Adtran box, but with the new router all that falls to us now. We've created new DNS entries on our Exchange box to provide valid IPs to all clients, pointing to the LAN addresses rather than the former WAN ones.
The Netgear dual-WAN router gives us ways to point the traffic from the LAN to whichever WAN interface we require, but I don't see any way to build a point-to-point route so that Exchange will know to send the traffic via the LAN. My guess is that it's waiting to shoot it out via the WAN, and hence the fat queue.
I've attached a pic of a representative msg via the Exchange Message Tracking.
Thanks in advance,