similar to: general cups & access permissions woes

I'm having a little problem with a HP 8550 Laser Color printer shared under samba. The printer works fine with local prints, I can see the resource printer from Win2k2 explorer. I install the remote printer in a W2k2 workstation, windows ask me for drivers, and then, I installed them. The problem is: when I'm triying to access the printer, windows told me: "Access denied, can

Hi, I'm running samba 2.2.1a (RPM install) on RedHat 7.2 I've connected a Canon LBP-8 IV laserprinter to the network via a HP Jetdirect box. I've configured the printer within linux and printing goes fine. Now I'm trying to access the printer via samba from my win2k clients. Now, the problem is: When I'm trying to print to the printer (e.g. a testpage) I get the message

I've got Samba 2.2.3 running as a PDC for some Win9x and WinNT clients. Everything seems to be fine except that occasionally (but rather often, at least every second day) printing from one of the NT-clients is impossible. In the log file it says (word wrap here in the editor): [2002/02/26 18:04:21, 0] printing/printing.c:print_job_start(952) print_job_start: insufficient permissions to open

Hi there Brian! I've seen your email on one of the samba mailing list. This has been my problem for a long time. I just want to share this problem directly to you and i hope you can lend me your help. I'm trying to setup windows printer sharing using SAMBA installed on my Linux box (Redhat 7.3 as printer server) and windows 2000 pro as my client. My win2k clients are connected to a

I have a Deskjet 690C connected to my machine running RH7.1 + linux 2.4.13 + samba 2.2.2 installed from RPM. I have setup the printer with RH's printconf-gui as a local printer. In local use it works fine. I have the following in my /etc/samba/smb.conf: --<snip>-- [global] security = share printcap name = /etc/printcap load printers = yes --</snip>-- and

On 11/11/17 02:22, Gregory P. Ennis wrote: > Everyone, > > I was hoping to be able to plug the Logitech Brio in and have it work, > but it did not. I can have it connect to a Windows 10 laptop and have > it function, so I know the camera works. > > The Centos 7.4 is recognizing it when I plug in the usb 3.0 cable. The > results of dmesg demonstrated : > > [

Everyone, I was hoping to be able to plug the Logitech Brio in and have it work, but it did not. I can have it connect to a Windows 10 laptop and have it function, so I know the camera works. ? The Centos 7.4 is recognizing it when I plug in the usb 3.0 cable. The results of dmesg demonstrated : [ 4519.922257] input: Logitech BRIO as /devices/pci0000:00/0000:00:04.0/0000:03:00.0/usb9/9-4/9-

Hi, We have just recently switched from Courier to Dovecot for both IMAAP and POP access for our shared hosting platform, and while the issues we have been seeing with Courier have gone away a new one has popped up. Unfortunately googling for an answer is difficult as it falls into the ownership and permissions category which people seem to have all the time. But in those cases it always

On 11/11/17 02:22, Gregory P. Ennis wrote: > Everyone, > > I was hoping to be able to plug the Logitech Brio in and have it > work, > but it did not.??I can have it connect to a Windows 10 laptop and > have > it function, so I know the camera works. > > The Centos 7.4 is recognizing it when I plug in the usb 3.0 cable. > The > results of dmesg demonstrated : >

Hi, I have a FreeBSD 4.1.1-RELEASE and samba-2.2.4 installed in my server, I have a printer configured and working through samba. My problem is, when I reboot my server, my Windows 2000 with service pack 2, can't print anymore, when I sent a printer job, there is no error, but nothing appear on printer, the other shares area ok, and I can get files from this shares. Then I restart the

Hi, Having a very odd problem with a printer that I've had up and running for over a year now with no previous issues. There have been no software or hardware updates recently that should have affected it. The printer is managed via CUPS and its details are loaded from the CUPS printcap. At some point late on the afternoon of the 11th, samba started rejecting print jobs sent to it.

Mates, On my Suse 9.0 pro installation, I updated Samba from 2.2.8a to 3.0.7. The upgrade went flawlessly, Samba is happily sharing all the files it was before. However, I can no longer print via cups. I have a HP LJ4 attached to the Linux box that worked great before the upgrade. I have 2 XP clients. Now from the Windows side, I get the printer status showing 'access denied, unable to

I installed Samba 2.2.2 on my Linux box. The smb.conf file is as shown below. The permission on /var/spool/lpd/lp is set to 755; ie, it is writable only by the owner, which is lp. With the setup as is, when I try to print from the NT machine, the smb log on the Linux box indicates the following error: " print_job_start: insufficient permissions to open spool file /var/spool/lpd/lp". If

Greetings, all: I'm having trouble working out a printing problem between my Samba box, and my Windows 2000 client. Here's the background: Network: Home network with a Slackware 8 box running Samba, 1 Windows 2000 client, 1 Windows 98 client, and a LEAF Project firewall providing Internet access. The Samba server should only be available to local clients. Systems: Slackware box:

On Sun, Nov 03, 2019 at 06:37:57AM -0500, Michael Lueck via samba wrote: > I have Samba shares mounted to my Linux workstation. Mostly I access files on the Samba server over the Samba mount. I use mount.cifs to bring up these mounts. > > For a couple of special cases, I use scp to transfer files between the > server and workstation. Special characters in filenames give sending them

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 4 Jun 2014, Bruce wrote: > Please see my responses below, I dislike top posting anyway :-) > On 04/06/14 01:35, dovecot-request at dovecot.org wrote: >> Message: 4 >> Date: Tue, 3 Jun 2014 09:33:48 +0200 (CEST) >> From: Steffen Kaiser >>> >Jun 3 11:38:51 brio dovecot: Dovecot postlogin.sh running as

On 03/11/2019 11:37, Michael Lueck via samba wrote: > Greetings Samba team, > > It has been a long time since I needed to ask a Samba technical question. > > Server and workstation are both running the latest Samba packages via > Ubuntu 16.04 LTS. I recently applied the security updates... actually > that was yesterday I applied them. > > >> samba

My smb.conf file contains in the general section. max print jobs = 50 And i disabled the print queue using this command : disable PrintQueueName Therefore i would expect SAMBA to reject print jobs after the 50th. But in real life it does not, it continues to spool indefinitely. If i run a batch file from a client workstation to print continuously. It means the request to print is made

If anybody could help this would be much appreciated... Samba being used with Domain security, as a printer server with an NT 4.0 PDC and BDC. Can browse file shares, can act as printer admin (FINALLY !!), but cannot upload printer drivers, have created print$ share, have created W32X86 and WIN40 directories. When I try to print I get the following error message in machine specific log,

Greetings Samba team, It has been a long time since I needed to ask a Samba technical question. Server and workstation are both running the latest Samba packages via Ubuntu 16.04 LTS. I recently applied the security updates... actually that was yesterday I applied them. > samba (2:4.3.11+dfsg-0ubuntu0.16.04.23) xenial-security; urgency=medium > > * SECURITY UPDATE: client code can