similar to: Samba and CUPS and drivers, oh my! (Why is this so **** hard?)

Boy this was a big scary headache! As well, I really wish the samba upgrade didn't wipe my changes to /etc/pam.d/samba and /etc/rc.d/init.d/smb (back them up instead, please). Situation: Upgrading Samba from 2.2.4 to 2.2.5. Samba is using winbindd for authentication. Problem: Under 2.2.4, smb.conf originally contained a password server specified by IP address: password server

Hi all... I need to make a few queries to WINS, but am unsure how to do so. 'nmblookup' will allow me to enter an IP address and get information about the machine name, domain, and username. I want to do the opposite...I would like to have a tool that will take a username and return the IP address. I know this information is stored in WINS somehow, and I am capable of writing some Perl

On friday I was having a heck of a time using Samba...especially in regard to CUPS and printing. I posted on the list some big questions about my setup and what could be done with it, and was a little disheartened not to get an answer. Later that day, completely out of the blue, I received a long-distance call from John H. Terpstra, one of the Samba lead people. He must have tracked down my

Nope, doesn't work, and I need the drivers to be available and read from the linux server. The PPD files do contain one which is specific to my printer and has worked on another machine. -----Original Message----- From: Blake Patton [mailto:pattonb@spots.ca] Sent: May 31, 2002 11:32 AM To: WEBSTER, Greg Subject: RE: [Samba] I will pay you $10US (via Paypal) out of my own pocket if you can

In the documentation the "oplocks = yes" option is give in an example, as the default for this parameter. However, I needed to turn oplocks off, and so assumed that the command "oplocks = no" would work. It doesn't, instead I found that "oplocks = false" does. There needs to be some boolean fixing done, or at least documentation should reflect this strangeness.

Unfortunately, it appears smbstatus will only show the clients that have accessed the shares since the last restart of the smb daemon (not a guarantee that people will do this in our case). There appears to be a timeout of this information as well. WINS does keep all this information based on when the client's machine first logs into the network, so it's a lot more accurate. Man, I wish

I'm running samba 2.2.2-6 on a redhat 7.2 box running 2.4.9-7 kernel... I'm trying to upload printer drivers from a Windows 2000 client. I've followed the instructions in the samba howto collection. I've created the print$ share, created the printer directory and subdirs, and made sure they are writeable by me. I put myself in the write list and the printer admin list.

I've experienced something like this, as well. Though I don't know if this will help, I would make sure that your NT username(s) are appropriately mapped to unix users. You may not be able to view the properties because the permissions/mapped user are mixed up. You can check this by doing a smbstatus - the user names listed as connected are the unix usernames that have been mapped to.

I'm sure you've seen that subject line before.... I can't get Samba (via Swat) to see my CUPS printers at all. I've tried everything I can think of...the single network-connected printer is listed in CUPS and I've added it on the command-line (via printconf-tui). I can send a test page to it from the CUPS web-interface and also through the printconf-tui interface. I can

Seriously. I can't afford to be down much longer or I'm going to be in serious trouble. Running Redhat 7.2. Here's the scoop: Cups is installed and running. Samba is installed and running and is sharing files properly to 100+ people. I can print a test page from the Cups web-interface. I can print a test page by "cat foo | lpr" or "cat foo | lpr.cups" no

I'm trying to add a printer to Samba 2.2.4, using the cupsaddsmb tool provided with CUPS. cupsaddsmb basically invokes samba's rpcclient program.. The driver part installs fine using cupsaddsmb, but addprinter always fails for some reason. This is what cupsaddsmb returns, does anybody have any idea as to what is wrong?? If I invoke rpcclient manually with a debug level of 10, it goes

Apologies if any of these have already been fixed in the working version Page 6 third and fourth lines from the bottom "Digium is the solely capable" should read "Digium is solely capable" -- Andrew D Kirch | Abusive Hosts Blocking List | www.ahbl.org Security Admin | Summit Open Source Development Group | www.sosdg.org Key At

I have built a new CUPS print server on Ubuntu 8.04 server for our office (used apt-get to download the CUPS v 1.3.7 and Samba v3.0.28a packages) as a replacement for our existing Suse CUPS print server and I want to use the cupsaddsmb tool to set up printer drivers for download by PCs rather than using the Add Printer Wizard method which we have used on our older CUPS print server. After some

This is probably a CUPS bug but maybe not, I'll mention it here just in case. When using cupsaddsmb to install 64bit drivers the drivers must be in the (maybe distro/configure dependent): /usr/share/cups/drivers/x64 to be sure that's "x64" with a lower case "x". The cupsaddsmb app ignores the drivers if the subdirectory is named with an uppercase "X" (X64).

Hello, I tried to find a way to having the setup of cups printing working for windows client. I end up now with "cupsaddsmb -v -a -U root" finishing by "Printer Driver mesange successfully installed. Running command: rpcclient localhost -N -U'root%xxxxxxxx' -c 'setdriver mesange mesange' cmd = setdriver mesange mesange result was NT_STATUS_UNSUCCESSFUL" My

Hi All, I was recently directed to look at some upstream CUPS changes which impact Samba's printer server functionality: cupsaddsmb has been dropped via https://github.com/apple/cups/commit/f1def5b85f51120f5dc1eb21e1f38860ef41be9c Given that it's only just gone in, I wouldn't expect it to reach distros for some time, but I think it's worth discussing how/whether we should react.

Try : killall -s HUP /usr/sbin/smbd is causes that smbd rereads its config. At 11:20 10.09.2002 +0200, Kurt Pfeifle wrote: >Hi, > >I have a question regarding the visible list of printers in the network >neighbourhood of my Samba server, and how to force it to become updated. >Maybe one of my settings is wrong? Maybe it is a bug? > >My problem (short):

Hello, i have problems getting the automatic driver installation for windows clients running. i am using cupsaddsmb, it creates the WIN40 Directory and tells me its putting files - but the Directory remains empty - and thats, so i guess, the reason for the rpccleint command failing (DOS error 0x00000042 smth.) what am i doing wrong? regards sven wandersleb transcript of cupsaddsmb and

Hi All, I have Samba 3.0.22-1ubuntu4 running on Ubuntu 6.01 (eft) and am trying to add printers using cupsaddsmb. On running it I get the following: root@pykota:/home/printeradmin# cupsaddsmb -U root -a -v Password for root required to access /var/run/cups/cups.sock via SAMBA: Running command: smbclient ///var/run/cups/cups.sock/print$ -N -A /var/spool/cups/tmp/454b654e20cfa -c 'mkdir

I can't even get cupsaddsmb to work right. I followed the configuration instructions from the documentation, and my smb.conf matches what the cupsaddsmb man page says. I am getting extremely frustrated with this and not being able to allow clients to download drivers from Samba. With cupsaddsmb, this is the error I am receiving when it gets to this point, over and over: Running command: