RE: IUSR issue after patch

From: Andrew Shore (andrew.shore_at_holistecs.com)
Date: 03/17/05

  • Next message: Conlan Adams: "RE: Admin Rights required on Terminal Services"
    Date: Thu, 17 Mar 2005 17:02:25 -0000
    To: "hartmann" <hartmann@thestar.com.my>, "Security Basics Mailing List" <security-basics@securityfocus.com>
    
    

    Can you logon with any use (pref domain admin)

    It looks like the machine SID is corrupt.

    Log on with local account, move the machine to a workgroup then
    reintroduce it to the domain.

    -----Original Message-----
    From: hartmann [mailto:hartmann@thestar.com.my]
    Sent: 17 March 2005 04:43
    To: 'Security Basics Mailing List'
    Subject: IUSR issue after patch

    - The server was unable to logon the Windows NT account
    'IUSR_machinename'
    due to the following error: Logon failure: user not allowed to log on to
    this computer. The data is the error code. -

    Any ideas guys?
    All sites hosted by this web server are now inaccessble after a full
    system
    patch.

    Please help, and thanks a million in advance.

    Regards,
    Adam

    /******************************************************************\
    This message and any attachment(s) are confidential and may be
    privileged or otherwise protected from disclosure. If you are not the
    intended recipient, please telephone or e-mail the sender and delete
    this message and any attachment from your system. If you are not the
    intended recipient you must not copy this message or attachment or
    disclose the content to any other person.

    Any opinion, view and/or other information in this message and/or any
    attachment(s) hereto which do not relate to the official business of
    Star Publications (Malaysia) Bhd shall not be deemed given nor endorsed
    by Star Publications (Malaysia) Bhd. Our company is not responsible for
    any activity that might be considered to be an illegal and/or improper
    use of email.

    E-mail transmissions cannot be guaranteed to be secured or error-free as
    information could be intercepted, corrupted, lost, destroyed, delayed,
    incomplete or contain viruses. The sender therefore does not accept
    liability for any errors or omissions in the contents of this message or
    for any virus damage which may arise as a result of this e-mail
    transmission.
    /******************************************************************\


  • Next message: Conlan Adams: "RE: Admin Rights required on Terminal Services"

    Relevant Pages

    • RE: IUSR issue after patch
      ... Subject: IUSR issue after patch ... Can you logon with any use ... It looks like the machine SID is corrupt. ...
      (Security-Basics)
    • Re: New employee, same computer -- what to do?
      ... By "local account" I mean there is a local username that is created when ... It is not considered good practice to rename user accounts to deal ... good domain logon password, but everyone has access to all the shared ... course Jane will use Susie's old computer and needs access to the ...
      (microsoft.public.windows.server.active_directory)
    • Re: Cannot logon to XP after changing network settings
      ... it no longer lets me logon. ... Make sure your username and domain are correct" ... the network settings from a business network to a home network. ... What happen if you logged into safe Mode and create a local account. ...
      (microsoft.public.windowsxp.help_and_support)
    • Re: Cannot authenticate remote user to share
      ... Have her try to logon to the domain via vpn using the ... domain name also which can be configured in the properties of the vpn connectoid. ... The remote machine is a laptop, ... She does not have a local account on that system, ...
      (microsoft.public.security)
    • Q: How to reset local policy (w/o being able to logon locally nor to domain)
      ... I'm unable to log on locally from any local account) ... nor the members of the domain who *do* have logon locally rights). ... I'd like to reset the local policy ...
      (microsoft.public.win2000.security)