Hi Doug i used the 1.11 version. I tried the -i one time with a 1.06 version too but same effect. -n: Both try to start the service whether they connect or not, but in this example whit PsExec > C:\\Users\\DarthVader>psexec \\\pcname > -u notavailableusername -p senselesspassword -n 1 cmd > > PsExec v1.98 - Execute processes > remotely Copyright (C) 2001-2010 Mark > Russinovich Sysinternals - > www.sysinternals.com > > Timeout accessing pcname. he trys only 1 second to connect and changes the message to "timeout accessing pcname." but with PAExec > C:\\Users\\DarthVader>paexec \\\pcname > -u notavailableusername -p senselesspassword -n 1 cmd > > PAExec v1.12 - Execute Programs > Remotely Copyright (c) 2012 Power > Admin LLC www.poweradmin.com/PAExec > > > Connecting to pcname... > > Failed to > connect to \\\pcname\ADMIN$. \\\pcname\\ADMIN$. Anmeldung > fehlgeschlagen: unbekannter > Benutzername oder falsches Kennwort. > [Err=0x52E, 1326] Failed to copy > [C:\\Windows\\system32\\paexec.exe] to > [\\\pcname\\ADMIN$\\paexec.exe] -- going > to try to continue anyway. Anmeldung > fehlgeschlagen: unbekannter > Benutzername oder falsches Kennwort. > [Err=0x5 2E, 1326] > > Timeout connecting > to pcname... > > PAExec returning exit code -5 So hey trys to connect -> the timeout occures but paexec dont stop -> it trys further to connect and after ca 25 seconds he sees that he cannot connect. At this point he stops the process cause the timeout already occured. What i wanna say with this is, there is no difference with the command in PAExec between "-n 1", "-n 5", "-n 15", "-n 22" and all the others from 1 to 24. In every case he stops as soon as he realizes that he cannot connect. -i: Do you mean when i set something as a session it should work ? ... When i do so, he connects, but my app, which i wanna start, returns only this exit code -1073741502 (0xC0000142) -s and -cnodel are working fine now =D -clist: Ok i didnt know that i have to write the executable file again after. I thought it would be enough if it stands in the txt-file. But no matter where i write the executable-file in the txt (beginning, somewhere in the middle or at the end) it works. -csrc: So this is like "-c" but i can choose another destination, sounds good.

Hi Doug i used the 1.11 version. I tried the -i one time with a 1.06 version too but same effect. -n: Both try to start the service whether they connect or not, but in this example whit PsExec > C:\Users\DarthVader>psexec C:\\Users\\DarthVader>psexec \\\pcname > -u notavailableusername -p senselesspassword -n 1 cmd > > PsExec v1.98 - Execute processes > remotely Copyright (C) 2001-2010 Mark > Russinovich Sysinternals - > www.sysinternals.com > > Timeout accessing pcname. he trys only 1 second to connect and changes the message to "timeout accessing pcname." but with PAExec > C:\Users\DarthVader>paexec C:\\Users\\DarthVader>paexec \\\pcname > -u notavailableusername -p senselesspassword -n 1 cmd > > PAExec v1.12 - Execute Programs > Remotely Copyright (c) 2012 Power > Admin LLC www.poweradmin.com/PAExec > > > Connecting to pcname... > > Failed to > connect to \\\pcname\ADMIN$. Anmeldung > fehlgeschlagen: unbekannter > Benutzername oder falsches Kennwort. > [Err=0x52E, 1326] Failed to copy > [C:\Windows\system32\paexec.exe] [C:\\Windows\\system32\\paexec.exe] to > [\\\pcname\ADMIN$\paexec.exe] [\\\pcname\\ADMIN$\\paexec.exe] -- going > to try to continue anyway. Anmeldung > fehlgeschlagen: unbekannter > Benutzername oder falsches Kennwort. > [Err=0x5 2E, 1326] > > Timeout connecting > to pcname... > > PAExec returning exit code -5 So hey trys to connect -> the timeout occures but paexec dont stop -> it trys further to connect and after ca 25 seconds he sees that he cannot connect. At this point he stops the process cause the timeout already occured. What i wanna say with this is, there is no difference with the command in PAExec between "-n 1", "-n 5", "-n 15", "-n 22" and all the others from 1 to 24. In every case he stops as soon as he realizes that he cannot connect. -i: Do you mean when i set something as a session it should work ? ... When i do so, he connects, but my app, which i wanna start, returns only this exit code -1073741502 (0xC0000142) -s and -cnodel are working fine now =D -clist: Ok i didnt know that i have to write the executable file again after. I thought it would be enough if it stands in the txt-file. But no matter where i write the executable-file in the txt (beginning, somewhere in the middle or at the end) it works. -csrc: So this is like "-c" but i can choose another destination, sounds good.

Hi Doug i used the 1.11 version. I tried the -i one time with a 1.06 version too but same effect. -n: Both try to start the service whether they connect or not, but in this example whit PsExec > C:\Users\DarthVader>psexec \\\pcname > -u notavailableusername -p senselesspassword -n 1 cmd > > PsExec v1.98 - Execute processes > remotely Copyright (C) 2001-2010 Mark > Russinovich Sysinternals - > www.sysinternals.com > > Timeout accessing pcname. he trys only 1 second to connect and changes the message to "timeout accessing pcname." but with PAExec > C:\Users\DarthVader>paexec \\\pcname > -u notavailableusername -p senselesspassword -n 1 cmd > > PAExec v1.12 - Execute Programs > Remotely Copyright (c) 2012 Power > Admin LLC www.poweradmin.com/PAExec > > > Connecting to pcname... > > Failed to > connect to \\\pcname\ADMIN$. Anmeldung > fehlgeschlagen: unbekannter > Benutzername oder falsches Kennwort. > [Err=0x52E, 1326] Failed to copy > [C:\Windows\system32\paexec.exe] to > [\\\pcname\ADMIN$\paexec.exe] -- going > to try to continue anyway. Anmeldung > fehlgeschlagen: unbekannter > Benutzername oder falsches Kennwort. > [Err=0x5 2E, 1326] > > Timeout connecting > to pcname... > > PAExec returning exit code -5 So hey trys to connect -> the timeout occures but paexec dont stop -> it trys further to connect and after ca 25 seconds he sees that he cannot connect. At this point he stops the process cause the timeout already occured. What i wanna say with this is, there is no difference with the command in PAExec between "-n 1", "-n 5", "-n 15", "-n 22" and all the others from 1 to 24. In every case he stops as soon as he realizes that he cannot connect. -i: Do you mean when i set something as a session it should work ? ... When i do so, he connects, but my app, which i wanna start, returns only this exit code -1073741502 (0xC0000142) -s and -cnodel are working fine now =D -clist: Ok i didnt know that i have to write the executable file again after. I thought it would be enough if it stands in the txt-file. But no matter where i write the executable-file in the txt (beginning, somewhere in the middle or at the end) it works. -csrc: So this is like "-c" but i can choose another destination, sounds good.