SMTP test to Exchange 2013 failing

I have an Exchange 2013 server set up for testing which I am trying to have the internal servers relay off of to EarthLink (My ISP).
The Receive Connector is set up as a FrontEnd Transport, Anonymous and Externally Secured authentication. It accepts all addresses from my internal subnet.
The Send Connector is set up using a Smart connector to smtpauth.earthlink.net. It is set to use port 587 ( which is what EarthLink apparently uses). It uses basic authentication with my credentials to EarthLink. The address space is set
to '*'.
When I am on one of the member servers, I telnet 25 to the Exchange 2013 server and testing it:
220 exchange.home.com Microsoft ESMTP MAIL Service ready at Sun, 23 Nov 201
4 08:41:40 -0500
ehlo home.com
250-home.cave.com Hello [172.16.200.20]
250-SIZE 36700160
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-AUTH
250-8BITMIME
250-BINARYMIME
250 CHUNKING
mail from:[email protected]
250 2.1.0 Sender OK
rcpt to:[email protected]
250 2.1.5 Recipient OK
DATA
354 Start mail input; end with <CRLF>.<CRLF>
Hello
Goodbye
451 4.7.0 Temporary server error. Please try again later. PRX3
I have been searching all over for some insights what this 451 4.7.0 .... PRX3 error is. There are a number of posts about PRX2, PRX4 and so forth. I have already found the information about verifying all DNS servers and creating a record in
the host file. None of that changed anything.
I disabled Symantec thinking it was causing the problem. Nope.
Any suggestions are GREATLY appreciated!

Hi Dolbert
Thank you for your question.
Did you can receive/send email?
If not, you can give me some error in your log or event?
“451 4.7.0 Temporary server error. Please try again later. PRX3” encoded SMTP response for when proxy fails because of connection failures to the destination. It happened at the send connector cannot resolve the correct destination. You can refer to the
following link to set configure internal reply:
http://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/
http://exchangequery.com/2013/12/02/steps-to-configure-anonymous-and-authenticated-relay-in-exchange-2013/
If there are any questions, please let me know.
Best Regard,
Jim

Similar Messages

Error 550 5.7.1 unable to relay with SMTP PORT 25 Exchange 2013

Hi All,
I know this issue has been posted for a while, but still can't resolved issue. We've new Exchange 2013 SP1 (CU4) installation, everything is working properly, the OWA, Exchange Client Connection, SMTP/POP with SSL, except with SMTP Using Port 25 Non-Encrypted
Connection.
If I'm using the SMTP Port 25 without TICK "My Outgoing Server (SMTP) Requires authentication", I've got the error: "550 5.7.1 Unable to relay", but if I TICK the option above, my message will be deliver without any error, how do i get
rid this problem, I need to UN-TICK the option above for the time being, since we've hundreds email account, I want to avoid to educate and tell the user and even remote their PC, just to configure this issue, it will drive me crazy, we're going to use the
Exchange Client Connection in the future, If everything is smooth and ok.
I research this problem on the Internet and of course with TECHNET, but still can't, anyone can help me on this?
fyi, I tried so many things, delete the default the Default Front End Transport for Port 25, it also not fix my issue.
Thx
Irwan

Hi
You can paste the output of below result
Get-receiveconnector | fl name,bindings,PermissionGroups
I think your default receive connector should be missing out some permissions.
Also try to see if you get any message on protocol logs and paste them too
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Uninstall Exchange 2013 failed on step number 8 Languages

Dear All,
I am not able to uninstall exchange 2013. the process is failing on step 8 Languages. Please advise

Any one please guide how to uninstall Exchange 2013?
Thanks in advance

SMTP Routing in Exchange 2013

We are migrating from Exchange 2007 to Exchange 2013 and I have some questions around the mail flow changes in 2013.
I understand that the CAS role plays a part in mail flow now. We have our 2013 CAS servers installed as a separate role.
Should we direct our internal applications to the CAS servers for SMTP mail delivery or should it be the Mailbox servers?
Should the external mail flow next hop from our SPAM firewall be the CAS servers?
Where should we apply receive connector rules, CAS or Mailbox?

