similar to: Latest versions of Solaris SPARC binaries

Hi all, i compiled Samba 2.2.5 with gcc on a Sunblade with Solaris 2.8. Last month i compiled Samba 2.2.4 on the same machine without problems. The following options i used: ./configure --with-winbind --with-pam --with-quotas I got the following warnings: Linking bin/wbinfo Compiling nsswitch/winbindd.c Compiling nsswitch/winbindd_user.c Compiling nsswitch/winbindd_group.c Compiling

Hi All, To clerify the problem, firstly I have to give you some details of our environment.. Linux Redhat 7.3, Samba 2.2.4, Win2000 workstations... We are trying to use Linux servers as file and print servers. Our client are Windows2000 workstations which will use Linux boxes as file and print servers... Problem with : winbindd Signal 11 error Suspect : When winbind starts, it can get all

Hello I saw that samba 2.2.5a is out. Whats the difference with 2.2.4? Is there currently any problem with 2.2.4 or 2.2.5a? I want to uppgrade my server from 2.2.3a so i want to know if there are any thing that i should be prepared for. Ive heard that 2.2.4 had some printing problems? Is this true? /Alexander

Hello. With version 2.2.4 I had the the following problems that seem to be solved in version 2.2.5 pre1 1. Problem with German special character - when listing NT domain users with "getent passwd", "getent group" - when showing NT groups with "id" 2. Using "veto files" with wildcards caused high load on my machine 3. "hide unreadable = yes"

Hi all, I am building samba-2.2.4 on Solaris 8 (Intel) with gcc-2.95.3, not Sun compiler. I have noticed that it tries to build winbind nss libs using -KPIC instead of -fPIC (which is the correct for my conf). It looks like configure overlooked the fact that I have gcc and assumed that all solaris boxes would use Sun compiler. I managed to compile them by substituting -fPIC for -KPIC in the

Firstly, apologies for asking this again, I see that it cause a mail loop lasttime. We've setup samba(2.2.4, no patches) and installed the printer drivers using the methods decribed in the printer_driver2.html. The drivers have appeared to have install correctly, we you right click on the printer share and select properties the relevent tabs for the printer driver appear. However, once

When 2.2.4 was released, I updated my cvs and did ./configure and make (no special options). Since I came in somewhat early today and nobody was around I did the make install. Everything ran fine until I tried to load a particular file and I'm receiving the following error and unable to open the file on a network share. If I place the file on a local drive it loads fine. Permissions and

Hi everybody, i just tried to install v 2.2.5 but i get the following mesage from configure : -----snipp---- checking for ldap_start_tls_s... no -----snipp---- grep in /usr/include tells me : -----snipp---- 486dx66:/usr/include # grep --line-number ldap_start_tls_s ldap* ldap.h:1075:ldap_start_tls_s LDAP_P(( 486dx66:/usr/include # -----snipp---- Looking into /usr/include/ldap.h from line

I'm having a couple of problems with Samba 2.2.4 on Solaris 8. First problem - Using gcc 2.95.2, everything comes out OK, but shared libraries seem to fail at install phase. The output indicates that they're non-existent. Second problem - VFS examples, audit and recycle. They build OK, but there are all sorts of undefined references at runtime. Could these two issues be due to the use of

Has any version of Samba been tested for compatibility with the new Windows Active Directory? We will be upgrading our NT domain to 2000 and creating Active Directory. Currently our solaris samba 2.0.7 server is configured to authenicate users from our NT domain controllers. Will we encounter problems with the 2000 upgrade? Thanks in advance, Cynthia --------------------------------- Do You

I have been using samba 2.2.2 for quit awhile running with security= share in my company. I looked into the /var/lock/samba and found a growing file unexpected.tdb. Is there a way to trim it down while samba is running or do I have to start and stop samba? Is this an expected behavior? TIA Joseph Loo

Hi, I am planning on upgrading our Samba servers to a more current version (presently we have 2.0.6) Just wondering if 2.2.4 is the best version to implement, or if an earlier version would be more stable, e.g. 2.2.3a I ask this question because I've seen a few messages on the mailing lists suggesting errors in 2.2.4, but don't know if these are real errors or just people with a bad

Hello all, I've got a strange problem with Samba 2.2.4. I'm able to associate print drivers to printers (raw queue in cups). My clients are able to see that the drivers belong to the printers, and they download them, but as soon as the server reboots, I lose my driver associations and I need to once again specify a driver on the windows end. The Print server was an upgrade from Samba

Hello We have one Samba 2.2.5-pre running as PDC of our domain, in one Solaris 7 box. There are also a winNT 4 machine used as a Printer Server (we prefer to use another machine to print services). After one printer instalation, on printer server, I try to configure permissions in the "Security" tab, "Permissions" button. I click in "Add" button and include

Hi Jerry I'm still able to recreate failures in with 2.2.4 when interleaving file creation/writing from W2k and NT4 machines to a Samba server. I orginally reported this in 2.2.2a, also 2.2.3: http://lists.samba.org/pipermail/samba/2001-December/063396.html http://lists.samba.org/pipermail/samba/2002-January/063483.html http://lists.samba.org/pipermail/samba/2002-February/067221.html I sent

Under Samba 2.2.4 (and possibly earlier), smbpasswd (when run locally) only really reads the first 8 characters, as opposed to the full password. Obviously, this can cause mass confusion. :) The fix is pretty simple (I would offer a diff, but this is the kind of thing the configure script should check for...) - under Solaris getpass() will only return 8 characters - you must use getpassphrase()

I have a Red Hat Linux release 7.1 (Seawolf) Samba 2.2.4 PDC and fileserver built with --with-ldapsam. The clients are either win9x or WinY2k. Authenitcation, etc... all works great. But print sharing is a real pain. Under 2.2.1a printing worked great, but our VOIP phone system wouldn't joint the domain until we upgraded to 2.2.4. Initial testing of 2.2.4 made it seem like everything

Trying to upgrade from 2.2.3a to 2.2.4 broke our Solaris 8 PDC. We see the following issues: - Compile flag -KPIC is not valid for gcc, does not seem to bread build - Now looks like directory /usr/spool/samba is needed, but not created by install - smbclient -L hemlock fails with login problem: [2001/10/16 10:43:28, 0] smbd/password.c:connect_to_domain_password_server(1295)

I had no problem configuring WINS lookups, via nsswitch and libnss_wins.so, under Linux. The problem I am having is on Solaris. I am working with the 2.2.5 release of Samba. Everything in the nsswitch subdirectory compiles cleanly. wbinfo, which uses winbindd, resolves WINS entries no problem. (When I am running winbindd, that is.) Solaris appears to use /usr/lib/nss_wins.so.1 rather than

Hi All, I am running a samba 2.2.4 domain controller and since the upgrade from 2.2.3a have been getting the following error messages in the logs. tdb(/etc/samba/secrets.tdb): tdb_oob len 943289144 beyond eof at 8192 Running Redhat 7.2. Anyone know how to fix this / root cause of the problem? I have a domain with 300+ machines so I'm hoping for something non-destructive. Regards Anthony.