similar to: CUPS setup with 3.0.3pre1

I have upgraded my Fedora Core 1 file server from the distribution supplied 3.0.0 RPMS to the Fedora/Samba 3.0.2 RPMS I found on the Samba Web Site. After doing this, printers are not be recognized or shared. When I restarted the server this message showed up in /var/log/samba/log.smbd: [2004/02/09 18:00:04, 0] printing/pcap.c:pcap_printer_fn(361) Unable to open printcap file cups for

I am using samba-2.2.7-3.7.2 on a redhat 7.2 server with an attached printer which is run by CUPS. It worked OK until I upgraded to samba-2.2.7-3.7.2. Now I can print locally on the server machine, but not from the windows machines on the LAN. The error message on the windows box is " Unable to create a print job." Another error, produced daily when samba is "re-initialized"

I am trying to add print drivers for a samba shared printer to a Windows 2000 group - Everything up to this step works - I am using Samba 3.0.1 rpcclient -d 100 -Uroot -c 'adddriver "Windows NT x86" \ E323:LMAAE1DD.dll:\ LMAAE1P1.PPD:LMAAE1DA.DLL:LMAAE1DA.HLP:\ NULL:RAW:LMAA1B1.DLL,LMAAE1BJ.DLL,LMAAE1BT.DLL,LMAAE1DA.ALL,LMAAE1ED.DLL,LMAAE1PI.EXE,\

I am posting again - Please help. I am trying to add print drivers for a samba shared printer to a Windows2000 group - Everything up to this step works - I am using Samba 3.0.1 rpcclient -d 100 -Uroot -c 'adddriver "Windows NT x86" \ E323:LMAAE1DD.dll:\ LMAAE1P1.PPD:LMAAE1DA.DLL:LMAAE1DA.HLP:\ NULL:RAW:LMAA1B1.DLL,LMAAE1BJ.DLL,LMAAE1BT.DLL,LMAAE1DA.ALL,LMAAE1ED.DLL,LMAAE1PI.EXE,\

Hi, I have updated my old 2.4.7 kernel to 2.4.19 using the full download from kernel.org and installed samba-2.2.6 Using my old kernel i can access every share and everything works fine. Using my new kernel also everything works but samba,. i can telnet the system, ftp also works ok, but windows 2k tells me server not found if i try to acces the shares. i think, i forgot something to compile to

Ok... here we go, I have a server running RH 7.3, samba 2.2.3a, and CUPS 1.1.14. All the printers we have are networked printers sitting off of Linksys printservers. On this server I am sharing all off our printers out via Samba. See my smb.conf file below. This server works perfectly. All printers are shared out successfully. Primary CUPS server: [global] workgroup = NEW

Hi, I've been trying to get Samba so tie with our departmental CUPS ssetup. I tried setting: load printers = yes printing = cups printcap name = cups etc in the smb.conf, but after a while discovered in log.smbd that: [2002/05/14 17:24:22, 0] printing/pcap.c:pcap_printer_fn(373) Unable to open printcap file cups for read! (Aside but possibly of interest - this

Am 2017-07-11 um 14:57 schrieb Rowland Penny: > On Tue, 11 Jul 2017 14:47:50 +0200 > "Stefan G. Weichinger" <lists at xunil.at> wrote: > >> Am 2017-07-11 um 14:40 schrieb Rowland Penny: >> >>>> Restarted winbind, did "killall -HUP" on smbd and nmbd. >>>> >>>> still can't login to DM via smbclient and that

I manage a bunch of workstations at the Wendell Free Library. They are all diskless, boot via PXE and mount all of their file systems via NFS from a server. All of the machines are 32-bit and run CentOS (fully up-to-date running 5.10). There are two printers with queues managed on the server. The server 'shares' these printers on the local LAN (eg with all of the workstations).

