similar to: Printer on LDAP PDC debug help?

Hi, I'm trying to set up a samba-cups-pdf-printserver. samba itself is running fine, but when i try to add the cups printer-drivers for windows i got the following error: System: Debian/sarge with 2.4.20 i686 GNU/Linux samba 3.0.2-2 cupsys 1.1.20final-13 Windows-driver from cups-samba-5.0rc1.tar ssflx01_v2:~# cupsaddsmb -a -v -U uuuu Password for uuuu required to access

Hey everyone. Having a little problem getting cupsaddsmb to work correctly. I have been reading throw the Samb 3 book today as i am trying to have the ability for drivers for our printers to be automatically downloaded when a client adds the printer. I am using: FreeBSD 4.10 samba 2.2.11 cups 1.1 cups-samba I put the following info in smb.conf: [printers] comment = All printers

Hi People, Trying to be as informative as possible: I'm trying to add printers drivers to cups-owned, samba shared printer. Called "PDF-Creator" But when I issue the command "cupsaddsmb -U root -v PDF-Creator" I get a "NT_STATUS_LOGON_FAILURE" Weird thing is: I was able to do this a few months ago. But I noticed the drivers where missing when I wanted to add

Sorry, Should have used plain text to begin with and better wrapping: Hi People, Trying to be as informative as possible: I'm trying to add printers drivers to cups-owned, samba shared printer. Called "PDF-Creator" But when I issue the command "cupsaddsmb -U root -v PDF-Creator" I get a "NT_STATUS_LOGON_FAILURE" Weird thing is: I was able to do this a few

Hi, I've also got problems downloading drivers from samba to a windows client. I'm running Debian Samba 3.0.7-1, and Cupssys 1.1.20final My Windows Client is a Win2KPro. I succesfully installed my printers with Cups and they work fine under Linux, and from remote cups clients. I've been trying to follow the samba docs on serving postscript drivers for cups from the print share in

I'm running Ubuntu 10.04 LTS and loaded (via apt-get) Samba version 2:3.4.7 as part of the effort to bring up Sambafax. A dpkg-query gives the following: # dpkg-query -l | fgrep samba ii libcrypt-smbhash-perl 0.12-3 generate LM/NT hash of a password for samba ii samba 2:3.4.7~dfsg-1ubuntu3.1 SMB/CIFS file, print, and login server for U ii

HI! I've a problem with cupsaddsmb!! :-( At the console I type: cupsaddsmb -U root -v <printername> and after some operations complete correctly appear this error: [...] Running command: rpcclient localhost -N -U'root%' -c 'adddriver "Windows NT x86" "eps6100l:cupsdrv5.dll:eps6100l.ppd:cupsui5.dll:cups5.hlp:NULL:RAW:NULL"' cmd = adddriver

Hi All, Following instructions from here: http://samba.mirror.ac.uk/samba/docs/man/CUPS-printing.html#id2942237 and also in the "Official Samba Howto" book, I tried to install the CUPS PS driver using cupsaddsmb. It failed due to various reasons, and then I finally got it to work. When I unpacked the latest tar.gz file (cups-samba-5.0rc3.tar.gz) it doesn't unpack the files as:

I'm trying to change my Samba setup from LPD to CUPS, with little success. I've followed [and re-followed] the setup documentation from CUPS and I just can't get Samba to recognize my printer. The catch is - it sort of recognizes it :-( First I added these lines to my smb.conf: ========================================= [global] load printers = yes printing = cups printcap name =

Windows 98 client cannot print via samba to PrintPro printer "exported" via Cups/PrintPro on PrintPro/Samba server. "Exporting" with Cups on server node allows print drivers to be downloaded to Windows clients from the server. Any help or suggestions are greatly appreciated. Win98 node gim98.rsmas.miami.edu [129.171.97.21] connects to Samba 3.0.0-15 server "prima"

I'm really not looking forward to downgrading because of this but if this persists much longer I'll have to. :-( Platform: MDV LE 2005 Previous version was 3.0.9 I think. Whatever the default for Mdk 10.1 Official was. samba-swat-3.0.14a-2mdk samba-smbldap-tools-3.0.14a-2mdk samba-doc-3.0.14a-2mdk samba-client-3.0.14a-2mdk samba-common-3.0.14a-2mdk samba-vscan-clamav-3.0.14a-2mdk

Hi all ..... I tried to connect my windows box to my PDC which is Debian Linux based with Samba 3.0.4. I've got windows-cups driver ( cups-samba-5.0rc3 ) came from linuxprinting.org installed. What I did : - host:#cupsaddsmb -H host -U root printername - connect to the shared printer via a fully updated winxp box, and it's successfully installed - I checked it out on printers and faxes

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 1. Is there a reference that will help in the identification of Samba errors? 2. Can anyone identify these errors? I' @ log level = 6 and I get: Mar 15 10:58:01 enigma smbd3[4271]: [2004/03/15 10:58:01, 0] lib/util_sock.c:get_peer_addr(952) Mar 15 10:58:01 enigma smbd3[4271]: getpeername failed. Error was Transport endpoint is not connected

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 | [root@enigma 0 3]$ rpcclient enigma -U 'root%XXXXXXXXXX' -c 'enumdrivers' | | [Windows NT x86] | Printer Driver Info 1: | Driver Name: [Lexmark Z53 Color Jetprinter] | | | [Windows NT x86] | Printer Driver Info 1: | Driver Name: [Lexmark Z53 Color Jetprinter] | | [root@enigma 0 3]$ rpcclient enigma -U

Hello all. I hope this question is not too dumb, but I thought I'd ask it anyway since I'd like to get the opinion of the samba gurus out there. My question is this: -- is it better to run smbd and nmbd on a server that acts as a NFS server and has disks directly attached to it or is it better to run samba on a seperate machine that acts as a client to the NFS server? In other words, in

Guys, I need a clue here. The command I am using is: cupsaddsmb -H kaliklak -U Administrator -h kaliklak -v Lex_Z53 and despite the fact that the password used is correct the result is: [root@kaliklak root]# cupsaddsmb -H kaliklak -U root -h kaliklak -v Lex_Z53 Password for root required to access kaliklak via SAMBA: Running command: smbclient //kaliklak/print\$ -N -U'root%XXXXXXXXXX'

I've also tried adding the pgsql and mysql RPM's and they're not available either. On 20/03/2023 12:58, Gary Stainburn wrote: > Apologies.? This is the correct screen grab. > > The extra errors in the OP were because I had been experimenting, to > try to fix the issue. > > [root at testsvr ~]# ./ldapAuth.php gary.stainburn fake-password > PHP Fatal error:?

All LDAP authentciation works just fine, windows passwords can be set LDAP users. Windows workstations can connect to the machine's shares using windows passwords stored in LDAP> LDAP tools are configured with the right LDAP credentials and DN settings, for people and computers. The logs show authenticated connections with Directory Manager's credentials, but the computer accounts

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi. I'm trying to write a HOWTO for Samba 3.0.1 with an LDAP (new schema) backend. Basically just how to get a PDC up and useful. Here is the background info: 1. Samba 3.0.1, Mandrake 9.1, openldap-2.0.27-5.3mdk, clients are XP Pro and either Mandrake 9.1 or 9.2. 2. System will do Single Sign-on auth for both Linux and Windows XP. Where I am

I am having the same problem as well. This is just an educated guess, but I think the problem has to do with the "in-memory krb5 keytab support" Anyone have any workarounds? -Jim