WIN2K Pro Crisis; Can't Log On - Domain/Workgroup Problem - Windows NT

This is a discussion on WIN2K Pro Crisis; Can't Log On - Domain/Workgroup Problem - Windows NT ; The network configuration on our laptop using a domain was changed to a workgroup without making changes to the user accounts. The system was rebooted and now the user accounts can't be accessed including the administrator. Is there any recovery ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: WIN2K Pro Crisis; Can't Log On - Domain/Workgroup Problem

  1. WIN2K Pro Crisis; Can't Log On - Domain/Workgroup Problem

    The network configuration on our laptop using a domain was changed to
    a workgroup without making changes to the user accounts. The system
    was rebooted and now the user accounts can't be accessed including the
    administrator. Is there any recovery from this? I have a WIN2K
    Professional installation CD and would also like to know if files
    currently existing under "My Documents" and other user directories
    would remain in place if WIN2K were to be reinstalled.

    Thank you.

    Mike Tessman
    matessman@yahoo.com

  2. Re: WIN2K Pro Crisis; Can't Log On - Domain/Workgroup Problem


    "Michael Tessman" wrote in message
    news:a3135368.0407150604.652a56e5@posting.google.c om...
    > The network configuration on our laptop using a domain was changed to
    > a workgroup without making changes to the user accounts. The system
    > was rebooted and now the user accounts can't be accessed including the
    > administrator. Is there any recovery from this? I have a WIN2K
    > Professional installation CD and would also like to know if files
    > currently existing under "My Documents" and other user directories
    > would remain in place if WIN2K were to be reinstalled.
    >
    > Thank you.
    >
    > Mike Tessman
    > matessman@yahoo.com


    If your system administrator is worth his salt then he will know
    the password for the primary or secondary local admin account.
    Once you get in, you can re-register the machine on the domain.



+ Reply to Thread