Re: Simple user/password management?

From: Steven L Umbach (n9rou_at_nospam-comcast.net)
Date: 07/07/05


Date: Thu, 7 Jul 2005 13:16:30 -0500

I just tried this and it worked for me. I changed a local password on an XP
Pro SP2 computer from a Windows 2000 Pro computer. I did have initial
difficulty and found that you must first be logged onto your computer with
the correct logon/password that exists on the remote computer and then use
control-alt-delete as you describe. If you first change your password on
your computer it will not work. In other words change the password on the
remote computer first and then on your local computer.

If you continue to have difficulty then possibly you have firewall or ipsec
policy configured on the remote server that is not allowing the necessary
traffic for the password change and checking the firewall log for dropped
traffic [after enabling logging] may help. Also check the security log in
Event Viewer on the Windows 2003 server for any pertinent events that may
help troubleshoot the problem which is what I did as I initially found
failed logon attempts recorded from the remote computer/user when I tried to
change the password remotely. By default Windows 2003 should already have
logging of logon events and account management enabled. --- Steve

"Franc" <Franc@discussions.microsoft.com> wrote in message
news:C2E723F5-93A1-442D-AA1C-1620549C107C@microsoft.com...
> First of all, thanks for getting back to me, Steve. I've seen your name
> associated with several posts regarding this issue.
>
> I tried your suggestion, or at least your suggestion as I understood it.
> I
> went to the initial Windows logon, and inserted the server name in the
> Domain
> box - there are only three boxes; username, password, domain. It came
> back
> with exactly the same error as when you enter the server name in the
> domain
> box of the Change Password dialog, which is "The system cannot log you on
> now
> because the domain 'servername' is not available."
>
> Did I do the right thing? Any other suggestions?
>
> Thanks again.
>
> Franc
>
>
>
> "Steven L Umbach" wrote:
>
>> Try having them specify the name of the server in the logon box which
>> would
>> normally show the name of their computer. --- Steve
>>
>>
>> "Franc" <Franc@discussions.microsoft.com> wrote in message
>> news:DB86825B-B373-4BDC-9023-AF8C145C5046@microsoft.com...
>> > Isn't there a simple way for users to manage/change their passwords on
>> > a
>> > 2K3
>> > server? The clients are all Win2K, and the server is not a domain
>> > controller. All the solutions I've seen that suggest using the NT
>> > Security
>> > dialog/Change Password button don't work, apparently because there's no
>> > domain to define. There must be an easy way that I'm just overlooking.
>> > It
>> > used to be so simple.
>> >
>> > Thanks, in advance, for any help you can provide.
>>
>>
>>



Relevant Pages

  • RE: Trend, IIS, Permissions, Exhaustion and close to very bad language :-) Heelp!
    ... I understand when you logon on Company web ... Does the IP address point your Windows XP clients or SBS Server? ... Is the IP address of the Windows XP client or server that in your network? ...
    (microsoft.public.windows.server.sbs)
  • Re: login fails from from Solaris to windows7
    ... I can see all three Windows boxes from Solaris, but I can not login to ... Samba has a huge number of configurable options (perhaps too ... server string = Samba Server ... # per user logon script ...
    (comp.unix.solaris)
  • Kerberos logon failure - Windows Server 2003 RTM
    ... Domain controller with Windows 2003 RTM. ... Authentication server with Windows Server 2003 RTM (Proxy ... Users logon to the web site from the authentication server and are ... see Help and Support Center at ...
    (microsoft.public.win2000.security)
  • Re: Secondary logon possible ?
    ... administrator on the remote computer. ... Server Win2K Server ... Just from time to time it would be helpful for me to logon to another ws in the background to change or check settings. ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Native Mode possible problems...help!
    ... their password will still be able to logon to an NT 4.0 - but using their ... Windows 2003/2000/NT ... > They NT 4.0 domain controllers will still be able to authenticate users, ... > Why not just upgrade the BDCs to Windows 2000 Server? ...
    (microsoft.public.windows.server.general)