Error 1605: Failed to create remote working directory

[ombra17]

Hi Team,

I’m receiving the following error message:

Windows Update Messages

Error 1605: Failed to create remote working directory. Please check permissions on the target computer and verify your working directory path in Tools > Settings. HRESULT -2147024829: The network name cannot be found.

– 09:56:17

All Messages

Tue-09:56:17> Windows Update: Error 1605: Failed to create remote working directory. Please check permissions on the target computer and verify your working directory path in Tools > Settings. HRESULT -2147024829: The network name cannot be found.

Tue-09:56:16> Windows Update: Attempting to initiate Windows Update (Action: Search for updates. Server selection: Windows Update) …

Tue-09:56:16> Windows Update: Establishing connection…

Tue-09:56:16> Windows Update: Initializing…

Tue-09:56:16> Windows Update: Queued…

I do have local permissions on the local machine.

Your help would be greatly appreciated.

[doug]

ombra17 – The key information in the error here is “The network name cannot be found.” It sounds like either you have entered the name of computer that does not exist on your network, or perhaps you have mis-typed the name, or it could be a DNS issue or a DNS suffix issue. It could also be a non-existent remote working directory path on the target computer. Verify your working directory path in ‘Tools > Settings > Remote Execution > Remote Working Directory’. Make sure that path exists. In particular make sure the drive letter exists. So if your remote working directory is set to ‘Q:\Program Files\BatchPatch’, but there is no Q: drive on the computer, the ‘network name cannot be found’ error will be generated. If the Q: drive exists, then BatchPatch will be able to create the directory successfully (or if it cannot because of a permissions problem or something like that, then we would see a different error). However, the bottom line is that BatchPatch can’t get to or create the network path that is specified in the ‘remote working directory’ field.

If you take that same computer name and go to the cmd prompt and type “ping <ComputerName>” and it can’t find the computer, BatchPatch also will not be able to find it. You might need to use the FQDN or have your network adapter automatically append the appropriate DNS suffix. Alternatively you could use the IP address instead of the name.

-Doug

[twilliamsj]

Im getting this same error. I used the directory to import the machines, and BP is able to ping the machines, but not able to create this working directory. I have found that if i turn off the firewall i get through to the machine. what is the exception that i need to put into the firewall to allow this to work?

-Thomas

[doug]

Using BatchPatch with Windows Firewall

[ombra17]

Thanks Doug.

I am able to ping the computer both by IP and DNS name. When I enter the IP address in BatchPatch I all receive the same error message. This is only happening for a select few devices.

Thanks for your assistance.

[doug]

ombra17 – What happens when you try to access \\targetComputer\admin$ and \\targetComputer\c$ from the BatchPatch computer? This is where BatchPatch is throwing the error. BatchPatch tries to access \\targetComputer\c$ so that it can create the remote working directory. If you try to access these locations manually by going to

start > run > \\targetComputer\C$
start > run > \\targetComputer\admin$

What happens?

[Author]

Posts