I had some similar problems and you will need to get further information, but I can point you in the right direction. There are a number of options available to you on the PC iSeries Access for Windows Remote Command, and it is quite confusing. In summary, the issue relates to the fact that the remote command is running under a job which is a service. I suspect that there are some user ID issues. I eventually gave up with my situation and created a job on the PC (not running as a service) which communicated with the iSeries with a data queue. I look forward to the wisdom of others in this matter which could help me out as well.