...however is possible based in the .pdf generate discover what tool were used to generate it?
So the use of Rainbow Tables can't help in discover the key?
Nope...rainbow tables are irrelevant to pdf-cracking....
Regarding detecting the tool that generated it...
Usually,most developers store their product's name into the .pdf 's metadata:
in Adobe Reader,you just go to File-Properties-Description-'PDF Producer" section.
But since it's encrypted...obviously you can't ;-)
Maybe you could use pdfinfo from the xpdf package to extract this info?
hxxp://www.foolabs.com/xpdf/download.html
Also,you could give a try with this one,it's a gui-based .pdf metadata viewer/editor,
(although I really doubt this would work without providing a password first):
hxxp://www.becyhome.de/becypdfmetaedit/description_eng.htm
As a last resort,just fire-up a "strings" utility...
In any case,discovering the tool that built this .pdf,
would certainly help in understanding what is that we have to deal with,
but I can't see a way(a "direct" way,at least),
in which it would assist on speeding-up the bruteforcing process...
As for PDF version 1.6...
this means the file in question can't be opened/displayed correctly in older pdf viewers...
you'll need at least Adobe Reader 7 to use it.
As for Length 128...this is obviously the number of the RC4 encryption bits....
Conclusion(in short):
Use all alphanumeric strings in pdfcrack(or Elcomsoft),and be patient...
"Maybe not today,maybe not tomorrow...but soon-and for the rest of your life"