List of errors addressed in this document:
You might face these issues while performing one of the following processes. Click on the required process and follow the steps mentioned to avoid these network errors.
You may see the following error messages on your screen while installing image creator component during image creation process.
This error may occur due to the following reasons.
To solve this issue follow the steps mentioned below:
Check for Windows Defender Firewall block.
Note: It is recommended to exclude SMB (file and printer sharing) ports 139 and 445 in your firewall to ensure effective file sharing.
Ensure that Windows Defender Firewall does not block the Imaging computer's accessibility within the network, by following the steps given below.
Check for Antivirus block
If you have any Antivirus software installed in the computer where Imaging is available, ensure that your antivirus settings does not block the computer's network share accessibility.
This error occurs when the DNS Server cannot resolve the host name of the Imaging computer. To solve this DNS issue in the network, ensure that the IP address is updated properly in the DNS server. To check if there is an issue with the DNS server mapping, follow the steps given below.
Go to command prompt in the Endpoint Central/OS Deployer server computer and pingthe Imaging computer, using the command given below.
ping <Imaging computer's host name>
If not, execute the following two commands in command prompt of the target computer to solve the DNS issue.
ipconfig /flushdns - This command will flush the DNS cache available on the computer.
ipconfig /registerdns - This command will update the host record in the DNS server.
In the Endpoint Central/OS Deployer server computer, open command prompt and execute the following command to check connectivity using the Imaging computer's host name,
ping <Imaging computer's host name>
If it is not connecting, execute the same command using the IP address,
ping <Imaging computer's IP address>
If you are able to reach the computer using IP address, specify the Imaging computer's IP address while adding computer details.

To automatically turn on "File and Printer Sharing" settings in the Imaging computer
To manually turn on "File and Printer Sharing" settings in the Imaging computer
If the Imaging computer's OS is below Windows 7, follow the steps mentioned below:
If the Imaging computer's OS is Windows 7 or later, follow the steps mentioned below:
You will need to edit the registry to enable the default administrative share in client machine.
For Servers:
Note: If you cannot find the value in the registry under the exact location (i.e. it does not exist) - No need to add new value. A reboot is necessary for this to take effect.
For Windows Server 2008 R2: In case you have a Windows Server 2008 R2 based domain environment you can enable the Admin$ in your client machine using a Start-Up script.
For Workstations:
Note: If you cannot find the value in the registry under the exact location (i.e. it does not exist) - No need to add new value. A reboot is necessary for this to take effect.
You may see the following error messages on your screen while configuring Image/Driver repositories.
This error may occur due to the following reasons.
To solve this issue follow the steps mentioned below:
Check for Windows Defender Firewall block.
Note: It is recommended to exclude SMB (file and printer sharing) ports 139 and 445 in your firewall to ensure effective file sharing.
Ensure that Windows Defender Firewall does not block the Image Repository computer's accessibility within the network, by following the steps given below.
Check for Antivirus block
If you have any Antivirus software installed in the computer where Image Repository is available, ensure that your antivirus settings does not block the computer's network share accessibility.
This error occurs when the DNS Server could not resolve the Image/Driver Repository computer's host name. To solve this DNS issue in the network, ensure that the IP address is updated properly in the DNS server. To check if there is an issue with the DNS server mapping, follow the steps given below.
Go to command prompt in the Endpoint Central/Os Deployer server computer and pingthe computer where the Image/Driver Repository is created using the command given below.
ping <Image/Driver repository computer's host name>
If not, execute the following two commands in command prompt of the Image/Driver repository computer to solve the DNS issue.
ipconfig /flushdns - This command will flush the DNS cache available on the computer.
ipconfig /registerdns - This command will update the host record in the DNS server.
In the machine where the Endpoint Central/OS Deployer server is installed, open command prompt and execute the following command to check connectivity using the Image/Driver Repository computer's host name,
ping <Image repository machine's host name>
If it is not connecting, execute the same command using the IP address,
ping <Image repository machine's IP address>
If you are able to reach the computer where the Image/Driver repository is available using IP address, specify the computer's IP address to configure the Image/Driver repository.

