PSinfo gives The network path was not found.

I have a variation on this issue - I have an internal tool that uses PSInfo to gather info before performing a process.  I'm attempting to collect info via PSInfo on that machine via a DNS A record that is not the same as the name of the machine.  I currently get the message "The network path was not found" when attempting to run PSInfo against the A record.  When I run the command against the actual name of the machine, PSInfo, works as expected.

I'm of the understanding that this is likely a limitation with Windows Remote Registry service  - assuming that by default, it can only be addressed by the machine's name.  I'm looking for a way to fake PSInfo into working with the A-record name instead of the machine's actual node name. 

Originally posted by namrehto Well since the original error message was Could not connect to CPQ379-03: The network path was not found. is the machine actually directly accessible via that name?

Originally posted by namrehto Exact command typed: psinfo -s \\CPQ379-03 -u administrator -p password Strictly speaking this should read psinfo \\CPQ379-03 -u administrator -p password -s If that doesn't help do check out the topics in *** FAQ: Common PSTools Issues ***, in particular: What are the minimum requirements to run PSTools commands? Please read PsExec could not start. Although it is about psexec, the requirements to run any PSTools command are pretty similar.

I've have tried running psinfo on a list of remote machines that have the same build, same OS, patch level and configs.  However, I encountered the following on some of the machines and the rest were successfully.