similar to: Difference Between Sernet and Samba.org Binaries?

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

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

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

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

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

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

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

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

We are trying to install a 32-bit SLES9-SP4 paravirtual machine on a 64-bit SLES10-SP1 Dom0 host from scratch. We have two problems: 1. The YaST2 VM creation tool fails to create a vm if a network card is selected. 2. The initial vm boots from the SLES9-SP4 iso file, but then complains it can''t find the installation source. Here is the /etc/xen/vm/file (after manually editing for a

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

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

Are you sure of that ? I thought it was possible... If it is not, I've got another slightly off topic question : how to I demote my former Windows NT PDC (that is now a BDC) to a normal Windows NT server, so that I have no problem with it ? Thanks in advance. -------- Message d'origine-------- De: Umberto Zanatta [mailto:uzanatta@provincia.treviso.it] Date: lun. 26/07/2004 14:09

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",

This problem has been driving me crazy for a week. Fedora Core 4, Cups 1.2.1 Samba 3.0.23a Thanks in advance. -- Curtis Maurand Senior Network & Systems Engineer BlueTarp Financial, Inc. 443 Congress St. 6th Floor Portland, ME 04101 207.797.5900 x233 (office) 207.797.3833 (fax) mailto:cmaurand@bluetarp.com http://www.bluetarp.com -- To unsubscribe from this list go to the following URL and

I have a problem. I've purchased 2 different brand NAS devices that both use Samba in some form as their "sharing" mechanism. When I attach them to the LAN I get dreadful speed. To the tune of under 3.5GB per hour transfers. I've even done tests on the same subnet. Two Windows servers on that vlan can move files at great speeds. Map one of them to the NAS and it crawls. I recall