| We did everything short of cozying up with a dictionary. We used the current admin password. We used the name of the company. We used password. We used admin. We used administrator. We used the admin password from three years ago, when the thing was first set up (yeah, I can remember a damn three year old password, but hell if I know where my socks are). We used the name of the program that RUNS on the server. We used the name of the server. We even typed in a few things out of frustration that aren't repeatable here. We used the old sysadmin's login, his wife's name, his daughter's name, all the passwords that he used that we knew, and some we didn't. We used the name of the OTHER company (don't ask). We used our own names. We used, in short, everything that should have been a password, all to no avail. We even pulled the drive out and stuck it in another NT computer to copy over the SAM files, only to find out there were two other drives hidden away in the server, which used RAID5 - so that route wasn't possible. After that, we got pissed off and reloaded NT, which of course killed the Oracle database program files that make the server useful. It was at this point that we realized that when the vendor of the software that runs on that server came out to load their package, they neglected to leave the server install CD with us. So we ordered some pizza on the company's tab, sat around, and figured What The Hell To Do Next. |