similar to: setting shares

I'm having some trouble adding machine names to Samba. I've added a user under linux for the machines that I need and they have a $ entry at the end of them. I've also added a user entry for each computer with smbadduser, all to no avail. Does anyone out there know of a good source of reference material on this subject? Thanks, James

> I have another samba server and upgraded it to samba4. testparm returns > clean with the old config (ROLE_DOMAIN_PDC) and starts up fine. smbclient > seems to work fine. > > The next thing now is to try and make it a domain member so it can auth > against AD. > > Thanks, Andrew, I appreciate the pointers. You might want to take a look at "Integrating Red Hat

Thanks Rowland & Miguel, Sorry, I didn't know setting in share overrides setting in global. So I've in the global section "vfs objects = recycle acl_xattr", but it doesn't work either. getent group <GROUP_NAME> command returns the group name correctly (DOMAIN\group_name:x:10006:). Nicolas Le 23/02/2024 ? 10:23, Rowland Penny via samba a ?crit?: > On Fri,

I have configure this folder share in samba : [share_name] Path = /home/folder With this acc?s : share root:group_name 2770 In my group ?group_name?, I?ve user1, user2, user3. Therefore the 3 users have complete acces in this folder. But in this one I have to add other folder shared : - /home/folder/ufold1 - /home/folder/ufold2 But I want the user1 have only an acces in the

Hello everybody. I have configured a linux box with samba 3.0.25b It's joined to a windows nt4 domain. It's running winbindd. Now I would like to create a local group with 'net sam createlocalgroup group_name' and adding members from the windows nt4 domain. I need this local group so I can assign permission to file/directories. This is my smb.conf: [global] workgroup =

Hi folks, Does anyone have a clue of how to by/pass the group scope value when creating a group in AD by using the net tools? I can delete an AD group, add/remove members from a group but I can't create a group. I reckon it's because of the group scope value (even Power Shell/New-ADGroup prompts for it) $ net -U $ADMIN_USER -S $DC_ADDRESS rpc group add $GROUP_NAME -c $OU Error

Okay, we're doing a bit of system revamping at my work since our last file server crashed and burned in a horrible tragic failure (hard disk died). Anyways, we've stepped it up a notch with some nice hardware and the fileserver will be running linux (Redhat 9.0 currently). Anyways, I'm currently running into an issue. (I'm using samba 2.2.7a-8.9.0 for reference). Anyways,

On Fri, 23 Feb 2024 08:13:08 +0100 Nicolas Boiss? via samba <samba at lists.samba.org> wrote: > Hello, > > I have a Fedora server, part of a domain, on which various shares are > configured. > > For one share, I want to set up permissions according to the groups > to which the users belong. But it doesn't work. For example, I want > the share to be accessible

Hello, I implemented two functions reshape_long and reshape_wide (see full working example below) to reshape data frames. I created several small examples and the two functions seemed to work properly. However, using the reshape_wide function on my real data sets (about 200.000 to 300.000 rows) failed. What happens is set all values for X, Y and Z were set to 1. The structure of my real data

Hi, so you would like to restrict the access to the share definitions? E.g. only "User1" should be able to access the Share "Private"? Have you had a look at this documentation? https://www.samba.org/samba/docs/using_samba/ch09.html (This doc is quite old but should still apply). We're running a seperate fileserver which is joined to the SAMDOM DC. Then we're using

Hi, I have server setup as BDC on a subnet different from the PDC. The BDC can auth fine against the PDC and they can browse each other just fine. The problem is on Unix side of the BDC. When I do a 'wbinfo -g' or 'getent group' each group fit the format 'DOMAIN\group_name' and the PDC does not. This is causing problems when synchronizing as the group perm is being set

Samba is too technical for a guy like me. I find it hard to configure my standalone samba server to respect the SAMBA PDC. From the documentation i need to install winbind and all those highly technical things. I hope we can make things simple guys! Our Setup: Samba Server PDC Clients: Win9x, WinXP, Linux I'm on a linux machine. I hope I could share and specify a valid user without

Racer X, The simple answer I have; No Regards, Robert Adkins II IT Manager/Buyer Impel Industries, Inc. Ph. 586-254-5800 Fx. 586-254-5804 -----Original Message----- From: Racer X [mailto:racer_x_0x0@yahoo.com] Sent: Tuesday, January 14, 2003 1:27 PM To: samba@lists.samba.org; Robert Adkins Subject: [Samba] Password protect shares without creating user accounts Hi, Could you tell

Hi All, I am new to configuring samba and am trying to setup a few read-write shares on my FreeBSD box. Unfortunately, it's proving very difficult to access my shares: 1. When I use the smb client, I see the following error: vanadium# smbclient -L localhost -U James added interface ip=192.168.0.2 bcast=192.168.0.255 nmask=255.255. error connecting to

I am supporting a site that allows members to upload release files. I have inherited this site which was previously existing. The goal is to allow members to file transfer to and from their project area for release distribution but not to allow general shell access and not to allow access to other parts of the system. Currently rsync and old scp has been restricted using a restricted shell

I have an NFS4 server exporting a folder, and a Samba server importing that folder which it then turns around and shares over Samba. I would like Windows machines accessing this folder and its sub folders to be properly restricted according to ACLs. The NFS4 server is running CentOS 5.7 and is NFS exporting an EXT4 folder. The Samba server is running CentOS 6.0, and Samba 3.5.4-68.el6_0.2. On the

Hello Marc, Am 24.10.2013 21:00, schrieb Marc Muehlfeld: > Hello Thoralf, > > Am 24.10.2013 20:32, schrieb "Th. S?ldenwagner": >> is it possible to hide/restrict access to the home drives of our samba >> users when accessing them directly via netbios address? >> >> The server is running at school and there are several pupils who have >> the ability

Hi, I am running 2.2.5 and I would like to know if the "restrict anonymous" as been implemented correctly, as it was supposed to behave from the start, in order to deny ALL anonymous connections as stated in the man : "When restrict anonymous is yes, all anonymous connections are denied no matter what they are for." Ive been reading some dev mailing lists and someone said

Samba 4.1.4 AD/DC (git) on Ubuntu 12.04.4 LTS X64 Hi all, It seems that client's authentication on shared folders is only done via login/password in AD. This means that a user coming in office with his personal laptop can connect to the shared folders he has rights to, using his AD credentials, even if his laptop is not joined to the domain. Is there a way to restrict shares to only

I'm setting up a samba primary domain controller in Debian woody and the users are logging into the domain fine and can access their shares. I would like to restrict the listings of available shares to only authenticated users of the samba domain. I know this works in a win NT4 domain, how does one do it with samba? This is the listing I get from an nt4 pdc (belongs to a different domain than