search for: lmstone

...s: creating libss.la /usr/bin/sed: can't read Packages/heimdal-0.6.2/lib/editline/libeditline.la: No such file or directory libtool: link: `Packages/heimdal-0.6.2/lib/editline/libeditline.la' is not a valid libtool archive make[2]: *** [libss.la] Error 1 make[2]: Leaving directory `/home/lmstone/Desktop/Samba Packages/heimdal-0.6.2/lib/sl' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/lmstone/Desktop/Samba Packages/heimdal-0.6.2/lib' make: *** [all-recursive] Error 1 lmstone@smelug-samba:~/Desktop/Samba Packages/heimdal-0.6.2> I also tried with 0.6.3...

...roup = ntadmin create mask = 0664 directory mask = 0775 guest ok = Yes [documents] comment = Reliable Documents path = /windows/D/Data/Reliable Documents/ read only = No guest ok = Yes hosts allow = 172.16.172.128 [data] comment = Top Data Directory path = /windows/D/Data valid users = lmstone read only = No guest ok = Yes hosts allow = 172.16.172.128 -- ______________________________________________________________ L. Mark Stone President Reliable Networks of Maine, LLC 477 Congress Street, 5th Floor Portland, ME 04107 Tel: (207) 772-5678 Cell: (917) 597-2057 Email: LMStone@RNo...

...oup = ntadmin create mask = 0664 directory mask = 0775 guest ok = Yes -- ______________________________________________________________ L. Mark Stone President Reliable Networks of Maine, LLC 477 Congress Street, 5th Floor Portland, ME 04107 Tel: (207) 772-5678 Cell: (917) 597-2057 Email: LMStone@RNoME.com Web: http://www.RNoME.com

...p printable = yes create mask = 0600 browseable = no [print$] comment = Printer Drivers path = /var/lib/samba/drivers write list = @ntadmin root force group = ntadmin create mask = 0664 directory mask = 0775 [data] comment = Data Directory path = /home/data/ public = yes force user = lmstone force group = users inherit permissions = yes writeable = yes oplocks = no level2 oplocks = no -- _______________________________________________________________ A Message From... L. Mark Stone Reliable Networks of Maine, LLC "We manage your network so you can manage your business.&...

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

...ng the OS? (See http://utools.com/UPromote.asp for more info.) Thanks! Mark -- ______________________________________________________________ L. Mark Stone President Reliable Networks of Maine, LLC 477 Congress Street, 5th Floor Portland, ME 04107 Tel: (207) 772-5678 Cell: (917) 597-2057 Email: LMStone@RNoME.com Web: http://www.RNoME.com

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

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

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

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

Can anyone here who has used both explain the differences between the SuSE Samba binaries on samba.org and the ones at ftp.sernet.de? There are more packages available at sernet, and their naming convention is different (samba3*.rpm vs samba*.rpm), which, in the past has created some dependency issues for me with KDE. But, sernet has 3.0.6 binaries for SuSE 9.1, whereas samba.org has only

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

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