How do I configure HUB Send and Recieve connectors under a WNLB CAS and HUB role installed server? Thanks

Hi Make sure that port 25 is allowed in your NLB configuration And for incoming mail on HUB transport, create a new receive connector, type in the NLB (VIP) ip address so that it will receive mails on only that ip address.. On the send connector under Org Config, HUB just create a send connector and add both HUB servers as source servers. For load balancing CAS (OWA etc) make sure that port 443 is allowed in the NLB configuration and point in the firewall that it should receive incoming https req and forward them to VIP address I think that's it :)Jonas Andersson MCTS: Microsoft Exchange Server 2010, Configuration | MCITP: EMA | MCSE/MCSA Blog: http://www.testlabs.se/blog

Hi Mr.Kris, For outbound emails, when you have more than one Hub Transport server deployed in an AD site, connections will be load balanced automatically between the Hub Transport servers. There is only one exception to this rule, and that is when a Hub Transport server role is installed on a server also holding the Mailbox server role. In this specific scenario the Hub Transport server local to the Mailbox server will always be preferred over other Hub Transport servers in the AD site. So for outbound messages, you just have to make sure you add more than one Hub Transport server under the Source Server tab of the Send Connector which routes messages on to the Internet (or perhaps to a set of SMTP gateways in your perimeter network). For inbound mails, you need to create a new receive connector and specify the IP for the connector. Please check the following article which contains detail steps (it's also for Exchange 2010): Load Balancing Exchange 2007 SP1 Hub Transport Servers using Windows Network Load Balancing Technology (Part 2) http://www.msexchange.org/articles_tutorials/exchange-server-2007/planning-architecture/load-balancing-exchange-2007-sp1-hub-transport-servers-windows-network-load-balancing-technology-part2.html Hope this helps. Thanks, Elvis

Hi Mr.Kris, For outbound emails, when you have more than one Hub Transport server deployed in an AD site, connections will be load balanced automatically between the Hub Transport servers. There is only one exception to this rule, and that is when a Hub Transport server role is installed on a server also holding the Mailbox server role. In this specific scenario the Hub Transport server local to the Mailbox server will always be preferred over other Hub Transport servers in the AD site. So for outbound messages, you just have to make sure you add more than one Hub Transport server under the Source Server tab of the Send Connector which routes messages on to the Internet (or perhaps to a set of SMTP gateways in your perimeter network). For inbound mails, you need to create a new receive connector and specify the IP for the connector. Please check the following article which contains detail steps (it's also for Exchange 2010): Load Balancing Exchange 2007 SP1 Hub Transport Servers using Windows Network Load Balancing Technology (Part 2) http://www.msexchange.org/articles_tutorials/exchange-server-2007/planning-architecture/load-balancing-exchange-2007-sp1-hub-transport-servers-windows-network-load-balancing-technology-part2.html Hope this helps. Thanks, Elvis

Thank you Jon and Elvis for responding to my post. I have followed those steps already. Since Default Recieve connector shows ALL available IP addresses I have not changed it. This change is MUST for successful communications between two HUBs in two separate sites correct? What does "Client <HUB Server>" do? Do I need to carry IPv6 info into new recieve connectors? After countless search and what not I found out that I missed under CAS/HUB servers I need to enabled Anonymous Users in permissions groups tab for "Default <CAS/HUB Server>" recieve connector to recieve inbound mails since I don't use Edge transport server. Can you please validate this statement? So far so good in terms of receiving e-mails at least I think. But as for as Sending I still have issues. I'm receiving "451 4.4.0 primary target IP address responded with "421.4.4.2 unable to connect. attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts" and e-mails are queued. Firewall is set to port forward public IP to NLB vIP for incoming and outgoing. Is outgoing IP incorrect meaning I need to add Non-NLB IPs to port forward for outgoing? Do I need to enable port 25 in NLB vIP as in the article? I'm able to telnet without that config. Thanks Kris Update: corrections

Hi Mr Kris If you're using a NLB VIP for incoming mails i would create a new receive connector like "Inbound (NLB)" and setup that one to only receive mails on the VIP address and select TLS and Anonymous so you can receive mails from external senders. For outgoing you just setup a send connector and under source add the two HUB servers, they need to be allowed in the firewall to send mails (smtp port 25) from internal LAN to external. Double check you firewall rules Hope this will help you solving the questions :)Jonas Andersson MCTS: Microsoft Exchange Server 2010, Configuration | MCITP: EMA | MCSE/MCSA Blog: http://www.testlabs.se/blog

Jon, Yesterday, my firewall team had indicated the same and made those changes last night. Sorry I didn't post back that its working as of this morning. Also, I wanted to confirm this though from experts like you to ensure the steps followed are correct. I will make changes for receieve connector as you have recommended. How about IPv6? Though I'm not using should I carry those info? Thanks Kris