FoBoT
No Lifer
anybody know what ports are required for schtasks.exe (the windows command line task scheduler) to work on remote PC's?
i can set the task from another comptuer on the targets LAN, but not through our WAN. the password isn't getting passed to the target, so the task is created, but fails when it runs due to the missing password
if i go into the console on the target PC and add the password, it works
so my guess is our WAN is blocking the mechanism that passes the password to the target machine. but i don't know for sure, i just doesn't fricking work
maybe i'll put that port monitor software on my machine and see if it pops when i run schtasks.exe
thanks for reading
*edit* it appears to only be using 445 , so i guess it isn't a ports/firewall issue
sigh , i give up . me go home now
i can set the task from another comptuer on the targets LAN, but not through our WAN. the password isn't getting passed to the target, so the task is created, but fails when it runs due to the missing password
if i go into the console on the target PC and add the password, it works
so my guess is our WAN is blocking the mechanism that passes the password to the target machine. but i don't know for sure, i just doesn't fricking work
maybe i'll put that port monitor software on my machine and see if it pops when i run schtasks.exe
thanks for reading
*edit* it appears to only be using 445 , so i guess it isn't a ports/firewall issue
sigh , i give up . me go home now
