OK, I fixed my immediate problem by changing the permissions for
/home/smbprint/ like this:
#chmod 777 /home/smbprint/
Now I can print from any Windows box to my Debian CUPS server.
My understanding of security is very weak; luckily I am just working on my
home setup. But I thought the whole poi
Thanks Pablo for responding, but still no joy.
After hours of trying different things, I finally went in search of log
files in Samba. I found that there were different relevant log files in
/var/log/samba depending, evidently, on how I had set things up at that
time. For example, from yesterday
You can point the printer in the lower part of the windows box, with the
printer url, like
http://yourdebianbox:631/printers/yourprinter or something like that, and
windows will
user ipp protocol to reach the printer. You will have to bring the windows
driver to the
windows box.
Beware of confi
I have set up a CUPS server on one of my Debian boxes, directly attached
via parallel port. I can print to it from a different Debian box on my
LAN, but not from a Windows box.
The Windows box does see the printer, and says the printer is setup
properly and sends jobs to the printer with no errors
On Thu, Jan 13, 2000 at 08:36:54PM -0600, [EMAIL PROTECTED] wrote:
> I am trying to print from Windows to a printer connected to a Linux machine.
just installed Samba, and printing is no problem
> What I have discovered, is that unless the spool directory has permissions
777, Windows cannot prin
I am trying to print from Windows to a printer connected to a Linux machine.
What I have discovered, is that unless the spool directory has permissions 777,
Windows cannot print to the Linux machine. However, if I set the directory
permissions to 777, it reverts back to 700 after I reboot. (Ca
I am trying to print from Windows to a printer connected to a Linux machine.
What I have discovered, is that unless the spool directory has permissions 777,
Windows cannot print to the Linux machine. However, if I set the directory
permissions to 777, it reverts back to 700 after I reboot. (Ca
On Fri, 1 May 1998, Hamish Moffatt wrote:
> H. If you don't specify a filter at all (remove the if=) then
> it won't use magicfilter, and will go straight through to the printer.
>
> Then you can have both the raw and cooked (magicfiltered) queues
> running in parallel; at least, I THINK this
On Fri, May 01, 1998 at 01:04:10AM +1000, Hamish Moffatt wrote:
> On Wed, Apr 01, 1998 at 04:03:46AM -0500, Will Lowe wrote:
> > about how to write a filter that does nothing, I'll do that ... I'd make
> > another printcap entry like this:
> >
> > raw|winprint:\
> > :lp=/dev/NULL:\
> > :i
On Wed, Apr 01, 1998 at 04:03:46AM -0500, Will Lowe wrote:
> about how to write a filter that does nothing, I'll do that ... I'd make
> another printcap entry like this:
>
> raw|winprint:\
> :lp=/dev/NULL:\
> :if=/usr/sbin/rawprint:
>
> where /usr/sbin/rawprint just takes its input a
> I have never found magicfilter to interfere with this though. I have
> a PCL5 HP5L, and I print through samba to the same printer which I print
> to on linux with lpr, with magic filter -- no problem. From memory
> I did the same with my ESC2P bubblejet 20 before that.
The problem is that my win
On Thu, Apr 30, 1998 at 06:57:35AM -0500, Brian Servis wrote:
> The solution then is to set up a printer in printcap that does not use
> magicfilter but instead just passes the raw data straight to the
> printer.
> Then use this printer as the share printer exported by samba. Windows
> is
> alrea
Will Lowe wrote:
>
> This DOES work:
> 1) make some windows thing (ie. MS Word) print to a file
> 2) ftp the file to the linux host in BINARY mode
> 3) killoff lpd
> 4) become user "lp"
> 5) do "cat filename > /dev/lp1"
>
> it prints just fine this way (even with all the crazy control characters
> Editing the file is cheating so you've shown nothing. I can delete the back
> half of a
> jpeg and 'file' will still say the file is a jpeg. Besides which fact 'file'
> and
> magicfilter do not share the same "magic" info which identifies files.
Nononono. The _front_ end of the file (which I'v
Will Lowe wrote:
> On Wed, 29 Apr 1998, Jens B. Jorgensen wrote:
>
> > I'm guessing you made the changes to your magicfilter /usr/sbin/XXX as I
> > instructed above (though you didn't reply to me). If you get gibberish out
> > of the
> Yes, I did, thanks.
Ok.
> > double-sure you have the righ
On Wed, 29 Apr 1998, Jens B. Jorgensen wrote:
> I'm guessing you made the changes to your magicfilter /usr/sbin/XXX as I
> instructed above (though you didn't reply to me). If you get gibberish out of
> the
Yes, I did, thanks.
> double-sure you have the right printer defined in Win95.
I insta
Will,
I'm guessing you made the changes to your magicfilter /usr/sbin/XXX as I
instructed above (though you didn't reply to me). If you get gibberish out of
the
printer when using the 'cat' passthrough in your magicfilter script that means
that your Win95 box is not generated the right output. Pl
I've got samba set up ok, but the output of my Win95 driver doesn't seem
to get sent to the printer ok -- it prints out as if I'd sent a postscript
file to a non-postscript printer (you know, one word of gibberish per
page) ... does anyone know if
1) I can get windows to just translate everythi
18 matches
Mail list logo
