FQDN on EHLO for External

If I telnet to my exchange 2013 server and do an EHLO it returns the local server name and not the external FQDN.

Mxtoolbox.com flags this as a problem as it doesn't match my reverse DNS which is to the external FQDN.

How do I change it to return my external FQDN ?

thanks

January 11th, 2013 10:16am

Hello,

You can modify the "Fqdn" parameters in the Set-ReceiveConnector cmdlet:

http://technet.microsoft.com/en-us/library/bb125140.aspx

Thanks,

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Free Windows Admin Tool Kit Click here and download it now
January 14th, 2013 3:00am

Thanks, eventually managed to do it.

For anyone else with a single Exchange 2013 server solution then you'll need to disable 'exchange server authentication' on the 'default frontend' receive connector before you can set the FQDN.

I've done that and mailflow is fine in and out.


  • Edited by ubiquitas Monday, January 14, 2013 12:20 PM
  • Marked as answer by ubiquitas Monday, January 14, 2013 12:20 PM
January 14th, 2013 12:19pm

Thanks, eventually managed to do it.

For anyone else with a single Exchange 2013 server solution then you'll need to disable 'exchange server authentication' on the 'default frontend' receive connector before you can set the FQDN.

I've done that and mailflow is fine in and out.


  • Edited by ubiquitas Monday, January 14, 2013 12:20 PM
  • Marked as answer by ubiquitas Monday, January 14, 2013 12:20 PM
Free Windows Admin Tool Kit Click here and download it now
January 14th, 2013 12:19pm

Great post, thank you to all. For reference, the syntax used to set the FQDN is as follows:

Get-RecieveConnector "SERVER01\Default Frontend SERVER01" | Set-RecieveConnector -fqdn "remote.mydomainname.com"

Amend as required.

June 24th, 2013 9:27am

Thanks,

This is great article help for me, I was looking for this from so many days

Regards,

Damodar

Free Windows Admin Tool Kit Click here and download it now
September 30th, 2013 1:02pm

There is a typo in the "Set-ReceiveConnector" on your post... Just an FYI.

Once I corrected the spelling I received the following error:

If the AuthMechanism attribute on a Receive connector contains 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
"EXCHANGE.home.lan", the NetBIOS name of the transport server "EXCHANGE", or $null.
    + CategoryInfo          : InvalidOperation: (EXCHANGE\Default Frontend EXCHANGE:ReceiveConnector) [Set-ReceiveConn
   ector], InvalidFqdnUnde...erAuthException
    + FullyQualifiedErrorId : [Server=EXCHANGE,RequestId=092580ef-d459-4982-a984-72c71fb87dee,TimeStamp=10/9/2014 12:5
   7:09 PM] [FailureCategory=Cmdlet-InvalidFqdnUnderExchangeServerAuthException] 949351FC,Microsoft.Exchange.Manageme
  nt.SystemConfigurationTasks.SetReceiveConnector
    + PSComputerName        : exchange.home.lan

Does anyone have suggestions?

Thanks,

Ray

October 9th, 2014 1:01pm

Hi Ray

Have you figured this out?

Vik

Free Windows Admin Tool Kit Click here and download it now
April 28th, 2015 4:13pm

Vik,

You can change the name through the mail flow/receive connectors/scoping (scroll down) in the Exchange Admin Center.   I left it as is since it was not that big of an issue for me.  If there are clear directions out there on how to do it, I might give it another shot. 

Are you looking to do the same?

Thanks,

Ray

April 28th, 2015 10:18pm

FYI - Just tried again with the advice above about un-ticking the 'exchange server authentication' check box and it appears to have worked.  Make sure you do this on "Default Frontend servername".  Go to the scoping button on the left and scroll down to where you see the local server name and replace with your external DNS name. 

Reboot your computer and test.

I still get my local server name for the EHLO as I use a smart host for outbound mail.  Will figure this out another day unless someone else has any advice they can share.

Thanks,

Ray


Free Windows Admin Tool Kit Click here and download it now
April 28th, 2015 10:35pm

OK. For outbound mail, repeat the same steps, but for your send connector.  Don't forget to reboot before testing.  It worked for me.

Ray

April 28th, 2015 11:46pm

FYI - Just tried again with the advice above about un-ticking the 'exchange server authentication' check box and it appears to have worked.  Make sure you do this on "Default Frontend servername".  Go to the scoping button on the left and scroll down to where you see the local server name and replace with your external DNS name. 

Reboot your computer and test.

I still get my local server name for the EHLO as I use a smart host for outbound mail.  Will figure this out another day unless someone else has any advice they can share.

Thanks,

Ray


  • Edited by Ray Wooge Wednesday, April 29, 2015 2:34 AM
Free Windows Admin Tool Kit Click here and download it now
April 29th, 2015 2:33am

FYI - Just tried again with the advice above about un-ticking the 'exchange server authentication' check box and it appears to have worked.  Make sure you do this on "Default Frontend servername".  Go to the scoping button on the left and scroll down to where you see the local server name and replace with your external DNS name. 

Reboot your computer and test.

I still get my local server name for the EHLO as I use a smart host for outbound mail.  Will figure this out another day unless someone else has any advice they can share.

Thanks,

Ray


  • Edited by Ray Wooge Wednesday, April 29, 2015 2:34 AM
April 29th, 2015 2:33am

at EXCHANGE 2013, from my understanding , we need to change the fqdn at SendConnector, NOT ReceiveConnector ,right?
  • Edited by Feng_G 4 hours 55 minutes ago
Free Windows Admin Tool Kit Click here and download it now
August 12th, 2015 10:34pm

at EXCHANGE 2013, from my understanding , we need to change the fqdn at SendConnector, NOT ReceiveConnector ,right?
  • Edited by Feng_G Thursday, August 13, 2015 2:32 AM
August 13th, 2015 2:32am

I also change on my receive connectors, otherwise the FQDN will show up. You can observe this by running a sniffer on the network and monitor your mail server IP.  The banner will show your FQDN unless you change it on your receive connector.  There are other online scanners out there that will scan the Internet for this information in which I don't agree with.
Free Windows Admin Tool Kit Click here and download it now
August 13th, 2015 10:02am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics