outlook clients sending via hub transport with no send connector

I have recently installed a second hub transport server to do some testing (nothing configured at first), i noticed after a couple of hours that any emails sent via outlook were getting caught in the new hub transport server.  not in any queue that could be flushed through but if i clicked on the messages tab i could see them all listed there.  i had to delete them all with NDRs so they could be resent.

If i configure the new hub transport server with a send connector, or add it to an existing send connector all emails flow ok.  If i shut the new hub transport server down then the emails go out the original hub transport server.

emails sent via OWA, LOB app or mobile phone all seem to go through the original hub transport server, emails via outlook all get caught in the new HT server if it's send connector isn't enabled.

i only wanted emails to go out via this HT server when the original is shutdown.  Has anyone seen this before or know what causes it and how to resolve?
P4ACAsked:
Who is Participating?
 
P4ACAuthor Commented:
after rebooting the servers i noticed on logging back in that the time was out by about 8 minutes between the two exchange servers.  i synced the two servers up and now when i remove one of the send connectors it sends email via the other one.  there is a bit of a lag on it as for some reason it still wants to send it via the opposite HT server than the one the mailbox is located on but at least it goes now after whatever time out it is checking against.

would still love to know why the MB server does not try to send out of it's own HT first but i'm sure that will remain a mystery.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
So you simply need to have both servers in the Send connector and if one is down other will automatically take the role of routing emails.

- Rancy
0
 
P4ACAuthor Commented:
Thanks for the quick response Rancy, however i may be moving this HT server to another site with it's own internet connection and don't want emails going out of that line by default.

I know if i create another AD site and move the exchange into it then theoretically it won't use that hub transport server as it's not in the same site but if it is going to be the same site i want to be able to pick and choose which hub transport is being used.

I also found it really weird that the minute it was installed the exchange decided to route email out a hub transport server with no send connector configured rather than the one it had been using all this time, also if the connector is disabled it doesn't re-route it, it just goes into a no-mans land that you can't see in any queue.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
If you say that you dont want any emails to be routed to External from this server you can simply remove it from the Send connector .... but still this server might be used to route emails to another HUB for relaying if needed.

I know if i create another AD site and move the exchange into it then theoretically it won't use that hub transport server as it's not in the same site but if it is going to be the same site i want to be able to pick and choose which hub transport is being used - You are correct Site does prevent using any HUB as it uses its internal site HUB for mail delivery :)

Last part is surely very wired :(

- Rancy
0
 
P4ACAuthor Commented:
if i remove it from the send connector that's when no emails go out at all, that's my whole problem. i've installed a new HT and all the users in my org want to use that one whether there's a send connector or not. i should probably have mentioned that this is only for external emails, internal work fine.

I've just done some testing and it gets weirder.  i created a mailbox role on that same server that's got the new HT server role and created a new user and sent an email and unless the original HT server is enabled emails from there go nowhere the same as my original users.

looks like users in my original mailbox server want to use the new HT server and won't go out the original server unless the new HT is shut down and users on the new mailbox server are doing the reverse and only sending out via the original HT server.

i must be missing something simple as this seems by design the fact that the issue replicates itself the other way.
0
 
P4ACAuthor Commented:
okay, slight update as it's quiet in here now, the user i setup on the second HT/MB server sends every second external email when the original HT is not in a send connector, however users in the original HT/MB server still can't send any emails when the new HT is not in a send connector.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Emails can only be sent to external if the server is in Send\Relay or some custom connector ....

If the same server has MBX and Transport it will always use the same server to route emails to the next hop until the recipient is not on the same server.

- Rancy
0
 
P4ACAuthor Commented:
i know how everything is supposed to work, problem is it's not working, can't figure out why one MB/HT server requires another HT server to be in a send connector for emails to go out when there is a perfectly good one already installed on the MB server the outlook clients reside on.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Agree ..... check for any Transport eventID's on the server.
Do you have a firewall in between .... is it able to receive emails from the affected Exchange server .... there are many firewalls on which you can specifiy which IP to accept emails from :)

- Rancy
0
 
P4ACAuthor Commented:
i've turned the internal firewalls off for testing but doesn't make any difference, IP filtering is done at the hardware firewall, i'll reboot servers tonight as a last resort then turn on diagnostic logging if it still isn't working, didn't have a lot of time to spend on this but looks like it's going to be a pain in the arse.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
:) ... will await your response

- Rancy
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
I had suggested to check for EventID's on the server also did put so much effort .... hope that should have helped and some points should have been awarded :(

- Rancy
0
 
P4ACAuthor Commented:
solution was to sync up the two exchange servers time
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.