Jump to content

Lab Tech

Active Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by Lab Tech

  1. When I enabled workgroups I was logged in, it required a reboot. LDAP and the Microsoft Networking for Workgroups are two different things, you are correct and they do not conflict. I can log in with or without Ldap, well at least I could before this incident. On comment on "its not your machine"; had I lifted a laptop I wouldn't go through this much trouble and frustration to reclaim the data. It just not worth it, when you can reformat and actually use the computer. Coming to a public forum would be a lot of exposure for a thief. I suspect a lot of folks come to this site because they've almost given up on reclaiming their lost digital photos, resumes, and trick spreadsheets, hoping this port of last resort might illuminate them to an option. I can select the domain or a local login. That is how I could work on the Ldap network and in turn work from home. No changes, I've watched others hose themselves doing just that. It was messy, and I didn't want that to happen to my system. Safe mode is a good idea, I haven't tried it yet since it is the same login, but it's worth a shot, thanks. I'll give it workout, thanks. The trick is finding the driver. The initial challenge loads it for me, so it must be locked up in the boot record.
  2. Sorry, I'm not sure what you mean. A workgroup is Microsoft's terminology for a localized peer-to-peer PC computer network. I think workgroup and domain, in this context, are roughly equivalent. The system was configured to participate in my local "windows workgroup" Is there a way to access the system upstream from the workgroup?
  3. When I used it one contract job, they had me install the encryption software and use LDAP to login. It was mandatory and I thought it a good idea... at the time. It's not my work PC anymore, do I just login locally. When my kids where young and reckless, I set all my systems with passwords and screen timeouts. So yes, I have passwords set. I normally drug it to work and back and never thought a share folder was a good idea. File Sharing, might be default, but this system was not part of a workgroup. I didn't think it would be an issue - I've activated workgroups on on other boxes in my home - so every box can see at least one folder. I'd allowed a few hotfixes to install days before but ignored the "reboot required' figuring I'd eventually reboot. When I did, everything went normally until I typed in my ID and password. All that to say this, I can't log in, short of a miracle. Is there a solution? Boot CDs can't read the encrypted disk. Can I force or recover the existing password through a USB program?
  4. Tried blank, space, every password I've used since 1980, and very combination of caps on and off. I've poked at it for weeks...
  5. The standard XP shared network workgroup set up. If you attempt to mark a folder as "shared", it pops up and asks you to set up a network group - "WORKGROUP" is the default. It's real handy if you want to move files around, etc.
  6. The system is encrypted,and I can get through the passworded boot challenge, load the encryption driver and start the OS, but I've locked myself out of XP. Thinking it would be nice to use the WORKGROUP feature, I used the wizard and rebooted - now my password is not working. The reboot also took care of the latest MS hot fixes. Either one may have caused the problem. I can successfully use my ID and password on the pre-boot challenge from the encryption software (PC Guardian, aka Guardian Edge, or Encryption Plus) and it responds as expected by "loading driver". The system seems to boot normally, but the previous password doesn't log me in. I've tried my old passwords. Of course boot CDs don't help - they don't load the disk driver from the boot sector, so the disk is still encrypted. If I read the forum correctly, if I am not logged in, am I out of luck?
×
×
  • Create New...