The problem of psexec and its solution

C:\>psexec.exe \\192.168.1.142 cmd

PsExec v1.98-execute processes remotely
Copyright (C) 2001-2010 Mark Russ Inovich
sysinternals-www.sysinternals.com

couldn ' t access 192.168.1.142:
Logon failed: Unknown user name or bad password.

c:\>psexec.exe \\192.168.1.142 cmd-u administrator-p

Yang PsExec V1.98-execute Processes remotely
Copyright (C) 2001-2010 Mark Russinovich
sysinternals-www.sysinternal s.com

couldn ' t access 192.168.1.142:
Logon failed: Unknown user name or bad password.

c:\>

On the 192.168.1.142, modify a configuration as follows:

To "classic"

Again PsExec:

C:\>psexec.exe \\192.168.1.142 cmd

PsExec v1.98-execute processes remotely
Copyright (C) 2001-2010 Mark Russ Inovich
sysinternals-www.sysinternals.com

couldn ' t access 192.168.1.142:
The network name could not be found. Make

sure this default admin$ share is enabled on 192.168.1.142.

C:\>

Open admin Share on 192.168.1.142:

C:\>net share

share name   resource                        annotation

------------------------------------------------------------------- ------------
ipc$                                         remote IPC
command completed successfully.


c:\>net share admin$
admin$ shared success.


c:\>net share

share name   resource                        annotation

---------------------------------------------------------- ---------------------
admin$       C:\WINDOWS                      remote management
ipc$                                         remote IPC
command completed successfully.


c:\>

Again PsExec:

C:\>psexec.exe \\192.168.1.142 cmd

PsExec v1.98-execute processes remotely
Copyright (C) 2001-2010 Mark Russ Inovich
sysinternals-www.sysinternals.com


Microsoft Windows XP [version 5.1.2600]
(C) All rights reserved 1985-2001 Microsoft Corp.

C:\windows\system32>

It worked.

Summarize:

1, CONFIGURED as "classic"

2, open admin share