similar to: Setting AD password from Linux

I'm using Samba marked 2.999+3.0cvs20020723 from Debian `sid'. In smb.conf, I've got: passdb backend = ldapsam:ldaps://master.ldap.server ldapsam:ldaps://backup.ldap.server tdbsam All works fine when both ldap servers are up, or when at least the first is up. When the first is down, though, samba tries to connect to it, doesn't manage to, and gives up instead of trying the

Hi all, i'm new to the list and here's my first question : I'm trying to install several printer drivers on my samba server with imprints. I did a package with the NT/2000 and W9x drivers and the mkprintpkg command. Then I used the command install_printer_drivers.pl to install the files in the appropriate directories. So now i'd like to check the drivers available and the

Hi, It is possible to login a W2000 workstation into a Samba PDC (version 2.2.6)? Can I use "logon drive" and "logon home" to mount automatically at login time for W2000? Thanks, in advance, Sincerely Peter Mann Tel. +49 0561/804-2465 University of Kassel Computer-Center Secr. +49 0561/804-2287 Moenchebergstrasse 11

Here are my findings. Keywords for Google and for those who, like me, did not find useful references: create user domain ldap active directory ad linux rpcclient net ads rpc account enable enabled login bind. Background: we're migrating users from AD to OpenLDAP; for a period the two have to coexist, because AD authenticates logins, OpenLDAP authenticates mail. My aim is to provide a single

Hi Matt, the problem you referred to is discussed in detail as bug #82 in Samba's bug tracking tool. It consists of 2 bugs. One prevents the registration of drivers and is due to a NULL-pointer passed from that part of code in rpc_server/srv_spoolss_nt.c which calls sys_adminlog function. It begins with the comment /* BEGIN_ADMIN_LOG */ and ends with the comment /* END_ADMIN_LOG */

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Message: 1 > Date: Wed, 18 Jun 2003 14:16:57 +0200 > From: Farget Vincent <farget@olfac.univ-lyon1.fr> > Subject: [Samba] 'Little' problems with Samba v2.2.3a-12.3 (Debian > Woody) and PRINTERS !! > To: samba@lists.samba.org > Message-ID: <20030618121659.0AC117D4F@olfac.univ-lyon1.fr> > Content-Type:

Hi Kurt, I've read the new document. It's a very fine piece of technical documentation. However, it doesn't help me in the present predicament. Going now by this book I'm only getting more frustrated. What are your versions of Samba, CUPS(?), OS, and Printer again? 2.2.8a, 1.1.18, SuSE 8.2 w/2.4.20-62, Lexmark C720 I'm stuck! I would

Hello I'm setting up the automatic printer driver download feature, and it works nicelly except for one little thing: I have to use, on the samba machine, rpcclient's setdriver command to associate a printer with its driver. I didn't see this requirement in the Samba howto, it only mentions setdriver as a way to speed up large installations. Am I missing something? Should windows

There seems to be some discrepancy between rpcclient's man page and "rpcclient --help" in regards to the servername. It seems that the proper usage of rpcclient is rpcclient [options] server this is the format that is specified in "rpcclient --help." rpcclient's man page, however specifies that the servername should come directly after rpcclient. I.E.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the release of Samba 2.2.7. A security hole has been discovered in versions 2.2.2 through 2.2.6 of Samba that could potentially allow an attacker to gain root access on the target machine. The word "potentially" is used because there is no known exploit of this bug, and the Samba Team has not been able

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the release of Samba 2.2.7. A security hole has been discovered in versions 2.2.2 through 2.2.6 of Samba that could potentially allow an attacker to gain root access on the target machine. The word "potentially" is used because there is no known exploit of this bug, and the Samba Team has not been able

I have an Ubuntu Sever 9.10 setup running Samba as a PDC for a bunch of Windows clients. Everything is functioning perfectly except for the point and print delivery of printer drivers. I have tested this with Ubuntu 9.10's Samba (3.4.0) and two of the Debian Samba packages (3.4.3 and 3.4.5). All seem to demonstrate the same problem. *What works:* Adding a printer and manually installing the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, i tried to compile and run Samba 3.0.20pre2 on one of our servers yesterday. The servers OS is FreeBSD-5.4. the configure run was okay, except for the aio part, but thats another point. compiling went fine and installation too. After starting smbd and nmbd i saw all printers but unfortunately all driver association where lost! i found out,

Hi, I'm trying to add a Windows NT/2000 OKI C5100 print driver to a Samba 2.2.3a server. I've been told that this driver does some server-side stuff, so I'll have to use 'adddriver' in rpcclient. I've read the manual page for rpcclient, and I printed out a 'Windows 2000 Printer Test Page' to get all the relevant information. This is probably just something

Hi, I am using Samba (v2.2.3a-12.3 on stable Debian Woody) on a bi-cpu server (named MYSRV) acting as a primary domain controller. All works well except for printers where I have severals little problems. I use LPRng (v3.8.10-1.2 on stable Debian Woody) as my linux lpd spooler on my server. I have 2 printers : one HP LaserJet 4000N (named nss.1er) and one HP LaserJet 4050N (named nss.rdc).

A question, althought it is not strictly samba pertinent: I have some Win2k server that offers dial-in to local users. Today all stopped working, but the ones using linux ... However these are not sufficient, so i ask here [since it is probable many people have win2k hosts around) - how to , logging in the win2k server with ssh, restart RAS ? Of couse i can use only CLI programs ... at woest ...

Hi I am trying to use rpcclient's addprinter to install a printer automatically in a large number of XP workstations (+100) But I get the following: 1) connecting to a XP workstation works fine rpcclient -U root sim31%xxxx rpcclient $> 2) adddriver also works fine. Enumdrivers shows this: rpcclient $> enumdrivers [Windows NT x86] Printer Driver Info 1: Driver Name:

This is the EXACT problem I had. Haven't fixed it either.... if I have 10 printers.... upload all the drivers.. for all the OS's... how do I tell which drivers go with which printer? -----Original Message----- From: Andreas [mailto:andreas@conectiva.com.br] Sent: Thursday, June 26, 2003 9:24 AM To: samba@lists.samba.org Subject: [Samba] 2.2.8a, printer driver download: need to use

I began playing around with 2.2.0a2 yesterday. The text docs have instructions for setting up the "print$" share and installing drivers for client download. This involves browsing to the samba share from a W2K or NT server, accessing the "printers" folder, and right clicking on each printer to install drivers. I've managed to get W2K/NT and Win98/95 drivers

Hi, I am trying to set up a Win98 PC to print to a server running Samba 2.2.3a. The server has print drivers installed via cupsaddsmb, which is just a wrapper around the rpcclient addprinter/adddriver/setdriver functions. Calls to rpcclient's geprinter and getdriver functions return valid data. When I go to install the printer on the Windows 98 client, however, things start out OK but soon