similar to: VMware Printing Problem - Access Denied, Unable To Connect

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

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

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

SuSE 8.2 with Samba 2.2.7a, smb.conf is at end. (Hostname=outside) This box runs VMware with a Windows 2000 client configured as a workgroup member (hostname=RNOME-W2K). I created a Linux user account for the W2K machine, edited etc/passwd to add a "$" at the end of the username for the machine, and added the machine account and my user account to the Linux ntadmin group. I then ran

Hi, I just installed Red Hat 9 on a Dell Latitude D600 laptop. Then I installed VMware 4 and installed Windows XP as the guest operating system. I want to run Samba on the Red Hat 9 host to share files with the Windows XP guest. Each OS individually is running fine. I compiled Samba 3.0.2 on the Red Hat host, but I can't start Samba. I try starting it with "/usr/sbin/smbd -D",

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

Hi, I'm trying to follow through the printing howto and I'm having a bit of a nightmare trying to use the rpcclient -c 'setdriver ...' utility. I keep getting WERR_ACCESS_DENIED errors. I tried setting up a root user with smbpasswd but I get NT_STATUS_LOGON_FAILURE if I try to run rpcclient with -U root. I think there must be something fundamental to authentication that I

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

I see you are using cups. I had the same problem It is a cups problem. First install a RAW printer in CUPS. Second allow cups to receive jobs from a remote host. By default it doesnot. -- Groetjes/Regards Kees van Hoof

(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

By mistake.... err a learning mistake... I accidentally placed this email on samba-technical first. I now believe that this is the proper list for questions regarding Samba installation issues. - Jerry Problem synopsis: What I can NOT DO is access any files to open or read. I always get 'access denied', but I can create, copy and delete files. Info: Platform: SuSE 10.2, Samba 3,

I want to set up a Samba Server (Cactus_3) as member server in our NT4 domain (PDC is Cactus_1, BDC is Cactus_2). We have about 50 client workstations most of which are WinXP but we have a few Win2K and Win98 machines. Shortly we will migrate off the NT4 servers but in the meantime we wish to test some real time scenarios. It is for this reason that I want SSO so the tests are transparant

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

I'm running a CUPS print server with SuSe 9.0 Pro with printers shared through Samba. I've recently upgraded from 2.28 to 3.010. My server is a member of an NT 4 domain. I run winbind to authenticate users to the domain; however, I also allow guest printing because many laptop users' machines are not domain members. There has been a change in guest printing behavior after the

Hi, I'm running samba 3.0.1 on SuSE9, server is configured as member server in a NT4 controlled domain. now the problem: it's possible to upload drivers; it's possible to set default settings/ setting printer configuration; Client: add new printer -> network printer -> browse for network printers , and here is the problem, the samba isn't shown as a print server,

Hello all, I've gotten the printing subsytem almost working - I think. I am able to install my print drivers to the server IAW the instructions found here: http://us4.samba.org/samba/docs/man/printing.html The drivers are being installed to /etc/samba/drivers/W32X86 IAW /etc/samba/smb.conf by following the instructions above This line specifically seems to do it: [print$] path =