similar to: Samba 3.0.2rc2 Available for Download

Hi! I had installed samba-3.0.0-2 with openldap-2.1.25 on debian testing with kernel 2.4.23. All the Windows 98, ME, XP, NT, 2000 were able to join the domain as I was able to set the same SID as the previous version of Samba that was installed earlier. The only problem that arised was the Win-98, ME User list problem that was posted on this list at

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a release candidate snapshot of the Samba 3.0.2 code base and should be considered for testing only. A release candidate (RC) means that we are close to the final, stable release and is provided for Quality Assurance (QA) purposes. This release is *not* intended for production servers. Use at your own risk. Common bugs fixed in this preview

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This is a release candidate snapshot of the Samba 3.0.2 code base and should be considered for testing only. A release candidate (RC) means that we are close to the final, stable release and is provided for Quality Assurance (QA) purposes. This release is *not* intended for production servers. Use at your own risk. Common bugs fixed in this preview

Our computers in our office ceased being able to print to a shared cups printer today. Could not find the cause. Seems the smbd processes are dying. Below is the stack trace produced by gdb bt full. The Samba 'panic action' script, /usr/share/samba/panic-action, was called for pid 5839 (/usr/opt/samba-3.0.2rc2/sbin/smbd). 0x40150a59 in wait4 () from /lib/libc.so.6 #0 0x40150a59 in

Hello list, I upgraded from Samba3.0.1 to Samba3.0.2rc1 and got now following problems: LaserJet printers 6MP (sorry, we have no other LaserJet printermodels) now couse the application to crash. With Samba3.0.1 there was no probem with that kind of Printers. I use the RPM's from ftp.sernet.de for SLES8. Printingsystem is CUPS, with raw printing and serverbased printerdrivers. Has anyone

Hello, I set up samba 3.0.2rc2 (also tried 3.0.1 which had other problems) on Debian sid as an ADS member server: - joining the domain works flawlessly - browsing the samba server via 'smbclient -k -L //samba' works flawlessly - browsing the samba server via 'smbclient -L //samba -U user%pw' fails with 'session setup failed: NT_STATUS_TRUSTED_RELATIONSHIP_FAILURE' -

I'm attempting to set up a 2-way NT4-style trust between samba 3.0.1-2 (from source rpm on redhat 7.2) and Windows 2003 running active directory. The AD server (SANDMAN) trust of my Samba domain works fine, but when I try to use the Samba trust of the AD server I get the following error: [2004/02/04 15:52:34, 3] rpc_client/cli_pipe.c:rpc_api_pipe(462) Bind NACK received on pipe c009!

Message follows this disclaimer -------------------------------------------------------------------------------------------------- This email and any files transmitted with it is confidential and intended solely for the person or organisation to whom it is addressed. If you are not the intended recipient, you must not read, copy or disseminate the information or take any action in reliance on it

>Tait Shrum wrote: >| We have a Samba 3.01 pre3 server that acts as a print server among other >| things. When our users go to the add printer wizard in Windows, it >| doesn't show our samba server! The only way to add a printer is by >| manually entering the path. That's really inconvenient if you don't >| know the path. :) Is there some way we can resolve this?

My W9x clients cannot download printer driver from samba 3.0.2rc1 with cups 1.1.17, while w2k clients do. The W9x clients open the Add Printer Wizard, connect to print$ share, request the ADOBEPS4.DRV file, but they stop at the beginning of the download. Permissions on print$\WINNT\0 directory are the same as print$\W32X86\2. cupsaddsmb was successful. I sniffed the packets while client was

I use Samba 3.0.2rc2 on Suse 9.0 (heimdal 0.6-68) as a Domainmember for File -and Printservices (about 100 Users). The Linuxbox ist added to the ADS, the User are mapped through winbindd. Everything works.. The I upgraded to Samba 3.0.2 and if I start the daemon, after a while follow Error occured if a Domainclient will connect to the Sambabox: [2004/02/13 13:33:43, 1]

Hello the list, When I try to add a w2k worsksation directly from winows it fails (see my previous posts on this list). Now if I try with pdbedit, it fails too :-( here is the ouput : # pdbedit -a -m fred-6csvh95hqd Server's Role (logon server) NOT ADVISED with domain-level security Trying to load: ldapsam:ldap://127.0.0.1/ Attempting to register passdb backend ldapsam Successfully added

Hi All, I experienced the problems with Samba 3.0.2rc1. When the Samba server is joined ADS, I got following Samba panic when access the share by hostname, it worked find if I access the share by the IP address. Actually, this issue was reported by me before. Your help is appreciated. BTW, it hasn't been solved the issue by using Samba 3.0.2 either. Juer [2004/02/27 16:05:25, 0]

Hi, we are running several test installations of Samba 3 on Solaris 8 and Solaris 9. On Solaris 9, there is a strange behaviour in terms of getting secondary group information from LDAP. With later revisions of patch 112960, only /etc/group is interpreted, but there is no query on the LDAP server for (Unix-) group information. Here is a short overview about our results: common configuration:

Well got a problem i gues... i got even more error's in my log files.. some about schannel processing error, or no route to host or get peer name... still everything looks to be working fine.. (got no complaints from the users) but these internal error's i get a fewtimes aday.. dunno, do i need to make a bugreport for it ? or do you need some extra debug info.. l8r Collen

I have a samba PDC/BDC setup with a small number of W2k clients. Not too long ago I set up a set of new servers on fresh Fedora 1 boxes using Samba 3.0.1 and migrated my LDAP to the new schema. It was all working quite well until recently. Suddenly, when I try to change permissions on a windows share (from the windows box), after I give the root password, I get a message that "The

Hi ! I have a problem using an external script to change password : in smb.conf, i have : => passwd chat = "Changing password for*\nNew password*" %n\n "\nRetype new password*" %n\n => passwd chat debug = Yes => log level = 100 => unix password sync = Yes => passwd program = /usr/local/sbin/smbldap-passwd %u The script is called normally, and logs show that the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the first beta release of the Samba 3.0.0 code base. While we are significantly closer to the final release, I will remind you that this is a non-production release provided for testing only. The source code can be downloaded from : http://download.samba.org/samba/ftp/beta/ The

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Samba Team is proud to announce the availability of the first beta release of the Samba 3.0.0 code base. While we are significantly closer to the final release, I will remind you that this is a non-production release provided for testing only. The source code can be downloaded from : http://download.samba.org/samba/ftp/beta/ The

I thought I got them working and it turned out I still have the same problem. This is a domain member server, joined to NT PDC. These commands are all working Ok: wbinfo -u, wbinfo -g, getent passwd, except getent group. It always stops at some point, I noticed these log messages: [2004/01/19 13:09:56, 10] nsswitch/winbindd.c:winbind_client_read(458) client_read: read 0 bytes. Need 1568 more for