Make Exchange 2016 Autodiscover work just on the LAN

Discussion in 'Application Software' started by cbsvitzer, Oct 11, 2016.

  1. cbsvitzer

    cbsvitzer MDL Novice

    Feb 4, 2010
    44
    20
    0
    #1 cbsvitzer, Oct 11, 2016
    Last edited: Oct 11, 2016
  2. Scopeman

    Scopeman MDL Novice

    Jul 29, 2009
    20
    8
    0
    #2 Scopeman, Oct 11, 2016
    Last edited by a moderator: Apr 20, 2017
  3. cbsvitzer

    cbsvitzer MDL Novice

    Feb 4, 2010
    44
    20
    0
    #3 cbsvitzer, Oct 11, 2016
    Last edited: Oct 11, 2016
    (OP)
    @Scopeman

    Thank you for your advice. This is all working fine when the Windows clients have joined the domain.

    The problem is, that if the clients haven't joined the domain (working as a workgroup computer which I prefer in a small company) then mydomain.dk does not point to the Exchange server and thus SERVER.mydomain.dk cannot be resolved even though the client pcs DNS server have been set to the IP address of the Exchange server!

    Any suggestion would be greatly appreciated
     
  4. Threat

    Threat Lord of the Files

    Feb 23, 2014
    1,064
    836
    60
    This part confuses me ... is your setup a single server running Active Directory, DNS and Exchange all on a single server? Really not a good idea if that's the case.

    If not then why would you point client DNS servers at a server that is not running DNS ... nothing will resolve.

    Can you ping the address autodiscover.damese.dk from your client?

    What mydomain.dk points to is irrelevant to what SERVER.mydomain.dk will point it ... DNS can point them to different IP's.

    I know these questions may seem simple but without more information we are going to struggle to guess setup.

    Even on a small company, it would be better to join them to a domain so you can control the various settings from the server via GPO's etc.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. cbsvitzer

    cbsvitzer MDL Novice

    Feb 4, 2010
    44
    20
    0
    Yes, the setup is a single server running AD, DNS and Exchange. This setup has been working fine for years in small companies employing just a few people.

    And no, I could not ping SERVER.damese.dk on the Windows 7 client.

    However I repeated the experiment on a Windows 10 client, and now I can ping both SERVER.damese.dk and damese.dk which resolves to the server

    I have to look into it again, thanks
     
  6. cbsvitzer

    cbsvitzer MDL Novice

    Feb 4, 2010
    44
    20
    0
    #6 cbsvitzer, Oct 13, 2016
    Last edited by a moderator: Apr 20, 2017
    (OP)