Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - pumpir

Pages: [1]
1
This is probably Apple issue, but good to know:
Client 1 from Mac OS (El Capitan) connecting smb://zentyal/share , connected and everything works fine. When client 2 from different machine (does not matter, if Mac or Win) connects and add folder or file to this share, client 1 cannot see these changes in Finder. But not alwyas, sometimes information is updated, sometimes not. If information is not updated, disconnecting and reconnecting share helps and client 1 can see everything correctly again.  There is some specification - if client 2 is Win and saving there MS Word file and there is character - (hyphen) used in the filename, client 1 can see in Finder only tmp file (which is MS Word creating during saving proccess and after that renaming it to the correct filename). Maybe it happens without hyphen in a filename, but not in my case. If client 2 creates new folder, client 1 sometimes see it, sometimes not.

I spent whole evening and no clue.

In the morning, with fresh mind, there was a small success.  If I use old smb (cifs), everything works fine. It looks some incompatibility or error in SMB 2, SMB3 protocol from Apple? Or combination of some settings in Samba and SMB2, SMB3 Apple protocol implementation?
I don't know, because  on my home Synology NAS all versions NT1, SMB2, SMB3 are working fine with Mac OS !!!!  Why?

For now I  "resolved"  it by adding:
client max protocol = NT1     parameter in /etc/zentyal/stubs/samba/smb.conf.mas 
server max protocol = NT1     parameter in /etc/zentyal/stubs/samba/smb.conf.mas
After samba reboot, clients are using NT1 version and there is no problem for MacOS connections.

Thanks for this tip:   https://forum.zentyal.org/index.php/topic,27225.msg99673.html#msg99673

2
I went back to kernel  linux-image-3.19.0.47-generic, from that time  BUG: soft lockup - CPU #1 is gone, but problem with permission denied to share in Directory under Zentyal is still there ...

3
The same issue with Zentyal 4.2.2 linux-image-3.19.0-49-generic and linux-image-3.19.0-51-generic, usually it happens within 1-2 days, today I changed grub to use linux-image-3.19.0-47-generic, hope it helps. Thanks for tip.
 I had another issue, not sure if also connected with this, it is described here:
https://forum.zentyal.org/index.php/topic,27402.msg100165.html#msg100165
 

4
Directory and Authentication / Zentyal and MacOS clients
« on: February 19, 2016, 09:34:34 am »
I am using Zentyal 4.2, there is one share called  "testshare", there is a folder structure. When connecting from Windows client, everything is fast and smooth. When connecting from MacOS client, following issues are there:
- very slow directory browsing
- slow files opening and saving
Google search done, many suggestions tested, no success. Also trying different client SMB versions from different MacOS versions, results very similar.  Are there some suggestions?
Thanks.

5
I instaled Zentyal 4.2, made configurantion (not installing and using it for the first time), everything looks fine for several days (before I started with adding data for testing - connecting via smb to share, creating directories, copying files, set permissions from Windows 10 machine - member of Zentyal domain) . Suddenly it says I have no permission to connect to whole share. I checked permissions and ACLs (from SSH console), everything looked OK (in whole structure /home/samba/"sharename"). Even domain administrator cannot connect to share - nobody. Creating new share in "Directory under Zentyal", the same result - permission denied. I am using it on virtual machine (KVM), when this happened, I had backup several days old, I restored this backup (where everything was working correctly) and was comparing smb.conf , shares.conf and permissions, everything the same as in wrong machine.
I started with restored machine, it happened again within few hours, but difficult to recognize when (it has affect after share reconnect).
If I create share under "File system path" (ie. /mnt/testshare), everything works fine.
Any suggestions?
Thank you.

Pages: [1]