why not let every machine compute the single tables on their own harddisk and once they are done transfer them on your main server?
thats how I did it

whive "Rainbowcrack sucess Probability 1.1 by nulladd" it says that i have 100 % chance to find all the password, but i can't
i don't know how it could be but i can't find a password taht is like : 44w31vbt
it find : 44w31vb and then say<not found> for the last letter "t"

is there someone that can say me why it count not found all the passwords ?
I thought i could find all whive these files... i have about 18 go of rainbow tables ...

it says ~100% not 100%, ~ is a mathematical term for 'almost' as the success rate for tables approaches 100% but can never reach it (tho it appears to do so)

but it should get the letter t.

perhaps try doing '44w31vb44w31vb' as you can already get '44w31vb' so you will be able to determine whether its the tables or incorrect use

ah whoops u trial members cant see download section
here is what i posted
------------------------------------------------------------------------------------------------
compiled rainbowcrack files with the rainbowcrack algorithm patch, enjoy!
QUOTE
This package contains some useful hash algorithms which are not supported in RainbowCrack 1.2.
These algorithms include: NTLM, MD2, MD4 and RIPEMD160.
With the patch, you will be able to generate the rainbow tables of these algorithms.
www.antsight.com/zsl/rainbowcrack

-----------------------------------------------------------------------------------------------
i also thought id quickly outline how to compile the rainbowcrack files with the latest openssl package, this isnt a tutorial but it should put you in the right direction.
compiled under Visual C++ Student Edtn, but other compilers should work fine too

download and install ActivePerl and masm (needed for openssl)
www.activestate.com/Products/Download/Register.plex?id=ActivePerl
www.masm32.com/masmdl.htm
download and install openssl by reading INSTALL.W32 and following the steps
www.openssl.org/source

assuming it all compiles fine you can now put the openssl files in the VC++ folders
* copy the files in openssl\out32dll to your VC++ bin folder
* copy libeay32.dll and libeay32.lib into your VC++ lib folder
* copy inc32\openssl into your Include folder. openssl should now be a subfolder within the include folder
you might also want to update your old libeay32.dll that came with rainbowcrack with the new one that you just made
now compile the rainbowcrack files - nmake makefile.win

Note:
nmake is included with visual studio, there are other ones out there too
you should have all your paths correctly set up as well

------------------------------------------------------------------------------------------------
should help get u started on compiling

its lm or ntlm (mostly lm) so i suggest you generate lm tables not md5

on a site note the lm hash is based off DES and ntlm is based off md4

what you need to do is set up the tables the way you want them
then start generating them
after a couple minutes (depending on your configuration) you will see something like "xxx chains generated in xmin and xseconds"
where x is some number

so you put that data (minutes and seconds) into rainbowcalc and then it will tell you how long it will take

i reccommend that you dont have anything running in the backround for the first couple chains and perhaps let it generate 2 or 3 chains so you can be sure of the time it takes

this is really a rough quess and if anyone wants to tell me of any holes in this explaination id be happy to hear them


also read the paper for detailed info
hxxp://lasecwww.epfl.ch/pub/lasec/doc/Oech03.pdf

statistics
-------------------------------------------------------
plaintext found: 2 of 2 (100.00%)
total disk access time: 24.64 s
total cryptanalysis time: 33.98 s
total chain walk step: 31374553
total false alarm: 1282
total chain walk step due to false alarm: 2555782

result
-------------------------------------------------------
case correction for password !KAT7KA96?? fail!
username !KAT7KA96?? hex:214b4154374b413936f500

Case correction always seems to fail on passwords with extended ASCII characters...

Oh well.

-Scott

--