Q: SMB2 on Mavericks does not work or is totally unstable with Windows client
Hello,
I observe this cazy behaviour when connecting from a Windows 7 client to a Mavericks Server:
a) Map network drive works after asking username/password TWICE
b) selecting a PDF document does not show it in preview, when double clicking: "Document cannot be opened because it is open in another application (or error"
c) selecting a TXT document shows it in preview, when double clicking it: it is opened
d) selecting a XLS document shows it in preview, but when double clicking it: "document is open in another application"
e) selecting a JPG picture shows it in preview, but when double clicking it: "document is open in another application".
f) under certain conditions (not regularly reproducable) the PDF document actually opens, but I am asked again for credentials - and then the credential window speaks of a UserWebDAV Gateway? Could it be that allowing WebDAV somehow mixes all up?
I have disabled filesharing on the server, re-enabled it - no change, I have changed the rights and ACLs according to the advice from Apple Support staff - no changed in behaviour.
I just don't know what else to do.
Setup is: Promise Pegasus Thunderbolt Storage holds the fileshare. Mac OS Mavericks server is configured to publish the share via AFP and SMB and WEBDAV.
The typical thing is: before, when using Mac OS Lion Server, all was working PERFECTLY. And now I have wasted like 8 hours in total ONLY TRYING to get it working right. Is anything at APPLE listening? Seeing the Sh*** state in which the Mavericks server actually is?
One more thing: I migrated from Lion Server to Mavericks Server according to the migration advice from APPLE. Everybody knows now that the mailman is discarded. But, interestingly, while migrating the mailman reference is not taken out of postfix configuration. Which means what? That all configuration rules regarding virtual users are ignored! Happy working with a Mavericks server which rejects legitimate email only because the mailman config statement is still in a line with the virtual user statement. Take it out, and voilá, the virtual users are honored again.
Jan 10 00:24:00 postfix/trivial-rewrite[2104]: warning: hash:/var/mailman/data/virtual-mailman: table lookup problem
Jan 10 00:24:00 postfix/trivial-rewrite[2104]: warning: virtual_alias_domains lookup failure
Jan 10 00:24:00 postfix/trivial-rewrite[2104]: warning: hash:/var/mailman/data/virtual-mailman is unavailable. open database /var/mailman/data/virtual-mailman.db: No such file or directory
Jan 10 01:06:56 postfix/smtpd[5421]: NOQUEUE: reject: RCPT from name.domain.de[x.x.x.x]: 451 4.3.0 <virtualuser@virtualdomain.de>: Temporary lookup failure; from=<postmaster@somedomainsomewhere.org> to=<virtualuser@virtualdomain.de> proto=ESMTP helo=<mailserver.mailserverdomain.de>
Have a look in your mail.log, if you find "Temporary lookup failure" with postfix, then this might be the mailman statement leftover in postfix configuration.
Anyway, I am trying to continue finding a solution for the SMB client connection problem, because everybody says it should work connecting from Windows 7 to a Mavericks server, unfortunately, in my setup it does not work.
Could it be that the fact that the Windows 7 runs on a Parallels Desktop add to the problem? Anyone any experiences in this regard?
Kind regards,
OJ.
Mac mini, OS X Mavericks (10.9.1), Runs as server on my desk ...
Posted on Jan 21, 2014 1:01 PM