Psexec error

Hi guys
When I run the command psexec \\ compname gpresult  I get

Open in new window

ERROR: Logon failure: unknown user name or bad password.
gpresult exited on compname  with error code 1.

Open in new window

 At the same time,  At the same time, the command psexec \\ compname ipconfig  is run normally,
User which run both  the commands  is  Domain admin,remote comp is winxp

Please help
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Emmanuel AdebayoGlobal Windows Infrastructure Engineer - ConsultantCommented:
It need authentication against so as to run the GPO as this need to read the registry get the GPO result

You might need to use Runas command with account that have admin priviledge on the remote computer.

i.e runas /user:<username> /netonly cmd

This will ask for the password and take you the command prompt.

You can now run psexec \\ compname gpresult
You can pass a username in PSEXEC as follows:

psexec \\compname -u {domain}\{username} -p {password} gpresult

My oersonal experience is that if you gat error with PSEXEC it is "usually" authentication if the command passed well formed i.e. correct.

Good luck!
nesher13Author Commented:
I did everything as you recommend, but I get the same error.
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

Have you got a space between the \\ and the compname?
nesher13Author Commented:
The computers on which I tried to debug the exec command is what is incomprehensible state, on the one hand, he responds to the ping and psexec \ \compname ipconfig, on the other hand, he does not answer the original command, and also on the VSC. I moved to another home computer (in same OU), which was responsible for VNC and tried to run a command psexec \\compname2  gpresult and get :

Couldn't access The network path was not found.
Make sure that the default admin$ share is enabled on compname2.

Then I checked the group policies, and it turned out that the file and printer sharing exceptions are open to the old ip addresses domain admins. I corrected the addresses and is now waiting for the user restarts the computer
Group policy changes are refreshed every 15 minutes by default, so you do not have to wait for a reboot.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows XP

From novice to tech pro — start learning today.