So let's set the table. You have just completed designing your Exchange 2013 environment for your client. You are anticipating no more than a day or so to build the servers and test mail flow. You have scripted the export and import of the existing receive connectors. Upon completion you instantly notice that the transport service will not remain started, and opening items such as queue viewer result in messages stating that the local server can not be found. Welcome to Exchange 2013 SP1.
First and foremost, there are several issues at play:
- Transport agent not starting
- Importing\Creating receive connectors of the "Hub Transport" type that are bound to port 25 is a no-no.
- The only type of receive connector that can be bound to port 25 on an Exchange 2013 server is a "Frontend Transport" type.
- Admin must change the type of transport agent to "FrontEnd" for any agents "Hub Transport" agents that are bound to port 25.
- Set-ReceiveConnector –Identity "Receive connector name" –TransportRole FrontendTransport
- Queue viewer will not open citing a name resolution error for the local server.
- Exchange DNS since SP1 is somehow unable to resolve its own name with regards to the Exchange tools.
- The fix is to set the Internal DNS server field of the "Hub Transport Service" and the "Front End Transport Service" via the "Set-transportserver" PowerShell cmdlet.
- Also add the Net Bios name and the FQDN of the server to the local host file.
Once the above items were set the server was able to process mail and I was also able to view the mail queues via the Exchange tools.Labels: DNS, Exchange 2013