On Wed, 2003-11-05 at 09:11, Timothy Stone wrote: > List, > > I'm trying to find my way thru the maze of supporting software to get > something that appears to be "cookbook" by some standards to work: > Anonymously Produce PDF documents via a PDF Pseudo Printer in Samba. > > I'm running RHL 8 (Psyche). > > I built Samba 3.0.0. It works--much disconcerting to my MCSEs; add the > random server messages placed and appearing in the Windoze Server Manager ;) > > What I'm after is an anonymous PDF printer that *anyone* on the Windoze > domain can use to print PDF documents. I don't want to have to add 10s > or 100s of users to the Linux box just so they can use the printer. > > Simple enough, right? Well, something is haywire. The pseudo printer is > available to a Windoze client via Add Printer... Printing seems to work > at first, but the resulting output is *always* 321 bytes and cannot be > opened by Adobe Acrobat. :( > > Additionally, there seems to be a rather unfriendly message about > "Access Denied, unable to connect" message on the Windoze client, yet > status is "Ready". > > I have a feeling that PAM might be getting in the way. I have really > loosened my Samba.conf per the Samba Project Documentation, Chapter 8 on > Anonymous Printing. I tweaked CUPS for raw feeds per the docs, but I > never really got printing working on my Linux box effectively in the > first place, and I'm pretty sure that I'm not asking Samba to use CUPS. > can you print a pdf normally? Samba is going to use the underlying print system. > My original sources for setting this up came from the following: > > http://www.linuxgazette.com/issue72/bright.html > > A great article, if slightly dated, but with some intelligent guessing, > configurable for RHL 8 and Samba 3.0. *But* I might have missed something. > > And more recently, and the current implementation being tested: > > http://www.linux-mag.com/2003-01/guru_01.html > Are you wanting to print pdfs or create pdfs. THe example above seems to discuss using a printer share to create one. If that is the case what is in the 321 byte file? > This one is very simple, but the output is still only 321 bytes. > > Does anyone have suggestions to try and resolve this? PAM has a Samba > config that is default for RHL 8. I did edit the /etc/rc.d/init.d script > to use my Samba 3.0 build so I'm fairly sure that I'm not using the > default Samba 2.x install found in RHL. > > Many, many thanks in advance for suggestions on resolving this problem. > I will actively monitor this thread and answer any questions anyone may > have on my configuration that may further help get this working. > Other things to look at: I have always used the DIAGNOSIS.txt file found in the /usr/share/doc/samba* for trouble shooting a setup. If you think the problem is authentication then try somthing very simple like sharing /tmp and see if you can connect. You can turn up the logging in smb.conf with the log level = directive. set it to something > 0 and see if that helps. You can have the linux machine join a domain and let samba authenticate to it using winbind. HTH Bret -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
