0

GOAL

Attempting to access XP_BOX on the LAN from a Windows 10 box:

CONFIGURATION

PsExec v2.2 installed on Win10 from Microsoft

OBSERVATION:

C:\> psexec \\XP_BOX -u XP_BOX\username  -c ipconfig

Password:
Couldn't access XP_BOX:
Access is denied

UPDATE TO OBSERVATION

Observed successful console-redirection: ran the XP_BOX command prompt on the Win10 box as if the command prompt were running locally

psexec \\XP_BOX cmd

Interestingly enough: I could not list directories of 'net use' configured drives: a question for another thread.

Succesfully returned the ipconfig command:

win10>psexec \\XP_BOX ipconfig

Windows IP Configuration


Ethernet adapter LAN:

        Connection-specific DNS Suffix  . : lan
        IP Address. . . . . . . . . . . . : 192.168.8.112
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.8.1
ipconfig exited on salve with error code 0.

WHAT HAS BEEN TRIED

I am able to share out a folder from the XP_BOX

C:\>net use Q: \\XP_BOX\Dropbox
The command completed successfully.

I have verified that XP_BOX resolves to a LAN ip address via ping.

I have tried this command with the XP_BOX off and it hangs (expected because of no response from XP_BOX).

I have tried the secpol update procedure on the XP_BOX:

Start>Run>secpol.msc

Navigate to

Local Policies>Security Options

Set the policy "Network Access: Sharing and security model for local accounts" to (Just hit OK: Don't close this out as we will be changing it back).

Guest only – local users authenticate as Guest

Open a command box and run (Dont close this either)

gpupdate /force

Go back and set the policy "Network Access: Sharing and security model for local accounts" back to

Classic - local users authenticate as themselves

Again run

gpupdate /force

Test from Win10 box

Reboot

Test from Win10 box

QUESTIONS

If you have had success sending psexec command from a WIN10 to an XP box please state this in your response. Because there are many versions of Windows, it is important to frame any comments so as to understand the context.

  1. What can be done to diagnose the root-cause of the error message?
  2. What corrective action can be tested?
  3. Is it possible to run psexec from win10 to an XP box?
gatorback
  • 1,091

0 Answers0