Error code 80070035: Error in Setting the Password. The Network Path Not Found

Error code 80070035: Error in Setting the Password. The Network Path Not Found

Issue description 

When creating a user or resetting a password in ADManager Plus, you may see the error message Error in setting the Password. The network path is not found - Error Code: 80070035. This indicates that ADManager Plus is unable to connect to the target machine, typically a Domain Controller, to complete the password operation.

Possible causes   

  • DNS resolution issues: The DNS server used by the ADManager Plus machine may not be pointing to the correct DC, especially if they are in different domains or networks.

  • Firewall blocking port 445: A firewall may be blocking port 445 (SMB - Server Message Block) between the ADManager Plus server and the target DC, preventing the password operation from completing.  

Prerequisites   

  • Ensure you have administrative access to ADManager Plus to modify settings.

  • Identify the IP addresses and DNS names of the ADManager Plus server and DCs.

  • Ensure you can manage firewall rules between the ADManager Plus server and the DCs.

Resolution 

Step 1: Verify DNS resolution   

  1. Open Command Prompt on the ADManager Plus server.

  2. Run the following commands to check name resolution to the DC:

    • Ping <DomainControllerName>. Replace <DomainControllerName> with the DC's NetBIOS name.

    • Ping <DomainControllerFQDN>. Replace <DomainControllerFQDN> with its fully qualified domain name (e.g., dc1.example.com).

    • Ping <DomainControllerIPAddress>. Replace <DomainControllerIPAddress> with its IP address.

  3. If the ping command fails or returns an incorrect IP address, there is a DNS resolution issue.

Fix DNS resolution issue:

  1. Open the network adapter settings on the ADManager Plus server.

  2. Ensure the DNS server points to one that can resolve the DC's name.

  3. If needed, add an entry for the DC in the hosts file (C:\Windows\System32\drivers\etc\hosts).

Step 2: Verify Firewall settings   

  1. Check Windows Firewall on both the ADManager Plus server and the DC:

    1. Open Windows Defender Firewall settings.

    2. Ensure there are no rules blocking inbound or outbound traffic on port 445 (SMB).

    3. If necessary, create an inbound/outbound rule allowing traffic on port 445.

  1. Check hardware Firewalls (if applicable):

    1. Verify that port 445 is not blocked between the ADManager Plus server and the DC.

    2. Modify firewall rules to allow SMB traffic if required.

 Step 3: Test SMB Connectivity   

  1. Open File Explorer on the ADManager Plus server.

  2. Attempt to access the DC by entering the following paths in the address bar:

    • \\<DomainControllerName>\C$. Replace <DomainControllerName> with the Domain Controller’s NetBIOS name.

    • \\<DomainControllerIPAddress>\C$. Replace <DomainControllerIPAddress> with its IP address.

  3. If access is denied or fails, there may be firewall restrictions or permission issues preventing SMB connectivity.

 Tips   

  • Ensure all servers use the same DNS configuration for consistent name resolution.

  • Maintain documentation of firewall rules related to ADManager Plus to track changes.

  • Regularly test network connectivity between ADManager Plus and DCs to identify issues early.

 Related topics and articles   

 How to reach support

  If the issue persists, contact our support team here

                  New to ADSelfService Plus?