Re: How to remove a cached password?

From: Steven L Umbach (n9rou_at_n0-spam-for-me-comcast.net)
Date: 11/17/05

  • Next message: Steven L Umbach: "Re: Strange Lockout on WinXP Pro"
    Date: Thu, 17 Nov 2005 11:09:39 -0600
    
    

    It sounds like the computer is not able to contact a domain controller which
    it must be able to do. See if another domain user can logon to it or not,
    preferably a user that is a local administrator and run the support tool
    netdiag on it and to also look in the logs via Event Viewer to see if
    anything pertinent is found. A common problem for not being able to contact
    a domain controller is that it has incorrect dns settings. A domain computer
    needs to point only to domain controllers as their preferred dns servers in
    tcp/ip settings and as shown with ipconfig /all. If no domain user can logon
    then logon as the built in local administrator account to diagnose and
    repair. Once it can contact a domain controller then the user should be able
    to logon to the domain with their correct credentials and access domain
    resources unless there is a problem with the computer account [netdiag would
    show that] which can be resolved by logging on as a local administrator,
    removing the computer from the domain, and then joining it to the domain or
    using netdom to do the same if you are familiar with it. --- Steve

    "Mike" <drobee@gmail.com> wrote in message
    news:1132234981.388365.247310@g49g2000cwa.googlegroups.com...
    >I hope someone may be able to help.
    >
    > Have a laptop computer that is used mostly out of the office for remote
    > work but is part of a domain. The login used on the laptop is the same
    > as one used on a desktop. While the laptop was out of the office, the
    > domain password expired and was reset on the desktop. Normally, we
    > bring the laptop back into the office, login with the new password and
    > things are good.
    >
    > However, this time, we bring the laptop in, plug it into the network,
    > but the new password doesn't work, only the XP cached password. The
    > network is small and the computer can get on the internet without a
    > problem, but is not able to access any network resources since it
    > doesn't recognize the password.
    >
    > Is there a way to force the machine to login to the domain rather than
    > using the cached password or remove the cached password itself? Any
    > assistance would be appreciated.
    >
    > Thanks.
    >


  • Next message: Steven L Umbach: "Re: Strange Lockout on WinXP Pro"

    Relevant Pages

    • Re: XP client cannot locate domain controller
      ... Have not seen one of those servers in quite a while. ... is that the time/day/date is correct on your laptop and that it is using the ... The domain controller is NT 4.0 based. ... After my most recent trip I found I could no longer logon to the domain. ...
      (microsoft.public.windowsxp.network_web)
    • Re: Audit Account Logon Events
      ... They probably had enabled auditing of "account logon" ... events in which case failures would be recorded on the domain controller ... that the domain user tried to authenticate to. ... >> and we're trying to get successful audits of our user logon failures. ...
      (microsoft.public.win2000.security)
    • Log on the domain controller as domain users
      ... If I try to logon as domain user account to the domain controller I ... "local policy of the system does not permit you to ... How could I allow domain users to logon the domain controller machine? ...
      (microsoft.public.windows.server.active_directory)
    • Login Problem
      ... I have de following problem when i tried to logon in my laptop without ... No domain controller is available for domain due to the ... There are currently no logon servers available to service logon request. ... Make sure that the computer is connect to the network and try again. ...
      (microsoft.public.windowsxp.network_web)
    • Re: whether can logon to windows 2000 or 2003 domain
      ... domain should be configured to use the domain DNS server as its only DNS ... > We have company wide network with windows2003 SBS as Domain controller ... > connect to company network, the user can logon to his user desktop, ... > some laptop can not, it will give err msg of" domain controller not ...
      (microsoft.public.win2000.networking)

    Loading