similar to: Printing from Windows 98

Hello, I've tried both samba-3.0.0beta2 and beta3 but both give me the same problem. When on a windows dekstop and trying to add a printer with samba as the printserver , the printers exported by the samba server are not seen by the windows desktop. e.g.: relevant part of smb.conf: ----------------------------------- load printers = yes printing = cups printcap name =

Hi After struggling with this for a couple of days it's time to ask for help. We have two samba servers one is on Solaris 8 running Version 2.2.8a and one on Solaris 10 running Version 3.0.28 I am having a problem with samba printing from the Solaris 10 samba server. I can print from the machine itself using lpr directly. I can print from a windows machine using lpr printing to that server

I am using Slackware 10.2 (kernel 2.4.29) and Samba 3.0.21c for my print server. The client workstations are WinNT4. I have two printers on the linux server..an HP DeskJet 600 and an Okidata B4250. I can install and print to the HP from any of the workstations. I can install the Okidata just fine, but when I try to print from Word, Excell, or any application Dr. Watson comes to visit. I get

I have Samba 2.0.6.3 (or is it 6.5?) running on a SuSE 6.2 system. I currently have three Windows 95/98 clients attached to my linux machine, which is a firewall/gateway to the internet via cable modem. When I was using Samba 1.-something, I was able to print to the printer on the linux box from two of the three Windows 95 machines on the network. Since I upgraded to 2.0.6, I haven't been

Greetings, My help request is about samba that can't print using CUPS from windows. I tryed to search for help on mailing-lists archives all around, and with the great Samba-HOWTO-Collection.pdf but didn't found a clue about my problem. I can print the CUPS test page, but can't print anything from windows using samba's share. I use samba-3.0.2a I compiled myself. It has been

Ok.. Just a little follow-up on my Solaris printing problem that I was having! As it turns out, I put the fully-qualified path names to the print commands (lpr/lpq/lprm, etc) in the samba config file (smb.conf) and all of my printing problems have disappeared! Now, after a clean reboot of the OS (Solaris, not PC), I can log on to Samba and directly print -- instead of it silently failing!

Hello, I have a question about samba and printing. I am running Linux RedHat 7.3 and installed the Samba from the install CD. (Samba 2.2.3a) I have a "Using Samba" Book from O'Reilly, it talks about Samba 2.0.5a, but I was hoping that somethings would be the same. On the RH Box I have a printer (actually it is on the network) but it is in the printcap file. It is a IBM Network

I am having problems printing to a Samba printer from my Windows 2000 machines. While eventually it does print, it takes an extremely long time. The test page takes over 5 minutes to print. I have tracked it to the Samba spooling process. The delay is in Windows sending the information to the Samba spool. If I look in the Samba spool directory during the print process, the file size increases very

Hello! We're using samba to manage our HP LaserJet 8000, which is a very fast and high capable printer. So we need the best performance, when we printing. The problem is when samba receive a file for printing it's copying the file to a tmp directory, and after that the lpr is copying this file out to its own spool directory. For example, where a 300M printing job is arriving from a

Hi again Thank you all for helping me out, really appreciate it. Works like a charm now, I added [global] printing = cups printcap name = lpstat load printers = yes and in [printers]-section: [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = yes writable = no printable = yes

Hi, I have a bizarre printing problem, and i think i've narrowed it down to either samba, or the way windows packages the file to be printed. I've recently implemented a new server. Users print through the linux server from their windows desktop machines. OLD server: -samba 2.0.7, which uses lpd NEW server: -samba 2.2.3, which uses cups The old server can print to the printer (Savin

I just thought that I would put this out there and see if anyone else sees this problem with Samba 1.9.18p4 (under Solaris 2.6). It appears that after some reboots of Solaris, Samba printing is partly dead. What I see in the logs are below, and what happens is that the file to be printed is spooled to /var/spool/samba, like always, but when the lpr command is issued it croaks. I've been

On 09/22/2017 06:58 AM, hw wrote: > > PS: Now I found this: > > > type=PROCTITLE msg=audit(09/22/2017 12:08:29.911:1023) : > proctitle=/usr/lib/sendmail -t -oi -oem -fwawi-genimp > type=SYSCALL msg=audit(09/22/2017 12:08:29.911:1023) : arch=x86_64 > syscall=setgroups success=no exit=EPERM(Operation not permitted) > a0=0x1 a1=0x7ffc1df3b0d0 a2=0x0 a3=0x7f5d77c3a300

Post the entire output of: ls -al /usr/local/lprng/current/bin/lpr Is this in the path of a regular user? Try: which lpr with a regular user. Joel On Thu, May 23, 2002 at 04:39:38PM -0400, amit deshmukh wrote: > > Can u help with this ? > > thanks in adavance > amit > ---------- Forwarded message ---------- > Date: Fri, 17 May 2002 12:36:32 -0400 (EDT) > From: amit

I?ve got a Ricoh multi-function printer/copier that I need to restrict the colour printing functions to only members of the @ColorPrinting group. I?ve two print queues for the Ricoh, one colour, one not. Unfortunately, even users on the B&W queue can change the colour settings on the print dialog in Windows and bypass the restriction and prints in colour. Part of this likely is our CUPS

Hi I'm running Samba 2.2.8a on a UnixWare 7.1.3 box. I'd set up the Samba printer shares, and it seemed to be working fine (only live for a couple of weeks). However, I've just added some heavy users, and the printer daemon keeps bombing out. I'd configured the printers to use lpr, but someone suggested I should use lp, so I thought I'd give this a go at the weekend.

Daniel Walsh wrote: > On 09/22/2017 06:58 AM, hw wrote: >> >> PS: Now I found this: >> >> >> type=PROCTITLE msg=audit(09/22/2017 12:08:29.911:1023) : proctitle=/usr/lib/sendmail -t -oi -oem -fwawi-genimp >> type=SYSCALL msg=audit(09/22/2017 12:08:29.911:1023) : arch=x86_64 syscall=setgroups success=no exit=EPERM(Operation not permitted) a0=0x1

I've noticed several users on various mailing lists that have had trouble printing from Windows to a Samba server. I've stumbled onto a fix for my particular situation, and I thought I would post it for the benefit of others. It turns out to be a CUPS/Windows interaction issue and not a Samba problem, but the symptoms tend to point to Samba as the culprit. (I've posted similar

Am 22.09.2018 um 13:24 schrieb Alex Persson: >> Sent: Saturday, September 22, 2018 at 12:08 PM >> From: "Robert Schetterer via samba" <samba at lists.samba.org> >> To: samba at lists.samba.org >> Subject: Re: [Samba] Printing via SMB-Kerberos no longer works >> >> Am 22.09.2018 um 09:49 schrieb Alex Persson via samba: >>> After upgrading

Hi. I mostly use my system as a super-user and so I can mostly do everything without worrying too much about permissions. Not too long ago I created a "general" user account which is automatically logged in after a few seconds for others to have (limited) access to the system. Mostly everything works (ie. CD/DVD writing, sound, floppy access, etc.) But when it comes to printing, only