similar to: static wins entries for failover shares -- do Microsoft clients get confused?

I am trying to use static wins entries, as stated in the Official Samba Howto Collection. One Samba server (VServer) is with wins service enabled. Another (Server1) is not, but it has the wins server in its smb.conf. When I set wins.dat at VServer: "SERVER1#00" 0 192.168.6.231 192.168.1.231 66R "SERVER1#03" 0 192.168.6.231 192.168.1.231 66R "SERVER1#20" 0

Hi, I have a samba server 3.4.0 running on a ubuntu karmic and there is a problem with the File Converter of Microsoft Office. When someone opens a .docx or .xlsx file with Office 2003 + File Converter, does some changes and tries to save the changes an error occurs: (something like) The file is locked for editing by another user. Afterwards the file is deleted. Here is a part of the

My systems is rh9, I installed the latest wine (20040914), with a RPM package downloaded from http://rpm.pbone.net/. when I execued "wine setup.exe" (Note: it is in the hardware, not in CDROM. I am not for sure whether it is a problem). The following errors occured. fixme:msi:MsiEnableLogA 00000516 "c:\\windows\\temp\\Office 2000 Premium Setup(0008)_MsiExec.txt"

Hi! I need to add static entries to my Samba 3.0.9 WINS server but I can't. Let's explain: The "Samba Collection Howto" chapter "Network Browsing" , section "Static WINS Entries" tells that I can edit my "wins.dat" file (/opt/samba/var/locks/wins.dat) to set the TTL of some entries to 0 . No matter if I edit the TTL of some existing entries

Hello, I have a problem with files locks on share. My server is running FreeBSD 10.2 (amd64) with ZFS pool (raidz) for windows share and samba 4.3.3 (ROLE_ACTIVE_DIRECTORY_DC). The server has approximately 100 users accounts and computers accounts. >From one windows workstation I open a file e. g. text file (file.txt) the smbstatus shows DENY_WRITE and everything seems right. But when I open

Hi, I'm trying to add static entries to the wins.dat file, as per The Official Samba 3 How-to guide but can't get it to work. If I add entries and just leave it be, the server responds with unknown host and If I restart nmbd it removes all the entries (static) that I manually added. Am I doing something wrong or is this a bug ? Brett

I have a need to setup the recycle vfs object on our server. On my test server, I have all of the shares on a single drive and have put the following into each share: vfs_objects = recycle recycle:repository = [Actual Path and Partition that the share is located] recycle:directory_mode = 770 recycle:keeptree = Yes recycle:touch_mtime = Yes recycle:versions = Yes It works like a charm. All

Is the issue below addressed in 3.0.25b? (no freebsd port available yet so I'm still at 3.0.25a) I can't see anything specifically about this in the release notes. I just want to add that I've also seen this behaviour on a windows xp x64 client. It's a pretty serious problem.. so I'm also thinking I may have to revert to an earlier version if it doesn't look like a

Hello, everyone, I'm seeing some inconsistent behavior across SMB clients when configuring shares using the "msdfs proxy" parameter, and was hoping to get some advice from the community on this. My issue is that various SMB clients seem to behave differently when this parameter is pointed as a path that includes a sub-folder under the root share. So, given the following share

Hello all, Got samba with AD integration and extended ACL up and running. Here is what I am trying to do. share1 in smb.conf: [share1] comment = share1 path = /mnt/data/share1 public = no writable = yes printable = no valid users = @DOMAIN+group1 user1 and user2 are members of group1 user3 is not user1 creates

We restored to 3.0.23d after update to 3.0.25a because of strange dfs behavior. the detailed situation: on msdfs root server 'samba' ls -lR dfsroot/: drwxr-xr-x appl1 dfsroot/appl1 lrwxrwxrwx share1 -> msdfs:server1\share1 [dfs] comment = "SaMBa DFS root" path = /path.../dfsroot # next line does not work prior 3.0.25 !!! # hide unreadable = Yes

On Thu, Jan 05, 2023 at 01:28:55PM -0500, Nick Couchman via samba wrote: >Hello, everyone, >I'm seeing some inconsistent behavior across SMB clients when >configuring shares using the "msdfs proxy" parameter, and was hoping >to get some advice from the community on this. My issue is that >various SMB clients seem to behave differently when this parameter is >pointed

Sorry for my previous email it was something wrong with my email client. Now is the corrected version: Hello, I have a problem with files locks on share. My server is running FreeBSD 10.2 (amd64) with ZFS pool (raidz) for windows share and samba 4.3.3 (ROLE_ACTIVE_DIRECTORY_DC). The server has approximately 100 users accounts and computers accounts. >From one windows workstation I open a

Hello Jeremy, I think you missed a "/" in: mount --bind /share1/DVR /medium/DVR mount --bind /share1/Audio /medium/Audio mount --bind /share2/Video /medium/Video mount --bind /share2/Backups /medium/Backups BR, Matt On Thu, Feb 13, 2020 at 5:15 PM Jeremy Allison via samba < samba at lists.samba.org> wrote: > On Thu, Feb 13, 2020 at 04:45:16PM -0500, Hal Vaughan via samba

Hello, I have a problem when uploading file to samba server when the share's volume is under lvm snapshot. I always got "The specified network name is no longer available", this happens when uploading large files like 500MB and the volume has a lvm snapshot(even 1 snapshot). If there are no snapshots, everything is ok, I can transfer large files without problem. my client is

Hi guys, I haven't seen any replies to this, but im seeing the exact same thing with Fedora 7 samba (with all the currently available patches). using winbind into a an ADS realm. My samba is 3.0.25b. Clients are XP, 2003 r2 SE and EE 32bit, 2003 r2 SE 64 bit. All work ok for a while, then suddenly start doing the same as below. I.e., when mapped it looks fine, then some time in the future

Hello, I'm using rsync 3.0.9 to backup several NFS shares from a fileserver, mounted over NFSv3, to a local RAID on a backup server. Both servers are running Ubuntu 12.04 server LTS. The fileserver's filesystem is ext4. The NFS shares are mounted on the backup server as follows: fileserver:/mnt/storage/share1 /mnt/share1 type nfs (ro,tcp,bg,soft,intr,addr=192.168.1.1)

List, I'm having trouble accessing shares, and I'm getting conflicting indications on whether I've successfully joined the domain with my PC and Samba server (which may bear on the share problem). I really could use some help; I've not been able to recognize anything in the docs or via Google that helps. I'm running SUSE 9.3 and Samba 3.0.21a, and I'm trying to

I encountered strange behaviour of "msdfs" when using together with "netbios aliases". E.g I have in smb.conf: [global] netbios name = server netbios aliases = server-oldname .... host msdfs = Yes [share1] path = /var/samba/share1 [share2] msdfs root = Yes msdfs proxy = \penguin\share2 .... From a windows (XP) machine I can now see: \\server\share1 and

I am having trouble with the %S Macro being expanded to an unexpected value. We have a section of disk where each directory under that directory is to be it's own share. This looks like: /export/ /export/share1 /export/share2 . . /export/shareN Rather than listing each share uniquely in the smb.conf, we put this in the global section: default service = export along with all of our