similar to: samba locking problem

I'm trying to copy a 400 MB file from a Windows 98 host to a FreeBSD 4.5 Samba server providing access to a FAT32 filesystem. I've got "strict allocate = no", but from what I can see with debug set to 10, it is doing a ftruncate which takes about 50 seconds to complete. It appears that Windows gets impatient and generates an error (while Samba is still waiting for the

Hi list, )2nd try bcs. of missing attachements). Following (very strange) problem: An ordinary windows user has mapped a drive F: on \\LUN1\Programme (running samba-3.0.20b-3 debian). The program "F:\Network\PMail V3\Pegasus Mail\winpm-32.exe" is being started, this works. But after about 10 minutes, the same program start fails with "invalid path or filename". When

Hello, We're experiencing a problem with samba after an upgrade, which only occurs when using a strange combination of software. The problem only occurs with samba 2.2 and higher. This problem does not occur with samba 2.0. We tested this with samba 3.0alpha17, 2.2.2, 2.2.4, and 2.0.10 First off, sticking to procedure, TESTs 1-11 as described in DIAGNOSIS.txt succeed. I've gone as

Greetings, I am running 2.2.7a as a domain controller on RH 8.0 When I attempt to create a folder I get the following "warning" "You may not be able to access the files created in the folder .... Do you want to continue?" If I continue everything goes file (the folder is created and I can access it). I find a file in there called TESTDIR.TMP. I thought it may have been a

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ~ Dear List, ~ My Win2k and WinXP workstations are endlessly complaining about can't ~ create central copy of the user profile, because of ..., or something ~ like that (in hungarian). When I'm trying, even as root to change the ~ acls of anything in the profile share I get an error, with other shares ~ this is working perfectly (I have ACLs

I'm having lots of hassles and troubles since I moved to 1.18p10: 1\ Why do I need a smbpasswd and have to have a user equivalent on the unix machine when an NT user wants to print via an smb printer? My NT/Win users shouldn't need to know anything about unix and I don't want to tell them "you have to log into my unix machine and invoke

Prior to upgrading from RH7.0 to RH7.3 our Samba filserver worked perfectly. Now we are having locking problems. Initially Iused the same samba binaries built on RH70, I tried rebuilding Samba and reinstalling but it had no effect. If user bon opens an M$-Office file they frequently get a 'file is already in use by bob'. Sure enough smbstatus -L shows the file locked by bob, but bob

if((group_c = *lp_force_group(snum))) { BOOL is_guest = False; some lines deleted token = create_nt_token(uid, gid, current_user.ngroups,current_user.groups, is_guest); must_free_token = True; } set_sec_ctx(uid, gid, current_user.ngroups, current_user.groups,token); /* * Free the new token (as set_sec_ctx

Hi All, I am having a problem with Samba that seems to be a bug. I say this because I read the archives and they described a problem similar to mine and were told that it was a bug in older version of Samba and the latest version should have it fixed. I am running what is essentially a RH 7.3 on a 1.4GHz Athon with 1GB or RAM. I compiled Samba 2.2.5 in /opt/samba-2.2.5 and am using the following

Hello list, I've got a problem concerning locking of files with a share on a nfs mounted NAS. samba server is 2.2.8a installed from SuSE-RPMs the NAS is mounted with following line in fstab: <IP-Number>:/vgroup00/data02/data /mnt/nas01 nfs rsize=8192,wsize=8192,soft 0 0 I tried to save a file from word which lead to a aprox. 1 minute hang of my Win2k/SP3. The log of the

Sorry if this issue has come up before. I have been using samba on a NetApp filer successfully for some time but I recently upgraded my samba server to Suse 9.0 Professional. I am trying to use the 'classic samba' version (since I don't know any better) and am having problems with file locking on my shares. Here is a transcript of the log.smbd that shows some incompatibility between

Hi, Is there a known issue with FreeBSD 5.2.1 and Samba 3.0.4? I am getting file corruption when copying to a local FAT32 drive (mounted under FBSD) from a Windows XP Pro workstation. There doesn't seem to be any pattern in the corruption. If I mount an UFS drive, everthing is fine. I'd also like to find out if the corruption would also have affected file updates, and not just new file

Hello I've got some strange problems with Samba-3.0.4. When using roaming profiles, keyboard layout is set to english (instead of norwegian) and a lot of programs wont load correctly. Setting log level = 3 revealed a lot of errors after the netlogon-script had executed (and all shares correctly set up). I switched to log level = 10 to get a more detailed view of these errors (show below).

I'm still having some problems with 1.9.18p10 on a DEC Unix 4.0e machine (this machine was upgraded from 4.0d last week). The smbds can take up to 20% of the cpu at various times. Anyways, I've been through all this before with the mailing list and a number of people who have attempted to help me out. Thanks to all of you. But, I have some more info which may or may not be useful.

I was trying to copy swf file (35MB) from a windows machine to my samba share. It told me "There is not enough disk space". However, it lets me copy it in another share. I didn't notice anything different with the share I am having problem with. I noticed the following messages in the log: [2005/08/10 13:56:47, 0] locking/posix.c:posix_fcntl_lock(657) posix_fcntl_lock: WARNING:

I really appreciate all your responses on this. I might not have fixed it by looking at samba logs but i noticed there was directory in user unix directory with wildcard * as folder name once i removed it, samba showed up all the files and directory. am not sure what would * as folder name caused this behaviour may be samba was trying to interpret * as something else not sure...... or it was

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 After 2GB of transfer, files stop being written by Samba. I keep getting Jun 12 11:29:37 nasserver smbd[8715]: [2005/06/12 11:29:37, 0] locking/posix.c:posix_fcntl_lock(656) Jun 12 11:29:37 nasserver smbd[8715]: posix_fcntl_lock: WARNING: lock request at offset 558761983, length 1 returned Jun 12 11:29:37 nasserver smbd[8715]: [2005/06/12 11:29:37,

What u wrote here: >>once again this folder stdc++.txt does exist.... ...reminds me on having charset problems with samba, doing the same stuff here until I set up the right charsets. Also, u see in logfile: >>call_trans2qfilepathinfo: vfs_stat of New Folder2231113/.directory failed >>(No such file or directory) And u say: >>but this directory NewFolder2231113 does

Hello again, I would like to thank Giant Wang and Miquel Bonastre for their responses to my query in "Samba Digest 1734" regarding simultaneous passwd changing for users via Samba. Their comments were helpful, but have not solved the problem. For those who do not have a back log of the Digests, the problem is that with unix password sync=yes, users are not able to change their own

There seems to be a few people having this problem, but not much response. I've dug into the logs, and while I don't know exactly what I am looking at, I think I may have found something that may make sense to someone. A short recap. Samba was working fine, until I did a Debian security update, which upgraded my Samba to 2.2.8a. Now, I can create files on a mounted Samba share in a