To automatically turn on "File and Printer Sharing" settings in the computer where the Image/Driver repository is available
To manually turn on "File and Printer Sharing" settings in the computer where the Image/Driver repository is available
If the OS version in the computer where the Image/Driver repository is available, is below Windows 7, follow the steps mentioned below:
If the OS version in the computer where the Image/Driver repository is available, is Windows 7 or later, follow the steps mentioned below:
You will need to edit the registry to enable the default administrative share in client machine.
For Servers:
Note:If you cannot find the value in the registry under the exact location (i.e. it does not exist) - No need to add new value. A reboot is necessary for this to take effect.
For Windows Server 2008 R2: In case you have a Windows Server 2008 R2 based domain environment you can enable the Admin$ in your client machine using a Start-Up script.
For Workstations:
Note: If you cannot find the value in the registry under the exact location (i.e. it does not exist) - No need to add new value. A reboot is necessary for this to take effect.
You may see the following error messages on your screen during Image Creation when the Image Creator Component tries to access the Image repository.
This error may occur due to the following reasons.
To resolve the network error issue follow the steps given below.
Check for Windows Defender Firewall block.
Note: It is recommended to exclude SMB (file and printer sharing) ports 139 and 445 in your firewall to ensure effective file sharing.
Ensure that Windows Defender Firewall does not block the Image Repository computer's accessibility within the network, by following the steps given below.
Check for Antivirus block
If you have any Antivirus software installed in the computer where Image Repository is available, ensure that your antivirus settings does not block the computer's network share accessibility.
This error occurs when the DNS Server could not resolve the Image Repository computer's host name. To solve this DNS issue in the network, ensure that the IP address is updated properly in the DNS server. To check if there is an issue with the DNS server mapping, follow the steps given below.
Go to command prompt in the Endpoint Central/Os Deployer server computer and pingthe computer where the Image Repository is created using the command given below.
ping <Image repository computer's host name>
If not, execute the following two commands in command prompt of the Image repository computer to solve the DNS issue.
ipconfig /flushdns - This command will flush the DNS cache available on the computer.
ipconfig /registerdns - This command will update the host record in the DNS server.
In the computer where the Imaging is performed, open command prompt and execute the pingcommand to check connectivity using the host name,
ping <Image repository computer's host name>
If it is not connecting, execute the same command using the IP address,
ping <Image repository computer's IP address>
If you are able to reach the computer using IP address, configure the share path using the computer's IP address instead of the computer name.

If the computer is reachable with the ping command and the issue still exists, use the following commands to check if the image repository is accessible from the Imaging computer.
net use \\<Hostname>\<sharefolder> /user:<username> <password>
net use \\<Hostname>\<sharefolder> /user:<Domainname>\<username> <password>
net use \\<Ipaddress>\<sharefolder> /user:\<username> <password>
The net use command is used to check the connectivity of the shared folders.
To automatically turn on "File and Printer Sharing" settings in the Image Repository computer
To manually turn on "File and Printer Sharing" settings in your computer
If the OS version in the computer where the Image Repository is created, is below Windows 7, follow the steps mentioned below:
If the OS version in the computer where the Image Repository is created, is Windows 7 or later, follow the steps mentioned below:
You will need to edit the registry to enable the default administrative share in client machine.
For Servers:
Note:If you cannot find the value in the registry under the exact location (i.e. it does not exist) - No need to add new value. A reboot is necessary for this to take effect.
For Windows Server 2008 R2: In case you have a Windows Server 2008 R2 based domain environment you can enable the Admin$ in your client machine using a Start-Up script.
For Workstations:
Note: If you cannot find the value in the registry under the exact location (i.e. it does not exist) - No need to add new value. A reboot is necessary for this to take effect.
You may see the following error messages on your screen during Image Deployment when the server tries to access the Image Repository.
This error may occur due to the following reasons.
To solve this issue follow the steps mentioned below:
Check for Windows Defender Firewall block.
Note: It is recommended to exclude SMB (file and printer sharing) ports 139 and 445 in your firewall to ensure effective file sharing.
Ensure that Windows Defender Firewall does not block the Image Repository computer's accessibility within the network, by following the steps given below.
Check for Antivirus block
If you have any Antivirus software installed in the computer where Image Repository is available, ensure that your antivirus settings does not block the computer's network share accessibility.
This error occurs when the DNS Server could not resolve the Image Repository computer's host name. To solve this DNS issue in the network, ensure that the IP address is updated properly in the DNS server. To check if there is an issue with the DNS server mapping, follow the steps given below.
Go to command prompt in the Endpoint Central/Os Deployer server computer and pingthe computer where the Image Repository is created using the command given below.
ping <Image repository computer's host name>
If not, execute the following two commands in command prompt of the Image repository computer to solve the DNS issue.
ipconfig /flushdns - This command will flush the DNS cache available in the computer.
ipconfig /registerdns - This command will update the host record in the DNS server.
In the machine where you are performing deployment, press Alt+Tab to open command prompt and execute the following command to check connectivity using the host name,
ping <Image Repository machine's host name>
If it is not connecting, execute the same command using the IP address,
ping <Image Repository machine's IP address>

To automatically turn on "File and Printer Sharing" settings in the Image Repository computer
To manually turn on "File and Printer Sharing" settings in the Image Repository computer
If the OS version in the computer where the Image Repository is created, is below Windows 7, follow the steps mentioned below:
If the OS version in the computer where the Image Repository is created, is Windows 7 or later, follow the steps mentioned below:
You will need to edit the registry to enable the default administrative share in client machine.
For Servers:
Note:If you cannot find the value in the registry under the exact location (i.e. it does not exist) - No need to add new value. A reboot is necessary for this to take effect.
For Windows Server 2008 R2: In case you have a Windows Server 2008 R2 based domain environment you can enable the Admin$ in your client machine using a Start-Up script.
For Workstations:
Note: If you cannot find the value in the registry under the exact location (i.e. it does not exist) - No need to add new value. A reboot is necessary for this to take effect.
If you still receive the network errors after reaching out to the computer using IP address, contact support osdeployer-support@manageengine.com.
Keywords: Image creator installation, network errors, image creation, image deployment