Fixing the error “The network path was not found” on a new witness server

Share this:

In situations where a new server is built to be used as witness server the administrator can get the error “The network path was not found” during the DAG creation. In this Tutorial we are going over why this happens and how we can avoid it.


Let’s use a scenario where we are building a brand new environment and we have our Exchange Servers and a brand new witness server ready to go. During the DAG creation we define our witness server and then we hit save. Note: The witness server was installed using default settings, the installation process was similar to this Tutorial: , after that we assigned a static IP and joined to the domain. image11 The following error message may show up on your environment, click on OK and let’s analyze the root cause of the issue. image31_thumb In order to understand the issue we need to list all features installed on the witness server after the OS deployment and we can do that using the following cmdlet.

Get-WindowsFeature | Where { $_.InstallState –eq ‘Installed’ }

image2 If we create a new share on the same server, in the example below we are creating a share of a Temp folder, make sure that you remember to remove such share afterwards. image8 Now that we have shared a folder on this server, we will run the same cmdlet that we have just run and we will notice that we have two new features on the OS when compared with the previous attempt, which are: File and iSCSI Services e File Server and these are the features that must be enabled on the witness server before running the DAG wizard. image5 Long story short, after commissioning a new witness server make sure that you enable those features or at least create a share to avoid that error message on the DAG wizard.


In this Tutorial we worked on the issue The network path was not found when using a new witness server on a DAG, the procedure listed here can be used for troubleshooting when that message appears. Bear in mind, that is not the only solution for that error message.

Written by Anderson Patricio

Anderson Patricio is a Canadian Exchange Server MVP and MCSM (Solutions Master) and he contributes to the Microsoft Community with articles, tutorials, blog posts, forums and book reviews. He is a regular contributor at, and (Portuguese).