similar to: Samba drop-box (on a sub-directory)

Hi: I've just configured a Samba 4 install as an AD DC, following the Wiki page at https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO I've successfully joined a few machines to the domain, and am now trying to add some simple shares. When I add a share to smb.conf, it appears on client machines via \\domain.example.com\sharename but trying to open any shares gives the error

Hi all, Following an upgrade from samba 2.2.8a to 3.0.22 we have been unable to delete files on a samba share using an XP client. We were previously able to delete these files when using 2.2.8a. The problem occurs when we have a particular sub-set of permissions. Directory permissions on UNIX are set to 775 and ownerhips to usera : group1. This should mean that either usera or anyone who

Excuse me for the little flood please, i've just checked it again and now i see SRV1 as master for exedra.cat workgroup, i event can see in the logs Samba name server SRV1 is now a local master browser for workgroup EXEDRA.CAT on subnet 192.168.69.203 So i'll keep digging on how to fix the issue exposed on my first email, tomorrow i'll try to see wether it's an IPV6 issue or

>> I just realized that I omitted an important piece of information and >> that is that I am using a separate EXT4 volume for my shares. I just >> did a test and it seems that shares on the same volume as sysvol and >> netlogon funtion as expected but shares on the second volume have the >> issue.  >> >> I just mounted that second volume with explicit acl

You should be able to unbind ipv6 for the win 10 machine's network interface. does "nslookup SRV1" work? Also, you may want to try running tcpdump or ethereal or wireshark on our PDC and see what traffic is captres. On 05/20/16 13:24, Pau Peris wrote: > I'm completely lost as i can ping SRV1 without issues but i'm starting > to think that maybe Windows tries to

Hey friends, I want to mount some windows shares on Linux workstations in my office.I am using FC3 and my shares are on Windows XP pro and Windows 2003 Server. I tried this command to mount those shares mount -t cifs -o username=windowsusename //windows2003/sharename/anotherfolder /mnt/server the samba then asks for the password of the windows user,i gave the correct password but then Linux

Hi, I have an Ubuntu server acting as PDC on a LAN whose client have WIN Xp professional installed. Domain's users are divided into different groups. Let's focus on only two of them, say group1 and group2. Now I have a share defined in smb.conf as follows: [shareName] comment =

I have a Samba 3.0.23a-1.fc5.1 configured on a Fedora 5 server. It's joined to an Active Directory 2003 domain controller using Winbind, etc. I'm able to connect from various workstations using active directory user accounts/credentials just fine to shares on this server, permissions work, and all is well. I'm guessing this is set up correctly. However, from another Fedora 5 server,

Hi list DFS Links in a separate share seems to work, but in the [homes] section does not. Is this a known problem? Samba is 3.0.26a. /etc/smb.conf excerpts: ---------------------------- 8< ---------------------------- [global] ... host msdfs = yes ... [homes] ... msdfs root = yes ... [dfstest] path = /data/dfsroot msdfs root = yes ---------------------------- 8<

Hi, thanks a lot for your reply. Yes, i enabled wins through "wins support = yes", i also enabled lmhosts lookup and wins on all clients but will check it as you proposed. Tomorrow will try to disable ipv6 on Windows clients following this link https://support.microsoft.com/en-us/kb/929852 Which process did you follow to disable IPV6? I'm also wondering if it's really necessary

Another nicety may be handling network drives. I''ve been using a ruby script which manipulate using the "net use" command to map network drives, disconnect network drives, query to see what drives are connected, etc..., but it''d be sweet if this type of functionality was included in win32 package. Maybe usage like: nd = Win32::NetworkDrive.new(

Hi all, some years ago i configured a `Primary Domain Controller` through Samba and LDAP (slapd) on an Ubuntu machine (13.10) at 192.168.69.203 which should be accessible by the string/name `SRV1`. I must note i did not installed winbind. I've never had any issue and it looks like it's working fine as about 10 Windows machines joined the PDC and Windows users can login against PDC on

On 03/07/2023 14:11, ???? ?????? wrote: > If you insist that it is the expected output, then we have a bug in > all linux distributions. All of them! > For example this is latest fedora: > [kasak at kasakoff ~]$ smbclient -N -L localhost > > Sharename Type Comment > --------- ---- ------- > print$ Disk Printer Drivers > share

I have a Windows Server 2003 system I'm trying to back up to a Linux host. when I access the share with smbclient, I can "see" the files (`ls` returns a list of files, etc) smbclient -U shareuser //server/sharename password But, when I try to actually mount the drive, I get "permission denied" errors trying to access the drive. (EG: using `df`) Running the following

If you insist that it is the expected output, then we have a bug in all linux distributions. All of them! For example this is latest fedora: [kasak at kasakoff ~]$ smbclient -N -L localhost Sharename Type Comment --------- ---- ------- print$ Disk Printer Drivers share Disk IPC$ IPC IPC Service (Samba 4.18.3) SMB1 disabled -- no

Hey Jeremy, Thanks for the advice. I followed your suggestion collected the logged information for a single connection attempt (i.e. smbclient //servername/sharename -U username); I've included the log data below (in the postscript). It looks like Samba is still looking for a Unix user account and not finding one. I should mention that it seems that I am able to authenticate as the user; the

I am setting up Samba between a Windows XP and Fedora Core 2 machine but the FC2 machine is not showing in network neighborhood although I have run the commands below on the FC2 box with no errors. The FC2 box is leitrim and the XP machine is kevinden. [root@leitrim root]# smbclient -L leitrim Password: Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.7-2.FC2] Sharename Type Comment ---------

In reviewing the recent printing-3-0-10_v2 patch, I think I have found an omitted 'release_print_db'. The following patch corrects this. Regards, Jerome Borsboom --- samba-3.0.10/source/printing/printing.c 2005-01-10 15:07:27.060999122 +0100 +++ samba-3.0.10.new/source/printing/printing.c 2005-01-10 15:07:36.784464292 +0100 @@ -1077,6 +1077,7 @@ if (

hello, I'm using samba 3.x and lprng on debian stable. My Problem is described by the following: smbclient -L Sharename Type Comment --------- ---- ------- printer6 Printer lpp6 printer5 Printer lpp5 lpp4 Printer printer4 lpp3 Printer printer3 lpp1 Printer

Hi all, After updating Samba last Friday (from 4.3.3-1 to 4.4.5-1), some issues appeared that weren't there before. Consider the following share (on a domain member): [sharename] path = /srv/samba/sharename guest ok = no writeable = yes acl_xattr:ignore system acls = yes This worked perfectly well until now and Windows ACLs were correctly applied. Since last Friday, however, new files are