Hi, hoping I get a bit of help on this one.. 

We are running exchange 2013 sp1 in a two node DAG.  I was applying CU8 onto the second node of the DAG last night and got a warning: 'setup can't detect a send connector with an address space of '*'.  Mail flow to the internet may not work properly' Running get-sendconnetor returns:

Internet                                {SMTP:*;1}                              True

Delivery is by MX using the DNS settings on transport server and both nodes are listed in the connector scoping as source servers.

With the databases all located on the second node I stopped the transport service on the first node and mail was stuck in the outbox until this service was restarted again then mail was delivered as normal.  On checking the header of a mail sent with telnet from the second node it shows the mail being sent from node 2 onto 1 to be delivered.  I need to take down node 1 to apply the CU but this will mean downtime.  How can I stop the mail being sent via node 1?

Follow this article 

http://blogs.technet.com/b/nawar/archive/2014/03/30/exchange-2013-maintenance-mode.aspx 

• Proposed as answer by Vishwanath.S 18 hours 6 minutes ago

Thanks for this, I presume you are referring to:

Redirect-Message -Server <ServerName> -Target <MailboxServerFQDN>

I'm pretty sure I ran this command, how do you reverse the redirect?

Checking get-servercomponentstate shows all components as active

• Edited by gilliano1715 16 hours 56 minutes ago

the redirect command is to stop new mails coming to queue. Once you are done with your maintenance, you bring back your server components to active state, this would bring the queue to be active 

Set-ServerComponentState <ServerName> -Component HubTransport -State Active -Requester Maintenance 

Restart-Service MSExchangeTransport

All components should be active, which shows it is ready to accept emails .

Follow this article 

http://blogs.technet.com/b/nawar/archive/2014/03/30/exchange-2013-maintenance-mode.aspx 

• Proposed as answer by Vishwanath.S Wednesday, August 05, 2015 1:23 PM
• Marked as answer by gilliano1715 19 hours 17 minutes ago

Thanks for this, I presume you are referring to:

Redirect-Message -Server <ServerName> -Target <MailboxServerFQDN>

I'm pretty sure I ran this command, how do you reverse the redirect?

Checking get-servercomponentstate shows all components as active

• Edited by gilliano1715 Wednesday, August 05, 2015 2:33 PM

Hi, hoping I get a bit of help on this one.. 

We are running exchange 2013 sp1 in a two node DAG.  I was applying CU8 onto the second node of the DAG last night and got a warning: 'setup can't detect a send connector with an address space of '*'.  Mail flow to the internet may not work properly' Running get-sendconnetor returns:

Internet                                {SMTP:*;1}                              True

Delivery is by MX using the DNS settings on transport server and both nodes are listed in the connector scoping as source servers.

With the databases all located on the second node I stopped the transport service on the first node and mail was stuck in the outbox until this service was restarted again then mail was delivered as normal.  On checking the header of a mail sent with telnet from the second node it shows the mail being sent from node 2 onto 1 to be delivered.  I need to take down node 1 to apply the CU but this will mean downtime.  How can I stop the mail being sent via node 1?

What servers are listed in the send connector? is it only one?

both servers are listed in the send connector.  I've moved databases/cluster etc off the second node and put this into maintenance mode and brought it back out, confirmed all the components are set to active via the maintenance requester and also set all the components to active using the functional requester but I'm still seeing the same issue. Any ideas?