Solved

Can't communicate between 2 hub transport servers

Posted on 2010-11-13
8
5,285 Views
Last Modified: 2012-08-14
We have installed a second domain (it is not a child domain) and have installed Exchange 2007 in a server of this second domain (call it seconddomain).  I am able to send emails out to the internet but not to addresses that reside in the Exchange server from my first domain.  I see that the meesages get stuck in the queue with error: 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.
If I click retry again, I then get error: 451 4.4.0 Primary target IP address responded with:"454 4.7.0 Temporary authentication failure"
I ran the Exchange Troubleshooter and get the followint error: Computer account for 'SMTPSVC\Exchangeserver.seconddomain' not found in Active Directory.  No computer account in Active Directory has 'ServicePrincipalName' set to 'SMTPSVC/Exchangeserver.seconddomain' .  This will result in Kerberos authentication failures when server Exchange server attempts to create an SMTP connection to another Hub Transport server.   Any tips or suggestions?  Thanks in advance!
0
Comment
Question by:TSAdmin8
  • 6
8 Comments
 
LVL 13

Expert Comment

by:markusdamenous
ID: 34128271
So you've got 2 separate domains/exchange organisations using the same domain name, and you want them to share this address space correctly?
0
 
LVL 1

Expert Comment

by:lukepdsilva
ID: 34129911
ensure that the port 25 is open between the two servers.
telnet remote.server.name 25
make sure that both teh servers reecive cnnectors have the following auth & permission

authentication
first one TLS
exchange servers
integ windows

Permission
anonymous
exchange users
exchange servers
Legacy exchange

as the two servers are in the same network, create a send connector on both serves with teh following
address space tab should have address of remote servers email address domain name
network tab should have smarthost added (IP/FQDN of the remote server) & no auth

this should fix your issue
0
 
LVL 1

Author Comment

by:TSAdmin8
ID: 34137387
We have 2 domains withing the same forest...  Therefore there is only 1 Exchange Organization.
0
 
LVL 1

Author Comment

by:TSAdmin8
ID: 34137405
lukepdsilva, I will try the settings you provided right now and will let you know!  Thanks!
0
Free book by J.Peter Bruzzese, Microsoft MVP

Are you using Office 365? Trying to set up email signatures but you’re struggling with transport rules and connectors? Let renowned Microsoft MVP J.Peter Bruzzese show you how in this exclusive e-book on Office 365 email signatures. Better yet, it’s free!

 
LVL 1

Author Comment

by:TSAdmin8
ID: 34138646
Hi Luke, i wanted to let you know that I made the changes to the configureation on the receive connectors and yes, the 2 servers can telnet each other using port 25.  Before I make changes to the send connector, I just wanted to clarify something.  One of the exchange servers (connected to the firstdomain) is on the west coast and the second exchange server (seconddomain) is in the east coast. We have a dedicated tunnel between the 2 sites.  I have created Inter-site links.  Again, the second exchange server is in the seconddomain but both the firstdomain and seconddomain are part of the same forest so there is only 1 Exchange organization.  All the users from first or seconddomain will have firstdomain email addresses and the only difference is that users working in the west coast office will have their mailboxes hosted in the first exchange server while the others will have their mailboxes hosted by the second exchange server.  Do you foresee any problems with that kind of a set up?  Thanks in advance!
0
 
LVL 1

Author Comment

by:TSAdmin8
ID: 34151449
Hi Luke,
Sorry for not responding earlier but I felt pretty sick yesterday and did not work on the servers too much (and was very busy today).  I just have one more question...  If I create a Send connector for the 2 domains, will it mess up the email delivery to the other exchange servers that are in mydomain?  Please let me know.

Thanks,

Allie
0
 
LVL 1

Accepted Solution

by:
TSAdmin8 earned 0 total points
ID: 34176977
Well, the answer turned out to be adding the DC IP addresses in the forwarder for each domain.  Once that happened, AD started to replicate and resolve the exchange servers in the mydomaineast.
0
 
LVL 1

Author Closing Comment

by:TSAdmin8
ID: 34203755
I found out how to solve a DNS problem which is how the problem got solved afterall.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now