Building an Exchange Server in a Local Network Environment(ローカルネットワーク環境でのExchangeサーバー構築について)

Question

We would like to build an Exchange server on our local network, where connection to the Internet is prohibited, to send and receive e-mail using Outlook between client terminals.

How can we build the environment?

Assumptions (what we want to do)

We want to build an Exchange server and client terminals in a local network where external connection to the Internet is prohibited.

We want to build an ExchangeServer in the local network, access Exchange from other terminals, and send/receive e-mail between terminals in the local network.

Environment

Build an Exchange server with Exchange Server 2019.

Use Outlook of Office365 from client terminals

Current Status

The current situation: - Exchange 2019 server is built, Office365 is installed on the Exchange server, and Outlook is used to send/receive email (between own terminals).

When I started Outlook on the client terminal and selected the above Exchange server as the connection destination at the time of Outlook initialization,

　The following error occurs

Cannot start Microsoft Outlook, cannot open Outlook window. Failed to log on to Microsoft Exchange.

Communication (ping) between the Exchange server and the client device is possible.

Exchange server and client terminal are under the same domain

インターネットへの接続が禁止されているローカルネットワーク上で、Exchangeサーバーの構築してクライアント端末同士のOutlookによるメール送受信を行いたいのですが、環境構築中に下記のエラーが発生しております。

どのようにすれば環境を構築できるでしょうか。

■前提（やりたい事）

・インターネットへの外部接続が禁止されているローカルネットワークにExchangeサーバーとクライアント端末を構築する

・ローカルネットワークにExchgenServerを建て、他の端末からExchangeへアクセスして、ローカルネットワーク内の端末同士でのメール送受信を行う

■環境

・Exchange Server2019によりExchangeサーバーを構築

・クライアント端末からOffice365のOutlookを利用

■現在の状況

・Exchange2019サーバーを構築し、ExchangeサーバーにOffice365をインストールしてOutlookによるメール送受信（自端末同士）を試行したところ成功

・クライアント端末のOutlookを起動し、Outlook初期設定時の接続先に上記のExchangeサーバーを選択したところ、

　下記のエラーが発生

「Microsoft Outlookを起動できません。Outlookウィンドウを開けません。このフォルダーのセットを開けません。Microsoft Exchangeへのログオンに失敗しました。」

・Exchangeサーバーとクライアント端末の通信（ping）は可能

・Exchangeサーバーとクライアント端末は同じドメイン配下

Answer 1

Hi @sada_165,

When I started Outlook on the client terminal and selected the above Exchange server as the connection destination at the time of Outlook initialization

Can you post a screenshot of this step (select Exchange server as connection destination)?

If you have created a mailbox in Exchange Admin Center and have Exchange autodiscover configured correctly, you do not need to manually enter the Exchange server information to connect to Exchange.

Example:

---

If the above does not work for you, please run the following cmdlet in Exchange Management Shell and post the result (Don't forget to hide your personal information):

Get-ClientAccessService | fl AutoDiscoverServiceInternalUri

Example:

By default the value would be like: https://<Exchange server FQDN>/Autodiscover/Autodiscover.xml

which can be resolved to your Exchange server and accessed from Outlook client.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment". 

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Thank you for your answer.

I have implemented the command you gave me,
The first time was not successful with the following error that the cmdlet was not recognized.


----------------

[PS] C:\Windows\system32>Get-ClientAccessService | fl AutoDiscoverServiceInternalUri

Get-ClientAccessService : The term 'Get-ClientAccessService' is not recognized as the name of a cmdlet, function, script file, or operable program.
The term 'Get-ClientAccessService' is not recognized as a cmdlet, function, script file, or operable program name. Make sure the name is written correctly, and if it contains a path, make sure the path is correct.
If the path is included, make sure it is correct and try again.
Occurrence Location Line:1 Character:1
+ Get-ClientAccessService | fl AutoDiscoverServiceInternalUri
+ ~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : ObjectNotFound: (Get-ClientAccessService:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Get-ClientAccessService | fl AutoDiscoverServiceInternalUri

-------------------

I just added an email account from Exchange Admin Center to View-Only Organization Management,
The cmdlet now works correctly and I am able to connect to Outlook from the client terminal.


Thank you.