nsaice.blogg.se

This message occurs when I click the name of the SMB server in the Finder sidebar.

The only thing I can get out of Console.app is: 5/15/11 7:36:40 PM /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder SharePointBrowser::handleOpenCallBack returned 64 Or should I look for the solution rather on the server side? (I know that other SMB shares seem to work fine in my network) Diagnostics Is there any way I could get Finder (or the underlying SMB client) to know which credentials to use? Well, as soon as I unmount all shares, I have to go through the same procedure of manually logging in as "guest" again, which I find quite annoying. If I select it in the sidebar, I get a list of all shares available, because I'm connected as "guest", obviously: Now, I can select one of the shares to connect to, and I'm finally connected to the server. I can however press ⌘ + K and enter the server's name manually, which gets me to this window: Now, when I click the name of the device in Finder's sidebar, I get the black "Connection failed" bar, with the option "Connect as.".

As I'm in a trusted environment, my shares are accessible as guest rather than with a combination of username and password. The same issue arises when I attempt to use AFP.I have a QNAP NAS that offers a few SMB shares. The parameter is rejected by the "testparm" command on the the version of Samba I am running (3.4) The compiling issue is resolved by changing the parameter to "unix extensions = no" but still fails to resolve the issue. I found a thread that describes my problem almost exactly suggesting to use the "unix extensions = off" parameter in the global section of the smb.conf file, but to no avail. Other clients should be able to read the file during this time, but not be able to write to it. My goal is to be able to lock a file (744) from other users when its in use or open on a client machine. No matter which permissions I set for a file on the server, the Mac ignores them and changes the permissions back to 766. I'm having some serious permission issues with Mac client machines (OS X Snow Leopard) connected to a UNIX server (running CentOS) through Samba.