similar to: Samba shares inaccessable

Hi All, I am running 3.4.7 on Ubuntu Lucid. I setup ldap auth in PAM and let that handle all the authentication with the 2003 AD Server (where the users groups, ect are stored). It works great, but one little issue is driving me nuts. On some users (can't figure out the difference) when they log into their machine, I see in the Samba logs that the machine_name_ is trying to connect

Hi, I'm now trying to setup a samba server and connected from Win 7 or XP . I want our PC connected to samba using NIS authentication. The Linux OS is red hat 6.0 with samba 3.5.4. So, here is my setting. smb.conf [global] workgroup = TEK server string = Samba Server Version %v security = user passdb backend = tdbsam interfaces = 127.0.0.1,

Hi, i have a lot of entries in my logs which i can't solve, but everything works as expected. my setup: samba pdc - bacula samba bdc - mule Ubuntu 10.04-LTS Server samba 3.4.7 log file entries: Aug 1 08:25:40 bacula smbd[23854]: canonicalize_connect_path failed for service alex, path /\\mule\alex Aug 1 08:25:41 bacula smbd[23854]: [2012/08/01 08:25:41, 0]

On Mon, Jan 08, 2018 at 11:06:37PM +0200, John Doe via samba wrote: > Hi, > > I am having a really strange problem with my Samba shares on Debian > Buster. None of the users can access any shares, which reside on > ZFS-filesystem. Any other share works just fine. For example, if I > create a normal folder to /home with same permissions and replace a > ZFS-share with that, it

Hi, I am having a really strange problem with my Samba shares on Debian Buster. None of the users can access any shares, which reside on ZFS-filesystem. Any other share works just fine. For example, if I create a normal folder to /home with same permissions and replace a ZFS-share with that, it works fine. When accessing any ZFS-shares the following error is recorded: Jan 08 22:39:56

I added one testshare /home/testijako and connected to it with the same credentials as I would connect to ZFS-shares. Then I did the strace to that particular PID and tried connecting to one ZFS-share. There was indeed an error which might have something to do with this issue: Line 2001: lstat("/tank/rex", 0x7fff1f6fb2c0) = -1 ENOENT (No such file or directory) Im sure that folder

Hello! I just upgraded Samba 4.8.2 to 4.8.3 on Arch Linux and user's home shares doesn't work anymore. Downgrading back to 4.8.2 they work again. On samba server smb.conf ... [homes] comment = Lietotāju Mapes browseable = no writable = yes valid users = @Lietotāji invalid users = Guest, @Guests ... $ id uid=1004(Dace) gid=1004(Dace) groups=1004(Dace),100(Lietotāji) $

On 26/10/2019 22:51, tootifrooti via samba wrote: >> Is there any way to still use systemd to manage smbd or do I have to >> just always start it manually? > Did you ever find a solution to this problem? I'm experiencing a very > similar problem right now. When running samba via systemd any access to a > share on a zfs filesystem results in the `make_connection_snum: >

I opted for 'remove the SERVER lines' (since I don't remember why they are in there) - but this hasn't changed the behaviour. The log file contains a different error message, but still refers to the incorrect path --- [2019/09/06 09:43:14.955067,? 0] ../../source3/smbd/service.c:784(make_connection_snum) ? make_connection_snum: canonicalize_connect_path failed for service

On Wed, 4 Jul 2018 20:01:42 +0300 Dāvis Mosāns via samba <samba at lists.samba.org> wrote: > Hello! > > I just upgraded Samba 4.8.2 to 4.8.3 on Arch Linux and user's home > shares doesn't work anymore. > Downgrading back to 4.8.2 they work again. > > On samba server > > smb.conf > ... > > [homes] > comment = Lietotāju Mapes >

I've been having an issue that's been discussed at some length here on the list, but I haven't found a definitive solution to it. The problem is the Win2k connection failing when attempting to connect to Samba 3.0.1 shares in a Win2k3 Active Directory domain. I've installed MIT-Kerberos 1.3.1 and done all the configuration. I'm running winbindd. The following commands work

Hello, I am wondering if this is preferred at this iteration in development. If so, what would be the best way to continue? To build a VM server and have that do file serving, then migrate file serving from the old ad, then join the new VM to the ad server? Vice versa? My reasoning; running sernet (Version 4.0.12-SerNet-Ubuntu-8.precise) with Ubuntu 12.0.2 and since deployment in three different

No problem -?https://pastebin.com/G8pa3bdE <https://pastebin.com/G8pa3bdE> 6 Sep 2019, 10:28 by samba at lists.samba.org: > On 06/09/2019 09:47, gac wrote: > >> I opted for 'remove the SERVER lines' (since I don't remember why they are in there) - but this hasn't changed the behaviour. The log file contains a different error message, but still refers to the

Hello I know that this is about outdated Samba versions, but I have to stick with those. And after trying now for days without getting anywhere I'm looking for help from others. We used an old Thecus-NAS as fileserver (no domain etc). It uses a Samba 3.0.26 which works as we want. Now we bought newer NAS-boxes, but those too use old Samba versions, 3.5.19. This in itself is not disturbing

I realize this may not/probably does not have anything to do with samba per se, but it didn't happen before I upgraded/rebuilt this particular server on 3.0.7. I'll ask anyway in case somebody has seen this... I have ONE user on ONE workstation that occasionally gets locked out of his workstation with the message about a corrupt/inaccessable profile, using a temp (sorry for not

Please help I'm in despair having spent the last few days trying to resolve an issue with my Samba setup. I have 2 shares defined in my smb.conf. The first share is located on my primary disk (partion 1). No problem with this one (I can copy files to/from my Windows XP pcs). I added a second disk (250gb sata) and for now created 1 big ext3 partition. The second share is mounted on

Not sure what caused it. It must be some change to permissions. I know I changed the root password with passwd and changed it back afterwards when problems started. I know for sure I didn't change a thing to the samba config. No firewall running atm. This morning I did smbpasswd as root and set it (to be sure) to same passwd as the original one. But I don't think this matters anymore. I

On 09/05/16 15:50, Fabian Cenedese wrote: > Hello > > I know that this is about outdated Samba versions, but I have > to stick with those. And after trying now for days without getting > anywhere I'm looking for help from others. > > We used an old Thecus-NAS as fileserver (no domain etc). It uses > a Samba 3.0.26 which works as we want. Now we bought newer >

W dniu 2019-09-12 o?22:17, Rowland penny via samba-technical pisze: > On 12/09/2019 20:37, Bart?omiej Solarz-Nies?uchowski via > samba-technical wrote: >> Dear List, > Sorry but this is the wrong list, it should have been the samba > mailing list, not samba-technical, I have cc'ed the samba list, please > reply there. >> >> I need to migrate my Samba NT4

>>work. Connecting from a Windows (from XP to 10) I get asked >>for username and password. But even giving those credentials >>no access is granted. The strange thing is that the user name >>is found in the system passwd and the correct home path is >>used. In the logfile (level 10) I see: >> >>smbd/service.c:996(make_connection_snum) >>