similar to: Samba, Cups, Windows driver and PPD File updates

Greetings, I'm seeing am odd printing problem on a Windows 2000 machine - the machine is NOT in the Samba controlled domain, but in a different "real" NT 4.0 controlled domain. The user on this machine is able to mount "shares" from my Samba servers, but since moving to 2.2.3a his is denied access to printers. Strange is he can access files on the same server that

Greetings, Similar to the other CUPS thread, but not the same. Samba 2.2.5 built on a Sparc Solaris 9 box with Cups 1.1.5. I've set up Samba to print with Cups as outlined in the docs. I am able to download the generic Adobe print driver to my Windows 2000 clients but the Windows 98 clients are asking for a local driver to be installed. Looking at verbose output from cupsaddsmb,

I have Samba 2.2.6 complied against Cups 1.1.16 on a Sparc system running Solaris 9. Cups has replaced the stock system V lp spooler on this system (original packages removed.) Cups working from UNIX command line is A-OK. I have been working on setting up Samba to play nice with cups. I have followed the instructions from both the Cups and Samba websites to set up downloading of the

Greetings, all I seem to run across more interesting issues with printing... Anyhow, by Samba (2.2.3a) print server (Sun Solaris 8) somehow forgot about all of its printer drivers. I went through the process of re-loading them from a Windows 2000 client machine using drivers downloaded fromn HP for all but our laserjet 4 printers. I was able to install the Windows 2000 drivers OK, but

Greetings, All, I've run into an interesting problem with Samba 2.2.2 and dealing with printer drivers for Windows 2000. I can install the drivers for nt4/2000 okay, I can install the drivers for win98 okay. The part I thought was really neat was how I could set the printer options for Windows 2000 in the driver install so that when a user installed the driver the correct printer

Greetings, I have Samba 4.4.7 running on several Sparc boxes running Solaris 9 as member servers in an Active Directory environment. (I do not control the AD configuration) I am able to connect to the servers using windows clients and smbclient - the problem I have run into is when I try to add domain users to local groups on the Samba servers I am told the users do not exist. As these

On 11/16/2016 04:34 PM, Rowland Penny via samba wrote: > Provided that the group urbanweb exists in /etc/group and your users > are shown by getent passwd or id, then you could try the unix tools > i.e. usermod -G urbanweb ADDOMAIN\\1001362 > > Rowland Greetings, Thank you for the response. the matching UNIX group exists. Been using local groups on Samba for years. # getent

Greetings, all, I have a fresh install of Samba 2.2.7 on a Solaris 9 machine. Stand alone, not part of a domain. Testing with a stand alone Windows 2000 professional client with service pack 3 installed. I am having problems setting defaults for the installed printer drivers and I have been unable to load Win98 drivers to go along with the W2k drivers. Printers being tested are an HP LJ

Greetings, I hope someone can tell me if what I want to do is possible with Samba or not. I have been searching for info and found a number of people with similar problems, but not an answer. I have a Samba server (3.2.4) running on a Solaris 10 machine which is a member server in Active Directory (AD). I am using winbind. The AD users can access the samba server shares and UNIX services.

Greetings, I recently upgraded an AD member server from Samba 3.5.15 to Samba 3.6.9 and found that I had lost all the existing local group mappings. I see that the group mapping file has gone from group_mapping.ldb to group_mapping.tdb. I asked on this list as well as searching the web, Samba documentation (which still seems focused on version 3.5), and Samba Wiki and found nothing on a

On 11/17/2016 02:42 PM, Rowland Penny via samba wrote: > On Thu, 17 Nov 2016 14:32:16 -0500 > Robert Martel via samba <samba at lists.samba.org> wrote: > >> >> On 11/16/2016 04:34 PM, Rowland Penny via samba wrote: >>> Provided that the group urbanweb exists in /etc/group and your users >>> are shown by getent passwd or id, then you could try the unix

Greetings, I have an elderly installation of Samba 3.5.8 running on 10 Sparc servers (and 3.5.12 on Solaris 9 servers with the same issue) set up as Active Directory member servers. Since we've laid-off everyone else around here I have not had the opportunity to update the Samba installation - and have not needed to as it has been very solid. Suddenly last Friday the Samba servers

Greetings, Attempting to build samba 3.5.6 on Solaris 10. Running make after the configure process has completed yields: make: Fatal error in reader: Makefile, line 1396: Extra `:', `::', or `:=' on dependency line Not that I have not had issues of late building Samba, but this id the first time it went of the rails so early in the building process. -Bob --

Greetings and Happy New Year, My samba print server is still running 2.2.2 and I've not been able to upgrade it past that point. I have not been able to get the printer drivers to behave properly in ANY later version. Currently I am testing Samba 2.2.7 running under Solaris 9. I have been using HP Laserjet 4000 and 8150 postscript drivers in my testing. I am seeing two distinct

... When I install the W2K drivers and set the options for each printer, only users in the printer admin group see the customized settings. Normal users only see the default settings that the driver originally installed, not the ones I edited (such as duplex installed, additional papertrays and output trays, and paper/tray assignment.) The normal users are also unable to alter these

Greetings, I recently upgraded my print server from Samba 2.2.8a to 3.0.7 and all is working well except banner pages for the print jobs. I am getting them now an I don't want them. This is under Sun Solaris 9 using the stock LP spooler. In my smb.conf I have had set (for years now) print commands of like the following: print command = lp -dnodis2 -c -o nobanner -s %s; rm %s The

Greetings, I have been playing with 3.0.8rc2 on a test machine to get ready to upgrade my samba 2 PDC to Samba 3. I ran across an issue with mapping the domain admin group to a local UNIX group on the server and I wanted to know if the behavior I saw was normal or not. The Samba server is a Sun ultra 1 running Solaris 9, user and group information is kept in plain old

Greetings, This is not a problem with Samba as I see it but I am hoping that others on the list have some ideas for working around the issue. Our central computer services group scans all the campus networks using Nessus and some custom rules to look for security problems. What I am seeing within my college is my Samba PDC getting beat-up when the scans go though. They scan a block of PCs

Greetings, All, To start off, I think everyone has done a WONDERFUL job with Samba, and I'd enjoy my job much less with out it. A remarkable effort from everyone that has contributed to the effort. Now I will contribute my printing problems. I have Samba 2.2.3a running on top of Sun Solaris 8 and I have been seeing a number of printing related problems. From what I am seeing on the

Greetings, I have a number of samba servers that will need to become Active Directory (AD) member servers. The testing I've done so far with default mapping has worked just fine. I configured a server to be an AD member server, joined it to AD but was unable to access it from a client PC - I get prompted for authentication on the client which shouldn't be happening. The log file