Re: Logon Failure - using Taskkill.exe

On Mon, 11 Jul 2005 17:41:02 -0700, usasma <usasma@xxxxxxxxxxxxxxxxxxxxxxxxx>
wrote:

>"Chuck" wrote:
>
>> On Mon, 11 Jul 2005 16:20:04 -0700, usasma <usasma@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> wrote:
>>
>> >I have 2 peer-to-peer networks, both using a mix of XPPro and XPHome.
>> >
>> >When I try to use taskkill.exe to kill a process on another system (from an
>> >XPPro machine) I first get asked to enter the password for the system that
>> >I'm on - rather than the one on the system that I'm trying to kill the
>> >process on. Once I do that, I get the following error message:
>> >
>> >Error: Logon failure: Unknown user name or bad password.
>> >
>> >Here's an example of the syntax that causes this:
>> >
>> >taskkill /s cindy /f /im notepad.exe /t
>> >
>> >When I press enter, I get this....
>> >
>> >Type the password for PUTZ\FUBAR:
>> >
>> >This is the machine I'm working on - not the one I'm trying to use taskkill
>> >on.
>> >
>> >When I enter the password and press return, I get the above error message?
>> >
>> >Since I'm a networking neophyte, nothing has been done with these networks
>> >other than to set them up with the Windows Networking Wizard.
>> >
>> >Any help would be sincerely appreciated!
>> >
>> >- John
>>
>> John,
>>
>> If you enter "taskkill /?", you'll note another parameter, "U", as in
>> /U [domain\]user
>>
>> Try adding that parameter, with an account on the target computer, to the
>> command.

>Thanks Chuck!
>
>I don't have domains - we use workgroups. I've replaced the domain name
>with the workgroup name and get the same error message. I also used just the
>user name - without the domain - and got the same error. I've tried all of
>these examples at least 3 times in case I messed up the passwords.
>
>I even went to the extent of creating an account named ED with a password of
>ED so that I couldn't mess it up - and still no luck!
>
>Could this possibly have something to do with permissions, etc?
>
>Thanks!
>
>John

John,

Is the target running XP Home or Pro? If XP home, remember Guest is the only
network capable account, and it won't provide administrative access (unless you
want to hack XP Home).

If XP Pro, try using the name of the target computer, instead of the workgroup
name - it has to be an account defined on the target, with workgroup
authentication.

--
Cheers,
Chuck, MS-MVP [Windows - Networking]
http://nitecruzr.blogspot.com/
Paranoia is not a problem, when it's a normal response from experience.
My email is AT DOT
actual address pchuck mvps org.
.

Relevant Pages

  • Re: how to connect puters via crossover cable!?
    ... it is a domain profile and when you moved it to a workgroup you ... your local account doesn't have the SID necessary ... >I tried to rename my computer (XP pro) and got an error ("Computer Name ... >hell I'm doing when it comes to networking, ...
    (microsoft.public.windowsxp.general)
  • Re: how to connect puters via crossover cable!?
    ... > it is a domain profile and when you moved it to a workgroup you ... your local account doesn't have the SID necessary ... >>hell I'm doing when it comes to networking, ... >>> to set up your user name for the Windows 2000 computer on the XP ...
    (microsoft.public.windowsxp.general)
  • Domain/Workgroup Admin Password
    ... >between her account and your new account... ... >which workgroup you have set up under networking. ... >to peer network will fail. ...
    (microsoft.public.win2000.new_user)
  • Domain/Workgroup Admin Password
    ... between her account and your new account... ... which workgroup you have set up under networking. ... to peer network will fail. ...
    (microsoft.public.win2000.new_user)
  • Re: Trust relationship between this workstation and Primary Domain
    ... it, with a new computer ID, a new workgroup ID, but again to no avail. ... password policy, renamed admin account, automatic updates are controlled by ... * PLEASE post all messages and replies in the newsgroups ... "Workstation ...
    (microsoft.public.win2000.networking)
Loading