psexec on xp home

[Guest]

I am trying to access a XP Home computer over a home network using PSEXEC. I
am not having any luck getting past the username and password thing.

Does PSEXEC work on XP Home????

 

[Sooner Al [MVP]]

Well, I had to jump through a few hoops to get it to work accessing one of
my XP Pro boxes over my home LAN. This may or may not be applicable to your
situation..

1. I dropped the XP SP2 Windows Firewall on the target PC.
2. I ran services.msc from the "Start -> Run" command window and configured
the Telnet service for Automatic and started the service.
3. I had to make the change specified in this support article then restart
the Telnet service on the target PC.

http://support.microsoft.com/kb/298060/en-us

4. I could only log on to the remote PC using PsExec as an administrator,
which is probably what you want to do anyway if your installing software,
ie. I ran the command string...

psexec \\norman -u sysadmin cmd

....in order to start the command window on the desktop PC named "Norman" as
user "sysadmin", which is my everyday administrator account. My wife and I
normally log on and run as limited users on our PCs. Note that I have a
sysadmin account on each of my XP Pro machines. I don't know if that will
make a difference or not...

Let us know how it goes for you...I don't have a XP Home machine to test
with so that is the best I can come up with...

Good luck...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...

 

[Sooner Al [MVP]]

I also noted that after I finally got a connection to the remote PC with
PsExec that I could go in and disable the telnet service again. PsExec
installs a service on the remote PC which seems to run in the background
somewhere waiting for the client to connect. Meaning that when PsExec is not
connected the PsExec service is *NOT* listed when you run services.msc but
it is listed when an active connection is running...

Anyway PsExec works, or seems to, as advertised after some work getting it
going...

I still like installing applications that require passwords, changing
listening ports on the application and firewall, etc...etc...etc in person
versus this way, but that is personal preference.

Good luck...

Later...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...

 

[Guest]

Al
Thanks for the reply.
I think that XP Home by nature of its limitations is where my problem is.
Simplified file sharing can't be disabled. So when I try to log into the XP
Home computer, even with a admin name and password, it denies me. If I go
from a XP Home to XP Pro I have no problem.

I guess I will just have to take your suggestion from another post and do it
the old fashoned way and install what I want locally.