Bug 11107 - SMB with Mac OS X and Excel
Summary: SMB with Mac OS X and Excel
Status: RESOLVED WORKSFORME
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: File services (show other bugs)
Version: 4.1.11
Hardware: x64 Linux
: P5 normal (vote)
Target Milestone: ---
Assignee: Samba QA Contact
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-20 12:44 UTC by Oliver
Modified: 2020-05-17 21:28 UTC (History)
3 users (show)

See Also:


Attachments
log_nmbd (19.94 KB, text/plain)
2015-02-23 08:20 UTC, Oliver
no flags Details
wireshark (32.73 KB, application/octet-stream)
2015-02-23 08:21 UTC, Oliver
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Oliver 2015-02-20 12:44:26 UTC
Hello,

My problem with our Samba server (we tested with two versions 3.6.6 and 4.1.11) is when an user edit an Excel file and saves, another user open is and edit again he got the error message from Excel temp. 8-digit-file will be created and Excel reports that this file can not be accessed. When trying to save again sometimes it works.

I have test it with Windows and Mac. Both have the same Problem. Primary we are using Mac OS X with Excel 2011 14.4.8

This is our samba configuration:

[global]
	netbios name = DEV
	workgroup = DEV
	local master = yes
	os level = 65
	bind interfaces only = yes
	interfaces = 127.0.0.1 192.168.xxx.xxx
	domain master = yes
	preferred master = yes
	server string = PDC
	dns proxy = no
	log file = /var/log/samba/log.%m
	log level = 10
	max log size = 1000
	syslog = 0
	panic action = /usr/share/samba/panic-action %d
	encrypt passwords = true
	passdb backend = ldapsam:"ldap://ldapserver:389"
	ldap ssl = off
	wins support = yes

	ldap admin dn = cn=smbadmin,dc=comp,dc=de
	ldap suffix = dc=comp,dc=de
	ldap group suffix = ou=Groups
	ldap user suffix = ou=Users
	ldap machine suffix = ou=Computers
	ldap idmap suffix = ou=Idmap

	add machine script = /usr/sbin/smbldap-useradd -W -t 0 "%u"
	add user script = /usr/sbin/smbldap-useradd -m "%u"
	add group script = /usr/sbin/smbldap-groupadd -p "%g"
	add user to group script = /usr/sbin/smbldap-groupmod -m "%u" "%g"
	delete user from group script = /usr/sbin/smbldap-groupmod -x "%u" "%g"
	set primary group script = /usr/sbin/smbldap-usermod -g "%g" "%u"

	unix extensions = No
	max protocol = SMB2


[Test Volume]
   path= /daten/austausch_test
   oplocks = no
   level2 oplocks = no
   posix locking =NO
   readonly=no
   valid users = @Intern 
   directory mask=2770
   force directory mode=2770
   create mask = 2770
   force create mode=2770
   force security mode=2770
   force directory security mode=2770
   force group = Intern
   vfs objects = full_audit recycle
   full_audit:prefix = %u
   full_audit:success = mkdir rename rmdir unlink pwrite
   full_audit:failure = none
   full_audit:facility = LOCAL5
   full_audit:priority = NOTICE
   recycle:versions = yes
   recycle:exclude = .*, ~*

And here are the rights for the Files on Samba Server:

9637  4 drwxrws--- 2 usera 1028  4096 Feb 20 12:05 .
9636  4 drwxrws--- 3 usera    1028  4096 Feb 19 17:05 ..
4860  0 -rwxrws--- 1 usera 1028     0 Feb 20 11:59 22009210
4858  0 -rwxrws--- 1 userb   1028     0 Feb 20 11:59 6B2D4000
4855  0 -rwxrws--- 1 userb   1028     0 Feb 20 11:58 8FEB4000
4866 20 -rwxrws--- 1 userb   1028 19094 Feb 20 12:05 Arbeitsmappe2.xlsx
4867  4 -rwxrws--- 1 userb   1028  4096 Feb 20 12:05 ._Arbeitsmappe2.xlsx
4864  0 -rwxrws--- 1 userb   1028     0 Feb 20 12:05 D1D25000
4856  0 -rwxrws--- 1 usera 1028     0 Feb 20 11:58 F63F8210


yours sincerely
Oliver
Comment 1 Jeremy Allison 2015-02-20 18:01:52 UTC
Please upload a debug level 10 log from smbd showing the exact error message you're seeing on the client. A wireshark trace would also help (filter on port 445).

Thanks.
Comment 2 Oliver 2015-02-23 08:20:38 UTC
Created attachment 10768 [details]
log_nmbd
Comment 3 Oliver 2015-02-23 08:21:02 UTC
Created attachment 10769 [details]
wireshark
Comment 4 Oliver 2015-02-23 08:21:56 UTC
I have upload all logs and wireshark trace from the point of the error.
Comment 5 Björn Jacke 2020-05-17 21:28:43 UTC
the nmbd log file is not relevant for this kind of problem. I also didn't see such a generic error in recent releases. I recommend to consult an option from https://www.samba.org/samba/support/ if you still have issues like this.