• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1067
  • Last Modified:

Exchange 2007 hub to hub (indifferent AD Sites) not working

Hi All
I have a network with two sites, previously both sites accessed Exchange mailboxes in Site1.  Site2 was installed with CAS, Hub and Mailbox roles and the intention of moving Site2 users off to the Site2 Exchange.  All 3 roles are on a server in Site1.

Everything so far looks fine except the original Site1 cannot deliver mail to mailboxes in Site2 - they sit in the queues instead.  The network is fully routed and there's no firewall rules blocking any traffic on the VPN link.  The BPA doesn't help much either and the queues just say "421 4.2.1 Unable to connect. Attempted failover to alternate host., but that did not suceed. Either there are no alternate hosts, or delivery failed to all alternate hosts. ".  I can telnet into port25 on the Site2 server from site1.

Can anyone please help??
0
nwteam
Asked:
nwteam
  • 3
  • 2
1 Solution
 
nwteamAuthor Commented:
Update.. that message seemed to have been a once off (maybe there were connectivity issues) but now the error that is reported, all the time, is  451 4.4.0 Primary target IP address responded with: "421 4.4.2 Connection dropped"  Attempted failover to alternate host, but that did not succeed.  Either thre are no alternate hosts, or delivery failed to all alternate hosts.
0
 
rparsons1000Commented:
Looks like the same error. I'd look at DNS again, can the HT telnet to the Site2 HT using the fqdn?
0
 
nwteamAuthor Commented:
Yep it sure can.  I just ran the Exchange Troubleshooting Assistant and got his though:  Mail acceptance failure.  Remote server exchange2.domain.local failed the mail acceptance test.  BDAT command: Respond = Remote socket is not available.  Check for firewalls and applications that can possibly block the BDAT command.

There's no antivirus on the new Exchange server yet and the VPN rules are still allow any-any....
0
 
rparsons1000Commented:
I am at a loss with easy possible fixes. I would make sure you are completely up to date with Sp's and rollups. I actually had a server one rollup back cause huge issues...at least I am pretty sure that is what it was. once I got all the same with restarts across the board all was good.

At this point if you can't find any acceptable answers II'd use Wireshark on both sides and do a capture to see what is going on. If it gets to that point, I;d be glad to assist in analyzing the captures.

Sorry I cant be of more assitance.
0
 
nwteamAuthor Commented:
hi guys, thanks for the replies... this was eventually tracked down to a firewall product that was installed on the Exchange server (yes not best practice!)
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.

Join & Write a Comment

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now