similar to: APW Permissions Issue

OK, I've solved all of my previous permissions issues, now I just need to get the output out. Setup: SuSE 9.0 Pro running Samba 2.2.8a. VMware installed with Windows 2000 Pro guest OS. Epson C84 attached via USB prints fine from Linux with CUPS and also via the commandline using smbclient > print. With data shares, I have no problems. Problem: Print jobs from Windows 2000 never get

Running Samba 2.28 on a SuSE Linux Pro 9.0 system, equipped with VMware Workstation 4. A Windows 2000 Pro guest OS is installed in VMware. Printing from the W2K OS doesn't work. I was able to add the printer as a network printer OK (it appears as a network printer when using My Network Places to browse to the Linux Samba server), but the printer status reads Access Denied, Unable to Attach

Running SuSE 9.2. This problem happens with both the SuSE-supplied Samba on the DVD, as well as the SuSE update rpms to 3.0.9. We even removed all the *.tdb files and recreated the installation from scratch, as always carefully following the steps in S3BE. FWIW, this same config worked previously on this and earlier systems; we did not change anything on this system (other than applying YOU

Trying to follow Chapter 9.3.3 of S3BE to create a SuSE 8.2 Active Directory domain member server. 9.3.3 says heimdal >= .6 is required. I installed the Sernet packages and saw 0.6.2 source is included. Running ./configure after unpacking the heimdal source completes OK, but running make results in the following errors: creating libss.la /usr/bin/sed: can't read

First time I've seen this... Trying to install Samba 3.0.7 from rpms obtained from the samba.org site on a SuSE 8.2 system--very vanilla. Samba has not been installed previously on this box at all. outside:/home/data/Downloads/Samba-3.0.7/8.2 # rpm -Uvh libsmbclient3-3* samba3-3* samba3-client* samba3-win* --test file /usr/lib/cups/backend/smb from install of samba3-client-3.0.7-1

We were trying to build a SuSE 9.1 box in a lab as a Domain Member server in a Windows Active Directory domain where the AD server was running Windows 2000 Server. We found that the instructions in Chapter 9.3.3 were, at least in our case, incomplete. The AD server was managing a private domain, so following the Windows Configure My Server wizard the domain was setup as

First off I have read the SAMBA 2.2 printer documetation and Samba Printing Documentation for 3.0. And searched the Internet through Google and did not come up with much. Maybe it is how I am doing search I don't know. I had some success using CUPS for Point and Click printing using cupaddsmb command. I could get the print drivers to download on W2K and XP. But, I could not get the the

A client has an existing NT4 domain with several NT4 servers. Two of the NT4 Servers function as a PDC and a BDC. We are installing Samba-3 on SuSE 9.0 Pro as a PDC with an LDAP backend, and decommissioning the NT4 PDC at the same time. So far, so good. We can also rebuild the old PDC hardware as a Samba-3 on SuSE 9.0 Pro BDC. Unfortunately however, the NT4 BDC cannot be removed from the network

Setting up a temporary Samba Member Server as part of a domain with real NT4 PDC and BDC machines. In two months the NT domain will go away to be replaced by Samba/LDAP PDC and BDCs, but for now I'm stuck using Winbind. Actually, I'm just stuck! The Samba box is running SuSE 9.0 and Samba 3.0.4-5 installed from the SerNet rpms (ftp.sernet.de). I followed chapter 9.3.2 in Samba-3 By

Just finished TOSHARG (again) and S3 By Example. All of the examples I saw that featured point 'n shoot printer driver installation on Windows clients have Samba performing as a domain controller. So here's the Dumb Question: Is it necessary that Samba be a DC for point 'n shoot printer driver installation to work? Can Samba be a standalone server and have this work? Thanks! Mark

We would like to build a SuSE Professional 8.2 box as a Domain Member Server in a Windows 2000 Active Directory domain, and we are referencing Chapter 9.3.3 of Samba3-By-Example. The version of heimdal supplied with SuSE 8.2 is 0.4e. S3BE references heimdal version 0.6 plus patches. Since SuSE often backports fixes from later versions of products into older versions, the question is: will

(Please forgive the cross posting; I know many SuSE users subscribe to both the Samba and SuSE-e discussion groups and will get this message twice.) I had always been frustrated trying to get SuSE's Firewall2 to play nicely with Samba and support seamless network browsing. After much experimentation and a lot of Googling, I was finally able to get this working. By "working",

We have not worked with Solaris much, and our contract Solaris guy has very little experience with Winbind. So, we are like two blind people touching opposite ends of the elephant and trying to come to a solution. (No comments please on which end I drew...) :-) The question involves authentication in a native mode Windows 2000 Active Directory domain. Is there any reason Samba/Winbind

Had planned to use LDAP and replace an NT4 domain, but trouble with a software vendor (long story) means we need to keep the NT4 domain and use winbind for share authentication for the next few months. So, I religiously followed the TOSHARG winbind chapter, stopping short of making changes to /etc/pam.d files. I can browse and see shares from the Samba box via KDE's LAN browser, but

OK, I fixed all of my winbind problems (I think), but I'm not sure the outcome is optimal, so I'm looking for advice and counsel at more of a philosophical level, rather than a pure technical level. I would be grateful for comments on the following setup: ::Background:: SuSE 9.0, Samba 3.0.4-5 rpms from ftp.sernet.de (quasi-official SuSE rpms, as I understand it). The machine is

Hi I recently tried to install the printerdriver to the samba server (samba 3.0alpha30 on debian) from a windows 2000 client. The APW asked me for a Win2k-server cd for the winnt drivers, although i had them on a disc...which I don't have 2 Questions: 1) does anybody know why the APW will not accept my winnt driver from the driver disc when i comes to install the winnt driver 2) is it

I have heard something about a 'known bug in 2.2.4' so this might already be known. If so, I just want to get confirmation... I have a new samba 2.2.4 running on a RH7.2 box, running solely as printserv. The spoolss printing functionality is working fine: uploading drivers works ok (aside from a few APW quirks if you change drivers). I'm using CUPS as unix printing backend. The

Hi, I have set up my samba server as a print only server. Nothing specific is wrong. The print server is working but I have a couple of questions about using APW to install printer drivers and Windows 7. Linux server: Centos 6 Samba version: 3.6.3 - Default install (./configure; make && make install) I did the usual, net use \\myprinter\print$ /user:root Browse to \\myprinter. In

Hi, I've set up an HP-PSC-2210 printer share accordingly to the Samba-HOWTO-Collection on a debian/testing. Everything works fine until the step "6.8.2. IMPORTANT! Setting Device Modes on new Printers" As soon as I hit the 'properties' menu of the printer, Windows displays the following message : "function address 0x606309ee caused a protection fault. (exception code

I hope someone has some ideas on this problem I've hitting against since yesterday afternoon. I've set up a samba server (samba 2.2.3a on RH7.2) as a PDC as per the combined samba howto docs. I have no problem joining Win9x machines to the domain but cannot add a w2k machine to the domain. It always fails with the message (on the W2K worksation): login failure: unknown user name or