Hello,
For your applications, if the recipient is a internal user, you can configure internal SMTP relay via the frontend transport service. If the recipient is an external user, you can configure external SMTP relay via the frontend transport service.
The frontend transport service is on CAS server.
Here is an article for your reference.
http://exchangeserverpro.com/exchange-2013-configure-smtp-relay-connector/ (Note: Microsoft
is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you
completely understand the risk before retrieving any suggestions from the above link.)
You're right. The external mail flow next hop from your firewall will be CAS servers.
You should apply transport rule on Mailbox server.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Exchange 2013 fails Active Directory Prep

This is a new, new, installation of Windows Server 2012 R2 Essentials followed by Exchange 2013, all on a single server that is also the DC, in a lab environment.   This is to replace an existing SBS2000 installation in a small business.
Server 2012 setup without any significant issues. The first pass at Exchange 2013 resulted in "access denied" when attempting to access the Exchange Management PS and login credentials failure for Exchange EAC (ECP).   After manually
adding the installation Administrator to a number of the Exchange security groups, I was able to access Exchange Manager. I checked that there was a mailbox associated with the Installation Admin ID, attempted to reset passwords and a number of other
things to no avail. I uninstalled Exchange (what a pain).
I reinstalled Exchange. As with the first time, no prerequisite errors and no installation failure alerts.   Again, I could not access Exchange Manager (access denied) or the EAC (login credentials failure).   This time, I was not
able change the security group permissions to gain access to Exchange Manager. Again, checked about everything there was to check on the web and found a reference to Exchange possibly not installing correctly due to lingering entries from the first install.
As I could not access Exchange Manager to perform the uninstall prerequisites, I attempted to manually delete it (nothing to loose at this point), but made the anticipated mess.
Wiped the RAID and started over with a clean sheet install of Server 2012 Essentials-OK. Progressed in the Exchange install prep to "Prepare Active Directory and Domains" (http://technet.microsoft.com/en-us/library/bb125224(v=exchg.150).aspx)
and stopped when I could not detect the confirming ADSI entries of AD prep set forth at the close of the TechNet document.
I methodically stepped through the install procedure and again received no prerequisite failures or installation failure alerts. I examined the install logs and found no errors, either.
Any words of wisdom?

Hi,
From your description, Windows Server 2012 R2 Essentials and Exchange 2013 are installed on a single server that is also the DC.
Microsoft does not support installing Exchange Server on a server that is running Windows Server Essentials. You need to install Exchange Server on a second server and then join the second server to the Windows Server Essentials domain.
And it is not recommended to install Exchange server on DC.
Here is a related article for your reference.
Integrate an On-Premises Exchange Server with Windows Server Essentials
http://technet.microsoft.com/en-us/library/jj200172.aspx
Best regards,
Belinda Ma
TechNet Community Support

Installation MS Exchange 2013 Failed

Hello,
Today I make a fresh install of the windows server 2012 STD, installed differents roles et promote my server like Domain controller.
After, I installed MS Exchange 2013 STD on this server with following procedure https://social.technet.microsoft.com/wiki/contents/articles/14506.how-to-install-exchange-2013-on-windows-server-2012.aspx and I encountered the following error during setup
progress (installation GUI).
Erreur :
L'erreur suivante est survenue lors de l'exécution de "$error.Clear();
          install-MsiPackage `
          -PackagePath ($RoleInstallPath + "TransportRoles\agents\Hygiene\ASEntIRS.MSI") `
          -LogFile ($RoleSetupLoggingPath + "\InstallASEntIRS.msilog") `
          -PropertyValues ("ALLUSERS=1") `
          -UpdatesDir $RoleUpdatesDir
        " : "Échec de l'installation du produit « D:\Donnees Entreprise\Messagerie\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASEntIRS.MSI ». Erreur irrécupérable lors de l’installation. Le code
d'erreur est 1603.".
I uninstall MS Exchange, demote DC and delete the folders created during exchange install and reboot.
After, I promote, reinstall exchange and I have a same error. I verify that the IP V6 is enable, I downloaded the source installation a second time (from MVLS), verify that my computer account is member of the exchange admin group...
Could you help me please because I have not got any solution?
Thanks and kind regards
Guillaume

Hello,
Today I make a fresh install of the windows server 2012 STD, installed differents roles et promote my server like Domain controller.
After, I installed MS Exchange 2013 STD on this server with following procedure https://social.technet.microsoft.com/wiki/contents/articles/14506.how-to-install-exchange-2013-on-windows-server-2012.aspx and I encountered the following error during setup
progress (installation GUI).
Erreur :
L'erreur suivante est survenue lors de l'exécution de "$error.Clear();
          install-MsiPackage `
          -PackagePath ($RoleInstallPath + "TransportRoles\agents\Hygiene\ASEntIRS.MSI") `
          -LogFile ($RoleSetupLoggingPath + "\InstallASEntIRS.msilog") `
          -PropertyValues ("ALLUSERS=1") `
          -UpdatesDir $RoleUpdatesDir
        " : "Échec de l'installation du produit « D:\Donnees Entreprise\Messagerie\Microsoft\Exchange Server\V15\TransportRoles\agents\Hygiene\ASEntIRS.MSI ». Erreur irrécupérable lors de l’installation. Le code
d'erreur est 1603.".
I uninstall MS Exchange, demote DC and delete the folders created during exchange install and reboot.
After, I promote, reinstall exchange and I have a same error. I verify that the IP V6 is enable, I downloaded the source installation a second time (from MVLS), verify that my computer account is member of the exchange admin group...
Could you help me please because I have not got any solution?
Thanks and kind regards
Guillaume

Installation of Exchange 2013 Failed on Mailbox Role Transport Service

Hi All,
Getting this error when trying to install a new exchange 2013 server. Thanks in advance
Error:
The following error was generated when "$error.Clear();
          if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
            Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
        " was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.Save(ADRecipient instanceToSave)
   at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.Link()
   at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Hi,
This problem occurs because the federated built-in e-mail account that links to the computer account no longer exists. Or, the federated built-in e-mail account in the AD
directory service is corrupted.
Please try to follow these steps to solve this problem.
    1. Remove the FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 e-mail account by using the ADSIEDIT tool. To do this, follow these steps:
Click Start, click Run, type adsiedit.msc, and then click
OK.
Locate the Default Naming Context node, and then locate to the
CN=Users container.
Locate and then right-click the CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 container. Then, click
Delete.
    2. Rerun the Exchange Server 2013 Mailbox role setup application.
    3. Create a new federated e-mail account by using the following command:
New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@<Default_Accepted_Domain>
If this issue persistes, please let me know.
Best Regards.

SMTP Authentication in Exchange 2013 multi tenant

I have configure a multi tenant environment. local domain is scurenet.local and i have host 3 different email domains like
abcd.com efg.com and xyz.com. now how its possible to create 3 mailboxes of same login in 3 different domains like [email protected] [email protected] [email protected] also
want to authenticate with there emailIDs and that is main issue. i can create 3 different logins like john1 john2 and john3 in AD and manually add smtp like [email protected] etc.
but issue is how i authenticate users with SMTP IDs so john1 can login using [email protected] and
password john2 use [email protected] as
login id and so on.

Hi,
I think you can try creating mailboxes for the three users and assign the full access permissions to each other.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange 2013, multiple IIS OWA sites with different authentication

Hi
I have an exchange 2013 server with Client Access and Mailbox server installed. The server has an second ip address which I have bound an additional IIS site to. The additional IIS site is named ExchangeExternalFBA.
The default web site is configured for basic and windows authentication with:
Set-EcpVirtualDirectory -identity "ecp (default web site)" -FormsAuthentication:$false
Set-owavirtualdirectory -identity "owa (Default Web Site)" -FormsAuthentication:$false -WindowsAuthentication:$true -BasicAuthentication:$true
Then a new ECP and OWA are configured with:
New-ecpVirtualDirectory -WebSiteName "ExchangeExternalFBA"
New-OwaVirtualDirectory -WebSiteName "ExchangeExternalFBA"
Set-owavirtualdirectory -identity "owa (ExchangeExternalFBA)" -LogonFormat FullDomain -FormsAuthentication:$true -WindowsAuthentication:$false -BasicAuthentication:$true
Set-EcpVirtualDirectory -identity "ecp (ExchangeExternalFBA)" -FormsAuthentication:$true
Then I perform an iisreset.
My problem is that then when I try to access the ECP or OWA on the default website, it loads forms authentication! The ECP or OWA on the ExchangeExternalFBA web site works correctly and also loads forms authentication.
If I run...
get-owavirtualdirectory "owa (ExchangeExternalFBA)"
then it returns:
InternalAuthenticationMethods : {Basic, Ntlm,
WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : True
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
If I then run
Set-EcpVirtualDirectory -identity "ecp (default web site)" -FormsAuthentication:$false
Set-owavirtualdirectory -identity "owa (Default Web Site)" -FormsAuthentication:$false -WindowsAuthentication:$true -BasicAuthentication:$true
and perform another iisreset then when I try to access the ECP or OWA on the default website it loads correctly. But then the forms based authentication on the ExchangeExternalFBA website can no longer log in, it does not accept the user name and password.
If I then disable and enable FBA on the ExchangeExternalFBA website then it works but forms based authentication takes over the default web site again!
Whether I perform the above from the gui or from powershell it does not make a difference, the same behaviour is observed. Changing the logontype on the FBA does not make a difference.
This has been tested on exchange 2013 cu1 and cu2.
Similar(if not identical until they get sidetracked) issue reported in http://social.technet.microsoft.com/Forums/exchange/en-US/9fcd360f-6658-4940-add7-2f13265cf86b/multiple-owa-sites-on-a-single-server-2012-with-exchange-2013-mailbox-cas.
This worked fine in outlook 2007 and 2010, why now do my virtual directories break each other?
I can reproduce the issue on a test exchange 2013 I built in dev.
Is this a bug or are you no longer meant to host different forms of authentication on a single cas?
I'm mostly interested to see if this works for other people and why it no longer seems to work in 2013, so please no questions; 'why do you want 2 different forms of authentication'.
Much appreciated, Thanks!

Based off of your feedback I have run the following:
Remove-OwaVirtualDirectory "owa (ExchangeExternalFBA)"
Remove-EcpVirtualDirectory "ecp (ExchangeExternalFBA)"
iisreset
Set-EcpVirtualDirectory -identity "ecp (default web site)" -FormsAuthentication:$false
Set-owavirtualdirectory -identity "owa (Default Web Site)" -FormsAuthentication:$false -WindowsAuthentication:$true -BasicAuthentication:$true
New-ecpVirtualDirectory -WebSiteName "ExchangeExternalFBA" -Role ClientAccess
New-OwaVirtualDirectory -WebSiteName "ExchangeExternalFBA" -Role ClientAccess
Set-owavirtualdirectory -identity "owa (ExchangeExternalFBA)" -LogonFormat FullDomain -FormsAuthentication:$true -WindowsAuthentication:$false -BasicAuthentication:$true
Set-EcpVirtualDirectory -identity "ecp (ExchangeExternalFBA)" -FormsAuthentication:$true
iisreset
After this there has been no change in behaviour. After the iisreset, forms have again hijacked the default web site and re-setting the authentication on the default web site removes the forms but breaks the ability to sign in to the forms based page on the
ExchangeExternalFBA web site again.
Note. '-Role Frontend' did not work. It showed the error:
Cannot process argument transformation on parameter 'Role'. Cannot convertvalue "frontend" to type
"Microsoft.Exchange.Management.SystemConfigurationTasks.VirtualDirectoryRole".
Error: "Unable to match the identifier name frontend to a valid enumerator name. Specify one of the following enumerator names and try again:
ClientAccess, Mailbox"
+ CategoryInfo : InvalidData: (:) [New-OwaVirtualDirectory], ParameterBindin...mationException
+ FullyQualifiedErrorId : ParameterArgumentTransformationError,New-OwaVirtualDirectory
Running get-help New-OwaVirtualDirectory -detailed shows the correct usage would be '-Role ClientAccess'?
-Role <ClientAccess | Mailbox>
The Role parameter specifies the configuration that should be used
when the virtual directory is created. The following are the values
that can be used with this parameter:
* FrontEnd Configures the virtual directory for use on a Client Access
server.
* BackEnd Configures the virtual directory for use on a Mailbox server.

Outlook Anywhere settings in a Exchange 2013 coexistence scenario with Exchange 2007

I have exchange 2013 and 2007 set up in a coexist environment. At the moment, the few mailboxes I am testing on Exchange 2013 are getting multiple pop ups in outlook and cannot connect to items like Public Folders on 2007. I found an article
that told me to change the authentication method from Negotiate to NTLM and that broke some of my Lync 2013 compatibility issues on users on exchange 2007 (ie conversation history and they got outlook integration errors.) I would like someone to confirm
if the change I am about to make from doing research will help me in my situation.
Current Setup:
Exchange 2007 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: NTLM
IISAuthenticationMethods : {Basic, Ntlm}
Exchange 2013 OA CAS Settings
ExternalClientAuthenticationMethod : Negotiate
InternalClientAuthenticationMethod: Negotiate
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
New Settings I am considering based on research:
Exchange 2007 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: Basic
IISAuthenticationMethods : {NTLM}
Exchange 2013 OA CAS Settings
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod: Basic
IISAuthenticationMethods : {Basic}
Will this work and eliminate my popups?

Hi,
The following TechNet article indicates that:
“In order to support access for Outlook Anywhere clients whose mailboxes are on legacy versions of Exchange, you will need to make some changes to your environment which are documented in the steps within the
Exchange Deployment Assistant. Specifically,
you will need to enable Outlook Anywhere on your legacy Client Access servers and enable NTLM in addition to basic authentication for the IIS Authentication Method.”
Client Connectivity in an Exchange 2013 Coexistence Environment
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
As for the Autodiscover service, please make sure the Autodiscover.domain.com is pointed to your Exchange 2013 in Internal and External DNS. For more detailed information about Exchange 2013 coexistence with Exchange 2007, please refer to:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 management tools installation on windows 2012 standard edition gives error.

Exchange 2013 management tools installation on windows 2012 standard edition gives following error.
Does anyone observed this issue ?
Error:
The Exchange management tools are supported on servers running Windows Server 2012 and Windows Server 2008 R2 SP1 or later, and also on Windows 8 and Windows 7 client computers.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ValidOSVersionForAdminTools.aspx
My Test lab is having
Exchange 2013 installed (xyz.local) domain and working fine.
Now i am installing Exchange Management tools on server which is member of (xyz.local) Domain (base OS : Windows 2012 standard edition : Windows updated)
Best Regards
sameer Prabhune

Hi Sprabhune,
It should work.
Did you install the tool by GUI or cmd?
Please select "Automatically install Windows Server roles and features that are required to install Exchange Server" to have the Setup wizard install required Windows prerequisites.
If possible, please try to install the tool on Windows 7/8 client to test.
Exchange 2013 Prerequisites
http://technet.microsoft.com/en-us/library/bb691354.aspx
Frank Wang
TechNet Community Support

Test-ReplicationHealth Database Redundandacy and Database Avaliability *FAILED* Exchange 2013 DAG setup

Trying to setup DAG between 2 exchange 2013 servers - one of them being in the remote location with physical point to point line. We have no firewall rules between 2 locations
EX01 ( on site)
EX02 (remote)
ETH01 10.11.1.2/24 - MAPI                       ETH01 10.11.13.15/24
ETH02 10.0.0.1/30 - REPLICATIOn            ETH02 10.0.0.2/30 - REPLICATION
Witness server is in 3rd remote location
These are the test results I get from Test-ReplicationHealth and Cluster Network Validation
I also run a Nmap command to make sure udp port 3343 is open on both sides
alex serdyukov

Hi,
The error message said that current Redundancy Count was 1 but expected Redundancy Count was 2. Therefore, Database 'IT2013' does not have enough copies configured to meet the validation criteria.
Please replicate that database to another server at least. We can refer to Hinte's suggestion to
add another copy for the database 'IT2013' in the DAG then check whether the issue persists.
Regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Winnie Liang
TechNet Community Support

Exchange2010 migration to Exchange 2013 federation trust failed (Outlook Provider Failure)

We are in a migration Exchange 2010 to Exchange 2013.
On the 'old' Exchange 2010 we are using a Federation Trust to 2 order company's. The federation trust for mailbox's on the exchange 2013 wont work.
We removed the federation trust on the old exchange 2010 server and create a new federation trust on the new Exchange 2013 server. We also changes the DNS TXT records. Creating the new federation trust without errors. But when the 2 order company's trying
to connect (add our company name for trust) they get a error.
A have trying to run a couple tests on the new Exchange 2013 server and found this error:
[PS] C:\Windows\system32>Test-OutlookWebServices -debug -Identity [email protected] -MailboxCredential(Get-Credential
cmdlet Get-Credential at command pipeline position 1
Supply values for the following parameters:
Credential
Source                              ServiceEndpoint
Scenario                       Result Latency
(MS)
AM111.AM.LAN                        autodiscover.company.nl            Autodiscover: Outlook
Provider Failure     144
AM111.AM.LAN                        webmail.company.nl
Exchange Web Services          Success     134
AM111.AM.LAN                        webmail.company.nl
Availability Service           Success     207
AM111.AM.LAN
Offline Address Book           Skipped       0

Hi,
Are you add primary SMTP domain as a federated domain? If not, please run below command to achieve this function:
Add-FederatedDomain -DomainName contoso.com
Configure federated sharing for the Exchange 2013 organization. Complete the steps in
Configure federated sharing.
Configure federated delegation (previous name for federated sharing) for the Exchange 2010 SP2 organization. Complete the steps in
Configure federated delegation.
Besides, I find an similar thread about Autodiscover service failed within federated trust, for your convenience:
https://social.technet.microsoft.com/Forums/ie/en-US/ea192e0a-1363-4cb6-9fc4-2973f64afc23/the-response-from-the-autodiscover-service-at?forum=exchange2010
Best Regards,
Allen Wang

Exchange 2013 External Relay gives me a headache... Anonymous relay fail to external address

I tried to set up external relay on my Exchange 2013 but was not able to do it. I don't know what else to do. I tried these:
http://technet.microsoft.com/en-us/library/bb232021.aspx
and these (which is pretty much same thing)
http://www.shudnow.net/2013/06/04/how-anonymous-relay-works-in-exchange-2013/
http://exchangeserverpro.com/exchange-2013-configure-smtp-relay-connector/
http://glazenbakje.wordpress.com/2012/12/30/exchange-2013-how-to-configure-an-internal-relay-connector/
http://blogs.technet.com/b/exchange/archive/2006/12/28/3397620.aspx
But still no luck. Here is somewhat detailed description what I tried do accomplice.
Server which need to send mail reports is sending these from web server on another location connected with site-to-site VPN to location server resides like on picture. I am able to send relay to all of
addreses of local domain but when I tried to send mails to my clients to external e mail addresses exchange return me message unable to relay.
Here is log from unsuccessfully operation
Connecting to [smtp.mydomain.com] port [25]...
220 smtp.mydomain.com Microsoft ESMTP MAIL Service ready at Fri, 24 Jan 2014 17:19:45 +0100
>HELO webserver
250 smtp.mydomain.com Hello [89.x.x.x]
>MAIL FROM: <[email protected]>
250 2.1.0 Sender OK
>RCPT TO: <[email protected]>
ERR: Received the following unexpected repsonse:
550 5.7.1 Unable to relay
>QUIT
221 2.0.0 Service closing transmission channel
Here is log from successfully operation:
Connecting to [89.x.x.x] port [25]...
220 smtp.mydomain.com Microsoft ESMTP MAIL Service ready at Fri, 24 Jan 2014 18:04:52 +0100
>HELO webserver
250 smtp.mydomain.com Hello [89.x.x.x]
>MAIL FROM: <[email protected]>
250 2.1.0 Sender OK
>RCPT TO: <[email protected]>
250 2.1.5 Recipient OK
>RCPT TO: <[email protected]>
250 2.1.5 Recipient OK
>DATA
354 Start mail input; end with <CRLF>.<CRLF>
>From: Dane <[email protected]>
>To: [email protected]
>Subject: asd
>Date: Fri, 24 Jan 2014 18:03:08 +0100
>X-Mailer: Qm Version 2.1
>MIME-Version: 1.0
Content-type: text/plain
>
>test>
250 2.6.0 <3ffb1fd6-e5e0-4232-9a6e-cac7b59db9df@exchange.mylocaldomain.local> [InternalId=6240587481093] Queued mail for delivery
>QUIT
221 2.0.0 Service closing transmission channel
And here is picture:

Hello,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

On Windows 2012 Terminal Server Outlook fails to connect to Exchange 2013

I have a new install of Windows 2012.  I have two physical servers. One is a W2012 std Domain Controller ("DC"). The Second is configured as W2012 HyperV  ("HV"). Under HV I have
two VMs. One VM is W2012/Exchange 2013 ("ExchVM) and the other is W2012/Terminal Server ("VMTS"). All systems are behind a firewall appliance. Exchange is working via Outlook and OWA internally and externally. The self
created SSL must be installed manually on external machines since it comes up as an untrusted certificate. Once installed remote outlook works and OWA works. I have configured the terminal server and I am able
to login remotely as various users under my "TS group". The problem is when ever I attempt to open Outlook for the 1st time, it fails to connect to the exchange server.   (Open Outlook 2013, click next
on the splash screen, "Yes" Add an Email Account splash screen, click next, Auto Account screen populates NAME and Email Address correctly, click next, Searching for mail server settings..., check on establishing network connection, check on searching
for alias@ domain, then fails the logging on to the mail server) The error reads: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The
connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."   I am connected in RDS from offsite, and from the RD session I can access shared folders on ExchVM and DC. I have
tried have verified the server Exchange server name is correct via "Get=ClientAccessServer" command. I have also tried to use the guid via "Get-Mailbox
ALIAS | fl name, exchangeguid. Keep in mind all desktop users on the network are connecting to Outlook without issue.
I would appreciate any thoughts on solving this issue.

Hi,
According to your workaround, it seems that the Outlook Anywhere configuration in Outlook client is not correct when using the Autodiscover service.
Once you connected to Exchange server by manually settings, please run Test E-mail AutoConfiguration tool in external Outlook client to check the autodiscover service:
open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar - Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service.
Please check the Log tab and confirm whether the Autodiscover service is connected successfully. Also confirm if the connection issue happens to all external users when they open Outlook for the 1st time. In Exchange server, please make sure
autodiscover.domain.com has been included in your Exchange certificate which is assigned with IIS service.
Regards,
Winnie Liang
TechNet Community Support

SMTP test to Exchange 2013 failing

Similar Messages

Maybe you are looking for