Author: eugenekwalker
Subject: PSEXEC 1.98 delay
Posted: 10 March 2014 at 9:00pm
Hello,
Subject: PSEXEC 1.98 delay
Posted: 10 March 2014 at 9:00pm
Hello,
We are running XP and Win 7 remote boxes. The PSEXEC command 1.98 works as well as it always had. Win7 boxes causing 2 issues.
psexec -i -h -u userid -p password \\ipaddress c:\folder\program.exe
This works great on the Windows XP boxes...Access denied on the Win7 boxes when either windows firewall or Kaspersky firewall on. If I enable both the firewall and Kaspersky, the process works (25 seconds which is too long, XP boxes are 3 sec). Windows firewall only, traffic gets through (25 seconds which is too long, XP boxes are 3 sec).
Kaspersky 10 apparently has a built in firewall, but I am not sure if it conflicts with the Windows firewall and somehow allowing traffic.
WF and KAS on....traffic gets through. WF only, traffic gets through. WF and KAS off, NO traffic getting through. Need KAS only, no traffic....Guessing there is a rule for Kaspersky which the network guys are trying to figure out. But if i remove Kas all together, why would it work with the WF on and not off?
#2)...the 25 seconds mentioned above. Is there something in Win7 at the "front door" that does a more extensive authentication which would cause such a delay, or is it just the constrats in the firewall issue (#1)..
1) added the token in the registry
2) killed the UAC
3) networking is supposed to take care of a Kaspersky rule.
4) running with the -h or without does not make a difference
5) running with the sessionID (from query session) does not make a difference.
thanks for the help, this has been kicking my tail for the past week.
gene