I am trying to do remote PGP calls to a couple of designated systems that are running Windows XP. I have an executable on the local machines that I call and pass the command line that I would like run. The exe then parses the command line and modifies it as needed and then runs the PGP command using PGP Command Line 9.0.1. The calls works perfectly when being called from a remote system IF the file the is being encrypting\decrypted it is the local drive of the machine the command is being passed too, however, if the files are located on the network and are being called in this fashion PGP cannot find the file, nor can my app see files that are on the network (my app does a check to ensure the encrypted\decrypted file is there after PGP runs, PGP seems to return 0 even when files arent successfully encrypted\decrypted not always but I need it to be consistent). I can run the exact same command locally on the designated system in a command prompt and it will encrypt\decrypt the file just fine if it is on the network or the local drive. When calling psexec I am passing the username and password and I know they are being passed because I can initiate the call from my machine which has a different user account then the designated machine that will run the command. The network drive that is trying to be accessed is also mapped with the same userID and password as the designated machine is logged in with. Here is an example of the command line I use when initiating the call using psexec.
psexec.exe -i \\<MachineName> -u "<User>" -p "<Pass>" <myExe> <PGP Command>