similar to: UpGraded to 3.0.3-1 from 3.0.2a Wins Installation Problem?

Hello all, did anyone get compiled samba-3.0.2a under HP-UX 11 with winbind enabled? It does not compile libnss_winbind. It gets stucked during compilation of nsswitch/winbind_nss_solaris.c. Any ideas?? It seems to be a problem of a newly added part to be solaris conform. Any help appreciated. Regards Olaf Speder _______________________________________________________________________ ... and

We have samba 3.0.2a running on Aix 5.1. We will be going to AIX 5.2. Trying to find out if Samba 3.0.2a is compatible with AIX 5.2. Thank You! Dan Pecina Unix Administrator/Operations Supervisor John B. Sanfilippo & Son, Inc. (847) 214-4621 dpecina@jbssinc.com

When I tried to mount a share folder from a pathwork vms server, I get the message 'protocol initiation failed'. I get this message since I've upgrade to the kernel version 2.4.25 and to samba 3.02a. I don't get this message with my old config (samba-2.2.28a and kernel-2.4.28). Is somethings has hanged with smbmount between these 2 release ?

Dear list, After the upgrade from 3.0.2a to 3.0.3 I see in my winbindd.log file all the time "user 'root' does not exist" messages. I didn't get these messages with my 3.0.2a samba setup, but after the upgrade to 3.0.3 it is flooding my winbindd.log file, sometimes I get this message every minute in my log file. winbindd.log ========== [2004/05/10 00:01:00, 1]

Hello from france, this little question cause i don't understand this in my samba logs for each of my windows XP SP1 clients : "getpeername failed. Error was Noeud final de transport n'est pas connect?" by thousands !! If someone have an idea :-) See you, ______________________________________________ Emmanuel Fournier - ISCAM - ICT mailto:fournier@ict-toulouse.asso.fr

Does someone have a fully functional PAM using samba 3.0.2a and winbind, on suse 9.0. Mine partially works but does not allow logons to linux. The samba side is working. When I try to logon to xwindows I get "account disabled".

Hi all, I am having problems attempting to upload the printer driver for my Konica-Minolta magicolor 2300DL to Samba through the Windows XP interface. I've read the HOWTO's and everything is set up correctly; I've tried using root permissions as well as printer admin permissions. I've searched far and wide for a fix, but have only found the same question asked a few times. The

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Flowers, Chocolate, a weekend at the beach, and Samba 3.0.2a. Samba 3.0.2a is a minor patch release for the 3.0.2 code base to address, in particular, a problem when using pdbedit to sanitize (--force-initialized-passwords) Samba's tdbsam backend. This is the latest stable release of Samba. This is the version that all production Samba servers

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Flowers, Chocolate, a weekend at the beach, and Samba 3.0.2a. Samba 3.0.2a is a minor patch release for the 3.0.2 code base to address, in particular, a problem when using pdbedit to sanitize (--force-initialized-passwords) Samba's tdbsam backend. This is the latest stable release of Samba. This is the version that all production Samba servers

Hi! How can I maintain users old NT RIDs while migrating to Samba PDC when they start from 1000. The RID to UID conversion algorithm is RID = 2 * UID + 1000 so the user with RID of 1000 would be root (0 * 2 + 1000 = 1000) on Unix. Maintaining the old RIDs is essential for migrating on-the-fly, because re-adding hundreds of computers to domain and losing local user profiles is not an option. Any

On Tue Feb 17 11:14:15 GMT 2004, Andrew Bartlett wrote: >> Any suggestions for things to try (or even a guaranteed solution ;-) ) would >> be very much appreciated. >> server signing = no >Try this as yes. How did you get it work? I've tried the "server signing = yes or auto", but it didn't work. Could you kindly tell us how to set the XP to get it

Hello! Here is request to 2.2.8a: [dm@dm-amd64 /]$ nmblookup -R -U 192.168.6.10 center querying center on 192.168.6.10 192.168.22.224 center<00> And here is to 3.0.2a: [dm@dm-amd64 /]$ nmblookup -R -U 192.168.22.220 center querying center on 192.168.22.220 name_query failed to find name center Certanly, all is OK in DNS, I have in smb.conf dns proxy = yes Today I upgraded 2.2.8a

Hi, we run a samba 2.2.8 server and like to migrate to a faster, new server running samba 3.0.2a. I thought to copy all files from the old to the new one mounting the new shares by nfs. For a test I copied some files using scp. A problem concernes the german umlauts: on the old server they aren't displayed if I "ls" the files while browsing the share works fine. If I copy the

After upgrading from 3.0.1 to 3.0.2a, accessing a shared folder has become unreliable: after being able to access my shares for some time I get an error message "No domain contoller was available" (actually, I'm paraphrasing that one, I unfortunately did not record it verbatim). Host linux log contains the following error message for each access: Mar 5 20:07:08 sharesmb01

I'm runninng samba 3.0.2a on a few machines, ADS security mode, domain member roles. I throw nessus at it, and it can fetch the SID and then list all of the users on the system. I view this as a security problem, is there a way to prevent this?

Sorry for posting again, I've posted my first message in a bad thread ... I promise to pay attention the next time :) So ... We encounter a strange issue with a 3.0.2a Samba server (this problem also happens with previous versions). (Using Debian stable, Samba 3.0.2a, Windows 2000 SP4 client, NT4 SP3 PDC, No WINS) The reproductibility is quite total with these steps : - Copying a quite

Hi! I'm trying to get samba and LDAP work together but there is some problems. I'm using Samba 3.0.2a prebuild binaries (RH9) and openldap-2.0.27. (I've tried also to compile samba myself and the result is same) Everything goes fine, I can change password for users with smbldap-passwd, add users, delete users which are located in LDAP -directory. Everything seems to be ok. While

Hi there, We just upgraded from Samba 3.0.0 to 3.0.2a last weekend. It was working well for a short time but then I restarted smbd and winbindd, and for some unknown reason the user/group databases became corrupt. I had to delete the contents of /var/cache/samba to get it to work again. Anyway, it is back up and running, but now winbindd seems to be crashing about once a day. Attached is an

After connecting to the samba server as a domain user without password challenge, authenticating against a w2k DC (security = ADS), with winbindd running, I can navigate the shares successfully but cannot write to the share. I have done "net groupadd ..." to map windoze-unix groups. I am assuming from the log enties below that my access problem lies in the given errors. How to

Hi, I'm using SuSE 8.2 and I got the source for samba 3.0.2a and I tried to install it. ./configure (w/o any arguments) went ok so I type make and it gives me the following errors: Linking bin/smbd auth/pampass.o(.text+0x59): In function `smb_pam_error_handler': : undefined reference to `pam_strerror' auth/pampass.o(.text+0xcb6): In function `smb_pam_end': : undefined reference