Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


Exchange 2007 on Server 2008 - problems with hub transport, no email in or out

Posted on 2008-10-13
Medium Priority
Last Modified: 2008-10-21
Just finished setting up Exchange 2007 SP1 with all updates on Server 2008.  We have an existing Exchange 2003 server running on Server 2003 that is running fine and are co-existing.  We're ready to move mailboxes, so we moved a test user over to 2007 and found we can't send or receive as that user.  Anything the user sends (Internal or external) just sit in the outbox.  If we try to send to the user from outside, we receive an immediate NDR.

So far, no AV on the Exchange 2007 box.  Exchange 2003 does have Forefront on it.

This is a typical Ex2007 install - there is no edge and the mailbox, client access and hub transport are on the same box.  

Running BPA does not give us any errors or notices.

Did a fair amount of research online and read about back pressure.  We're not receiving any errors regarding this.  Our C: drive has about 10 gigs free, which is where Exchange is installed, and our E: drive has about 80 gigs free, which is where our data lives.  Server has 4 gigs of memory.

The transport service is set to auto and is not running.  Credentials are currently network service.  Also tried as local system, no good.  As domain admin, the service runs, but doesn't help.

Here is the only error we're receiving -

Log Name:      Application
Source:        MSExchangeMailSubmission
Date:          10/13/2008 7:55:16 PM
Event ID:      1009
Task Category: MSExchangeMailSubmission
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      EXCH002.domain.com
The Microsoft Exchange Mail Submission Service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.
Question by:dipersp
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
LVL 23

Expert Comment

by:Justin Durrant
ID: 22708306

Author Comment

ID: 22710418
Here's the NDR:
Delivery has failed to these recipients or distribution lists:

The recipient's e-mail system can't process this message. Microsoft Exchange will not try to redeliver this e-mail message for you. Please provide the following diagnostic text to your system administrator.

Diagnostic information for administrators:

Generating server: remotedomain.com

#< #5.3.3 smtp;500 5.3.3 Unrecognized command> #SMTP#

As for the link you sent, under user actions,
"Make sure that the Microsoft Exchange Transport Service is enabled and running on the Hub Transport server."
- Well, right there's a problem.  Can't get the transport service running.

"Make sure that no firewalls filter network data or block MAPI remote procedure call (RPC) traffic between the Mailbox server and Hub Transport server."
- No firewall on the 2003 server, and the firewall is turned off on the 2008 server.

"Make sure that the Mailbox server and the Hub Transport server are not deployed in a perimeter network."
- Nope, mailbox and hub transport are on the same box on the internal network.

If this frequently occurs, consider whether you should add more processors on the Hub Transport server. You can also increase the value of MaxConcurrentMailboxSubmissions by using the Set-TransportServer cmdlet. For more information, see Set-TransportServer.

Accepted Solution

dipersp earned 0 total points
ID: 22731819
Found the problem - we had moved the transport logs to an alternative drive, and the network service didn't have the proper rights to the transportroles directory on that drive.  Once we fixed the permissions, started up and sent mail!

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A couple of months ago we ran into an issue that necessitated re-creating our Edge Subscriptions. However, when we attempted to execute the command: New-EdgeSubscription -filename C:\NewEdgeSub_01.xml we received an error indicating that the LDAP se…
Are you an Exchange administrator employed with an organization? And, have you encountered a corrupt Exchange database due to which you are not able to open its EDB file. This article will explain all the steps to repair corrupt Exchange database.
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
In this video we show how to create an email address policy 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…
Suggested Courses

636 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