similar to: 3.0.25 smbclient problem

Hello, I've been testing out 3.0.25 before putting it into production and came across an issue. As a simple example.. in a share definition root preexec = echo "hey there, hi there, hello" > /tmp/hiya.txt works fine under 3.0.24 not so under 3.0.25, /tmp/hiya.txt isn't created. Cranking up the debugging and using some other similiar tests it seems to me that Samba is in

Samba is a domain member server authenticating to a MS-Windows domain controller. With 3.0.7 and all previous version for the past few years I could map a Windows to Unix userid in the username map file like so.. fred = fredw His home directory was then accessible as \\servername\fredw so \\servername\%username% from a Windows NTx client. I make EXTENSIVE use of that functionality. I missed

More precisely what I've discovered is, at least in the cases of 2.2.8a and 3.0alpha22, when a 64-bit Samba is built with Sun's Forte compiler you'll end up with something incompatible with Mac OS 10.2.3. I always compile Samba myself with Sun's compiler to produce a 64-bit Samba. Well yesterday it came to my attention that Mac OS 10.2.x doesn't work with whats on my main

Good morning, I have a working Offline Files setup w/Samba 3.0.24 (FreeBSD 6.2 host OS) and a Win XP SP2 client. Upon updating to Samba 3.0.25, the XP client's offline cache would show (as viewed via the Offline Files Folder) that synced files are write-only ('User W' in the Access column). When offline, theses files appeared to be available via Explorer and double clicking would

I truely believe I've stumbled across a bug deleting directories. The bug is either with Windows 2000 or with Samba 2.2.1a and 2.2.2. I'd tend to think it was a Windows bug except that the problem does not occur against earlier versions of Samba. I've duplicated this problem deleting directories to Samba versions 2.2.2 and 2.2.1a in various configurations running on several

I'm having trouble with files being marked read-only in Windows because the Solaris file owner does not have write-permissions on the file; group-write is allowed: -r--rw---- 1 user group 32 Feb 13 14:19 testfile.txt I thought that setting "store dos attributes = yes" for this share would allow the "read only" setting to be stored in extended attributes, but it

Sparc Solaris / UFS file system. I have some ACL's set up for a handful of users and its all worked flawlessly with every incarnation of Samba I've used over the past couple years, which would be most. Last Friday evening I upgraded from 3.0.11 to 3.0.13 and some of the users I have some ACL's set up for promptly found Monday that they couldn't save new Excel files, they'd be

Hi folks, I've been testing out Windows Vista Enterprise today. It defaults to only using NTLMV2 authentication. I'm testing with Samba 3.0.23d running on Sparc/Solaris 8. Samba is configured with security = domain The password server is a Windows Server 2003 domain controller. I've joined Samba to the domain. I simply can't get Vista to connect unless I change its security

Hi. I have problems, when upgraded from samba sernet 3.0.24 to 3.0.25 (too early ?): 1) always must change password, when log in to windows XP professonall - samba 3.0.25 PDC - password expired 2) I can't browse widnows network on client machine - network broswer in WinXP don't respond - just hangs 3) I cann't priny any more to printers attached to another widnows machines

I'm happy to be able to announce that Xapian 1.3.4 is now available. Please note that 1.3.x releases are development releases - they are made to encourage earlier and wider use and testing of new and changed code. Our record with 1.1.x was very good - all the bugs I am aware of were either in new features, or were also present in the corresponding 1.0.x release. But if you main concern is

I recently added a 60Gig HD to my little linux server at home with the intention of sharing it via Samba to all my PCs which run Windows 98SE. I really want to use vfat file system on it. The server is running Mandrake 8.1, so kernel 2.4.something, and the Samba that came with it. Much to my disappointment I quickly discovered poor performance copying files to it, the copy is like slow to get

I'm working on trying to get Samba 3.0.23c to work with Vista and I've run into a snag. If a share is set up for security = share, and protected with a password, when I try to mount the share using Start->Run->\\server\share, the password is rejected by Samba for about the first 10 seconds, but after that, it lets me in. I've tried all the common suggestions such as changing

I use the sernet samba packages on debian sarge and have problems after upgrading to 3.0.25 with rid mappings. My rid configuration for 3.0.24 looks like this idmap backend = rid:ISC=500-100000000 idmap uid = 500-100000000 idmap gid = 500-100000000 after updating to 3.0.25 I get a core dump of winbind (log at the end of the post) with these settings. I tried to use the new configuration

Hi, I've spent a lot of time digging the last couple days and seen some talk about how now with 3.7.1p1 the PAM challenge response requiring keyboard interactive on the client is "right" and no longer a kludge. I understand that. Unfortunately I've got a bunch of users who's client (www.ssh.com's client version 3.2.3) doesn't function without a kludged server.

Hi, I'm currently using v3.0.24 in production and all works well. I'm testing 3.0.25 to see if I'm going to have any problems with it if I have to upgrade. I have a problem with the "force group" setting if it is set to a local Unix group. This same setting works fine in 3.0.24 but I'm denied access to the same share in 3.0.25. If I comment off the "force

Dear Samba List, I just updated my samba setup from an older Version (3.0.22) to 3.0.24 (Debian Version). Now unfortunately "valid users" does not work anymore. I have a Samba Server with security=ADS (win 2003 SP2 Domain Controller) in an all local Unix Users Setup! Thus all my usernames are available either way, by Unix "getent" and "winbind -u". Probably this

Hello list, A change in smbclient between 3.0.24 and 3.0.25c breaks [1] the gollem filemanager [2] and maybe others. In particular folder creation is broken unless the folder is a top level folder on the share. To create a subfolder "level2" in the folder /level1 of a share gollem executes this command: /usr/bin/smbclient "//1.2.3.4/sharename" "-p139"

We've updated from 3.0.24 to 3.0.25 and we've noticed some minor problems such as some clients had to reboot in order to mount the share. And the log is now showing this warning all the time: WARNING: Winbindd not running, mapping ids with legacy code [2007/05/17 08:57:37, 2] passdb/lookup_sid.c:sid_to_gid(1435) We are thinking to revert to the previous version 3.0.24 which works

Gerry, It looks like 3.0.25 breaks "stand alone/no winbind/no domain" servers. This is remeniscent of the 3.0.23b SID/GID problem. The only thing that jumps out at me is that you can't access your home share and other shares just quit working. Looking at the log files, I see this: [2007/05/14 15:24:55, 10] smbd/open.c:share_conflict(389) share_conflict:

We've recently migrated my entire University including faculty and staff from Novell to Samba. There's typically 700+ clients connected to the samba server at any given time and thus far there are about 400GB of client's files on the server. Basically every Microsoft Windows user generated file (Word, Excel, whatever) of the entire University gets stored on my Samba server. Obviously