search for: 2.2.8

Hello I have a problem with setting up Samba as a AD member server. Environment: Linux tux 2.2.20-idepci (Debian Woody) samba 2.2.8-1.woody samba-common 2.2.8-1.woody smbclient 2.2.8-1.woody (samba from people.samba.org/~peloy/samba) Smb.conf: ---cut--- [global] printer driver file = /etc/samba/printers.def encrypt passwords

Samba List Serve Users: Is there a document or web link that follow that describes the steps to upgrade Samba from 2.2.5 to 2.2.8? The documentation on samba.org the I have read assumes that the install is a fresh install and not an upgrade. Thanks so much, Mark Roth Systems Engineer Mylan Pharmaceuticals, Inc. (304) 598-5430 x6864

Dear All I'm about migrating Samba 2.2.8 to 3.0.13 on Sparc, Solaris 8. Compilation and Installation without any problem. Runs fine with exception of 2.2.8-user validation in the domain (no problems with validation of WXP- and W2K-Client Machines, newly set users (./smbpasswd -a username) works perfectly ). I simply have copied smbpasswd 2.2.8 to the diferent directory of Samba 3.0.13.

Last weekend I upgraded from 2.2.7a to 2.2.8 because of the security problems. Unfortunately 2.2.8 is not only security upgrade but also contains some improvements one of which is backport of ACL code from 3.x Since the upgrade I have problems with rights. In a directory with empty ACL for the creator group and the same default ACL files created by samba have rwx set while files created in shell

Hi Folks, We recently upgraded from 2.2.7 to 2.2.8 to fix the recently discovered bug in Samba. We are now getting intermittent log on failures from Win2K clients connecting to our Samba server (vitals below). Samba 2.2.8 is running on Solaris 2.8 with Kernel 108528-18 Our Samba security method is set to server and we pass along auth requests to an Win2K AD Domain Controller that has NT 4

Hi, I would like to install SWAT to administer Samba on my Mandrake 9.0 server. The Swat file is ver 2.2.8 while my Samba is version 2.2.6. The installation aborts because of version differences. I have tried to upgrade Samba to version 2.2.8 but run into other problems with dependencies. Am I correct in thinking that I have to uninstall Samba first and then re-install the later version? And if

I have to upgrade a 2.2.8a (Debian) installation to 3.0.14a (Debian too). I have quite everything clear but I am afraid I will get into trouble with the filename encoding on disk. The current samba installation has no explicit codepage declared for the file system, and running "testparm" gives only these settings (which are default) for codepages and charsets:

How do i upgrade samba 2.2.8 to the newest 3 version? Is there some documentation about upgrading? I am new to linux/samba Setup is debian 3, Samba 2.2.8 Thnx, Giel

Hi, we run a RH 9 Server with samba 2.2.8 as a PDC. Win 2K/XP Clients can log in without a problem, logonscripts work fine. Now I'd like to update to Fedoroa Core 1 with Samba 3.0.0. I have read the update chapter of the "The Official Samba-3 HOWTO", but have the simple questions: will the new samba server work "out of the box" with the "old" configuration,

Hi! I am running samba 2.2.8 as PDC with ldapsam and acl support. Some users must be have power users or administrators right. In 2.2.8 samba vesion how to patch ou configure samba for see more than one group for a w2k client ? example : toto first group : user second group : power users I can't use samba 3.0 alpha because the server is in product. Thank you

First of all, thank you very much for your fast answers. Congratulations, samba is a great product. This is possibly a newbie question, but I am not able to compile samba-2.2.8 with libcups support. >From the options that appear running "./configure --help", only "--enable-cups" seems to be related to the problem. However, after compilation the "smbd" executable

I just successfully upgraded a server from v 2.2.8 to v3.0.7. When I execute smbstatus or swat it correctly shows v 3.0.7. When I browse thru network neighborhood it still shows v 2.2.8. I stopped samba, and removed /usr/local/samba/var/locks/browse.dat & wins.dat. Then restarted samba. It still reports v2.2.8 thru network neighborhood. In viewing browse.dat it shows 2.2.8. Where is this

Hello, Back when 2.2.2 was the current samba release I came across the following problem when deleting folders in Windows 2000 which I'll repost again below. After I finally got his attention with a few very wordy messages to the samba mailing list, Jeremy fixed it blazingly fast and wrote me back: "I just found the problem and fixed it in 2.2 CVS and HEAD CVS. It was to do with the

I am having some problems adding packages under FreeBSD 2.2.8 and R-0.62.2 I have included the output of "uname -a" below first: == FreeBSD stiegl.niksun.com 2.2.8-RELEASE FreeBSD 2.2.8-RELEASE #0: Thu Dec 10 10:29:07 EST 1998 ath at stiegl.niksun.com:/scratch/obj/compile/STIEGL i386 == The CC in use is gcc (not egcs). The install failed as follows: == stiegl> R INSTALL

Johan says: > After upgrading from 2.2.5 to 2.2.8, our WinXP clients don't recognize our > DFS-root shares as DFS anymore. > When viewing the properties of a DFS root share on a WinXP client, we don't > get the "DFS" -tab page. Luc says: > I'm having the same problems with DFS and WinXP clients since I upgraded > to 2.2.8. > > >Can anyone else

Hi, We tried to upgrade from samba 2.2.8 to 3.0 and got the following problem. We have set samba to be the PDC of our domain (no BDC). And it works fine in 2.2.8 Upgrading to 3.0 using the same smbpasswd file and now when people try to logon to the domain they get this error : The Procedure Number is out of range We have downgraded back to 2.2.8 until we can find a solution to this problem. Does

Since I upgraded from RedHat 9.0b / Samba 2.2.8 to Samba 3.0.10 I have problems with the roaming profiles of my students. Although the log-files show no errors at all, several users reports me that they are loosing files. One time I saw the problem myself, when a user logged in and had not a single file in her 'Personal Files' after logging out and logging in on the same host the whole

HI, I've successfully compile 2.2.8 on Solaris (6,7,8) and Linux. However on Tru64-5.1 I get the following during the make: Compiling smbd/dfree.c Compiling smbd/dir.c smbd/dir.c:649:70: macro "stat" passed 3 arguments, but takes just 2 smbd/dir.c:716:13: macro "stat" passed 3 arguments, but takes just 2 make: *** [smbd/dir.o] Error 1 Any ideas? Ramon Kagan York

My server provider only supports Samba 2.2.8. I need 3.0 to fully appreciate my XP Pro and Microsoft Office 2003 Pro products. I've installed 3.0 but it does not seem to be there. When I run SWAT, it still reports the version to be 2.2.8. Any suggestions? Bill Mann W. D. (Bill) Mann, Sr., LUTCF, RHU The Benefits Office, an RMA Company P. O. Box 1884 Cypress, TX 77410-1884

I have just upgraded two of our samba boxes to 2.2.8 and ended up with partially broken winbind after the upgrade. The machines are slightly different, and so are the symptoms, so here goes: System 1: Was at 2.2.3 compiled from source Feb4/02, using options: "./configure --with-winbind --with-acl-support --with-quotas". Running on RedHat 7.2, installed from SGI's XFS installer