Exchange 2007 SP3 Failure at Hub Transport Role step.

Posted on 2010-09-12
Medium Priority
Last Modified: 2012-05-10
I have Exchange 2007 running on W2K3 R2.  I attempted to apply SP3 and got the following error message during the Hub Transport step:

Hub Transport Role

When the AuthMechanism parameter on a Receive connector is set to the value ExchangeServer, you must set the FQDN parameter on the Receive connector to one of the following values: the FQDN of the transport server "gsjs2.domainname.local", the NetBIOS name of the transport server "GSJS2", or $null.

We use a third party that receives our mail and relays it to our internal exhange server.  The FDQN of my LAN is gsjs2.domainname.local.

I have 3 Connectors:

Client - FDQN: gsjs2.domainname.local  Auth: integrated
Default - FDQN: mail.domainname.local Auth: Exchange Server
Internal Relay: FDQN: mail.domainname.local Auth: none

I believe it's complaining about the Default connector.

Your recommendations on how to resolve are very much appreciated it.  If I change the FDQN, how to proceed to continue with the SP3 install?  Do I rerun setup?

I'm hoping to resolve before monday AM when the workforce returns.

Many Thanks

Question by:OnsiteSupport
  • 2
  • 2

Author Comment

ID: 33658756
correction that last connector:

Internal relay: FDQN: gsjs2.domainname.local  Auth: none

LVL 32

Expert Comment

ID: 33658765
your Default connector must have the fqdn value of gsjs2.domainname.local  because of the ExchangeServer authentication
LVL 32

Accepted Solution

endital1097 earned 2000 total points
ID: 33658768
if you want external mail to connect to a different fqdn, then you need to create a new receive connector with anonymous permission

Author Closing Comment

ID: 33658909
Thanks....reapplied SP3 and we're back in business.

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

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

If there is anything erroneous with Exchange Database, it causes a significant effect on email communication till the user remounts the database. Further, database crash directly affects Outlook users due to which they are unable to access their ema…
In an Exchange Crossforest migration, the distribution groups can be a very complex operation that would cause loss of time, lots of issues and continued headaches if not solved in a timely manner. I had to do a similar project so I created a sc…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…
Suggested Courses

624 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