Hello, as I continued exploring Samba 3.0.4 as a PDC, I managed to get roaming profiles up ... Saving changes worked out fine. I logged in as TheUserWithUID=0 ... and tried to add a user. Access denied. The logs for the XP-client contain: > [2004/06/03 23:10:46, 2] passdb/pdb_ldap.c:init_group_from_ldap(1792) > init_group_from_ldap: Entry found for group: 513 > [2004/06/03

Some notes first: Fedora Core 1 (2 node HA cluster, heartbeat & drbd) Cups 1.1.20 Samba 3.0.4 400 Windows 2000/XP clients 50 print queues HP Laserjets, Xerox colour multifunctionals, Ricoh mulitfunctionals, HP DesignJet plotters 2000+ print jobs/day 8000+ pages/day 5GB + print data/day I have a custom printer accounting application that is run by samba when a print job arrives at

Am 2017-07-11 um 14:40 schrieb Rowland Penny: >> Restarted winbind, did "killall -HUP" on smbd and nmbd. >> >> still can't login to DM via smbclient and that mentioned user. >> >> I assume I need to restart all the smbd daemons ... ? > > Well, you wouldn't be able to, would you, what with having this in > smb.conf: > > template

On Sun, 1 Jan 2017 13:45:11 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 2017-01-01 um 13:29 schrieb Rowland Penny via samba: > > > Try checking in AD, as you have classicupgraded, your users should > > have uidNumber attributes. Find the lowest and the highest, do the > > same for groups and if you change to the

Hi all, I have set up a printer in cups and I can see it with lpstat -a, and I can print to it. I put what I thought was the appropriate stuff in smb.conf, and yet no printer shows up to the NT client I'm testing with, or in smbclient -L output. Any ideas at all? Here is the relevant info: ### smb.conf excerpts ### [global] ... printing = cups printcap name = cups printcap cache

Am 2017-01-01 um 17:32 schrieb Rowland Penny via samba: > If you have a user called 'root', then it is easy, remove it, 'root' > shouldn't exist in AD, it is a Unix only user and you need to map > Administrator to 'root' in the user.map removed from AD now. the user.map was there already, as mentioned. > The only thing is, do any of your users need to

I have installed Samba-3.0.22 with CUPS on my Solaris 10 box. It prints fine and shows up in my CUPS queue but active print jobs in my CUPS queue don't show up in my Windows Print Driver queue on my client! I've also tried not using CUPS and having it call lpstat but it still doesn't work! When I run CUPS' lpstat in command line it can see the jobs. What am I doing wrong?

Hello, I've compiled Samba 3.0.0 with CUPS support. I verified this: # ldd /usr/local/samba/sbin/smbd *snip* libcups.so.2 => /usr/lib/libcups.so.2 (0x400dc000) *snip* My smb.conf was copied from the HOWTO and the relevant sections look like: [global] *snip* # print support load printers = yes printing = cups printcap name = cups *snip* [printers] comment = All

ok, edited etc all uidNumber now > 10000 except that "root", I was unsure now (?) gidNumber: # ldbsearch -H /var/lib/samba/private/sam.ldb cn=Domain\ Users | grep 'gidNumber' gidNumber: 10001 - smb.conf on member: idmap config * : backend = tdb idmap config * : range = 2000-2999 idmap config ARBEITSGRUPPE:backend = ad idmap config

googled and tried stuff: # net ads search '(|(uidNumber=*)(gidNumber=*))' sAMAccountName uidNumber gidNumber -P | grep uidN | sort -n ... shows me uidNumbers: uidNumber: 0 uidNumber: 1000 .. up to 1077 So my idmap range was completely wrong, I assume. I now have on the member server: # cat /etc/samba/smb.conf [global] security = ADS workgroup = ARBEITSGRUPPE realm =

Il giorno mar, 06/10/2015 alle 16.23 +0100, Rowland Penny ha scritto: > OK, from the smb.conf manpage: > > To use the CUPS printing interface set printcap name = cups. > This should be supplemented by an addtional setting printing = > cups in the [global] section. printcap name = cups will > use the "dummy" printcap created by CUPS, as specified in your > CUPS