similar to: Samba 3.0.0rc1 and 2 servers - PDC and homes

I'm trying to setup a samba PDC and I seem to be missing a few pieces in the puzzle. I've reached the point where I've tried joining an XP workstation to the domain (yes, I've applied 3 changes to the registry that have been mentioned numerous times on the list). The domain join appears to work fine - I get back a nice box from the Windows machine welcoming me to the domain.

In the release notes for 3.0.20rc1, I noticed the following: Changes since 3.0.15pre2 ------------------------ Parameter Name Action -------------- ------ ldap filter Removed I'm curious as to why this was removed and if there's another alternative. Our samba setup makes use of the ldap filter to restrict

Does anyone have perl code that can generate the Samba passwd hashes from a clear text password? I'm aware of the smbpasswd command that comes with Samba but that isn't the best tool for my purposes. I have a local account creation/deletion software that already handles encypting the password to generate unix /etc/passwd files and I need to be able to do the same for the Samba passwd

I am having problems with samba and ldap as concerns groups. We have two central LDAP servers which we use for authentication for many different applications, samba being just one of those. The LDAP servers are Solaris servers running Directory Server v5.2. Our PDC is running samba 3.0.7 on linux. There are several file servers, but the main ones are running samba 3.0.7 on solaris and all

I have Samba 1.9.18p10 running on linux 2.0.35. It's being used largely as a file server for student email, netscape bookmarks, Word papers, etc. from Win95 clients. The configuration is pretty much the defaults. We have an application called Visible Analyst (VA) that needs to be used by a few users. The bulk of the application files are shared but a few need to be available at startup

I'm really desperate for some quick help in getting the samba-3.0.0beta3 compiled with ldap on Solaris 8. I'm working from the tarball and I'm trying to use this configure command: ./configure --prefix=/opt/samba --disable-xmltest --disable-mysqltest --with-privatedir=/var/opt/samba --with-lockdir=/var/lock/samba --with-piddir=/var/run --with-configdir=/etc/opt/samba

i've been trying to get samba 3 to join my AD domain, and have gotten stuck. when I wbinfo -t it returns "Could not check secret" log.winbindd says: nsswitch/winbindd.c: nsswitch/winbindd.c:process_loop(722) process_loop: Invalid request size from pid 5368: 1304 bytes sent, should be 1568 here's my smb.conf incase it matters. # Global parameters [global] workgroup =

Hello, I am running into the same behaviour of nmbd with samba-3.0.0rc1 compared to samba-3.0.0beta3: A few minutes after starting samba nmbd dies with the following messages: [2003/08/19 09:28:23, 0] lib/charcnv.c:(194) convert_string: Required 17, available 16 [2003/08/19 09:28:23, 0] lib/charcnv.c:(194) convert_string: Required 17, available 16 [2003/08/19 09:29:19, 0]

I compiled and installed the latest samba 3.0.0rc1. I see that the binary executable was placed in the default location of /usr/local/samba/sbin/smbd. However, I cannot located the default smb.conf file. I was expecting that the 'make install' script would have copied this file somewhere onto my system. Where is the default 'smb.conf' file located?

Hi, I'm stilltrying to get this running, tried some different ldap libraries but nothing goes on :-( Any hints someone, I know the same problem exists on suse 8.2 ??????? [printsrv4] # gmake all Using FLAGS = -O -g -I/usr/krb5-1.3.1/include -I./popt -Iinclude -I/usr/samba-3.0.0rc1/source/samba-3.0.0rc1/source/include -I/usr/samba-3.0.0rc1/source/samba-3.0.0rc1/source/ubiqx

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the first release candidate of the Samba 3.0.0 code base. A release candidate implies that the code is very close to a final release, but remember that this is still a non-production snapshot intended for testing purposes. Use at your own risk. One of the main additions in this release is

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the first release candidate of the Samba 3.0.0 code base. A release candidate implies that the code is very close to a final release, but remember that this is still a non-production snapshot intended for testing purposes. Use at your own risk. One of the main additions in this release is

Greetings ... Installed Samba 3.0.0rc1, and seem to be having problems with winbind. First question, shouldn't "wbinfo -t" return success? I have "wbinfo -u", "wbinfo -g", "wbinfo -p" and "wbinfo --sequence" returning what seems to be valid information. Second, where does winbind keep the details for "wbinfo

Hello, I tried to configure a share with samba-3.0.0RC1 but after specifying the share name and after I clicked "create", nothing happens. Only the header "share parameters" is shown. I've searched the list archives and a certain Chee Wai Yeung reported exactly the same problem with samba3.0.0beta1 on 09/06/2003 Will this bug be fixed before the final release? Werner

After install samba-3.0.0rc1, I mount the windows share as usual, but it gives an error "client use lanman auth is disable". I've made the change in smb.conf "lanman auth = yes""encrypt passwords = yes" already but it seems not working. Any idea ? ========================================================================================== ¾Ç­^»y/´¶³q¸Ü,

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a release candidate snapshot of the Samba 3.0.1 code base and is provided for testing only. A release candidate (RC) means that we are close to the the final, stable version and is provided for Quality Assurance (QA) purposes. This release is *not* intended for production servers. Use at your own risk. For those utilizing an LDAP backend

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a release candidate snapshot of the Samba 3.0.1 code base and is provided for testing only. A release candidate (RC) means that we are close to the the final, stable version and is provided for Quality Assurance (QA) purposes. This release is *not* intended for production servers. Use at your own risk. For those utilizing an LDAP backend

Hi all, I'm trying to share a directory that contains files with non-ASCII characters (actually, hungarian chars, iso8859-2 or utf8 encoding, I'm not sure - the encoding of ext2) in their name. When I mount the share and try to list the contents of the directory, smbd crashes. samba version: 3.0.0rc1 The shared dir is on an ext2 partition. My system is a debian woody. iconv is installed

I need a little advice on finishing off a Samba PDC. I have Samba 3.0.0RC1 installed and working as a PDC on a Redhat AS 3.0 machine. It authenticates users nicely but the "roaming" profiles don't work. Tailing the samba log, I see the an attempt to access the users ntuser.dat file, which doesn't exist before the first logon, when logging in. The profile directory

here's the tail end of the -d 10 log.host. It seems to not like the encryption type. Which should I be using, and where should I change it? -dave [2003/08/22 09:45:29, 3] smbd/process.c:switch_message(685) switch message SMBsesssetupX (pid 6310) [2003/08/22 09:45:29, 3] smbd/sec_ctx.c:set_sec_ctx(288) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2003/08/22 09:45:29, 5]