|
Doing some side-by-side comparisons with PsExec, and so far not being able to get PAExec to work at all :( Active directory environment, executing PAExec on a Windows 7 laptop, trying to access a Windows 2008 R2 server. Simple command: PAExec \\machinename\ cmd.exe I get "Failed to open remote pipes" as a response after a few seconds, and it just sits and hangs forever. I have to Ctrl-C to get my prompt back, then sometimes it exits with -9, and sometimes fails to clean up and exits with -9. PsExec executes the above command with no issues. So, I tried specifying the user, in case the 'automatic' use of the local user was somehow different: PAExec \\machinename\ -u DOMAIN\User.Name -p P@$5w0Rd cmd.exe Same results. Again, PsExec executes the above command with no issues. What should I look for here? |
|
Open inbound port TCP 139 and 445 on \machinename Nice idea, but not an issue. We don't run firewalls at all in the closed network. Besides, I don't believe PsExec would work, either, if these were blocked.
(18 Nov '14, 08:16)
Thalgor
|
Hmmm, above had double slashes in front of the machine name and a single behind...and between DOMAIN and User.Name. The forum seems to have filtered them out :)
EDIT: Okay, I got the slashes back in...silly escape sequences!