Sharity 3.4 improves compatibility, stability
Objective Development on Thursday unveiled Sharity 3.4, an update to its UNIX platform SMB file system that adds several bug fixes and improved compatibility with NAS devices. Sharity allows users to mount shared volumes from Windows, Samba, and other SMB/CIFS servers onto UNIX-based systems such as Mac OS X, Sun Solaris, and Linux, among others. S...
published on Thursday, the 3. July 2008, macintosh-news-network
A workaround for SMB share disconnects
When mounting an SMB share from a Windows 2003 server, I ran into the problem that after about five minutes, the share would disconnect and I would not be able to reconnect to it at all. My system log would say things like this:KernelEventAgent24 tid 00000000 received VQ_NOTRESP event (1)KernelEventAgent24 tid 00000000 type 'smbfs', mounted on '/Volumes/xxxx', from '//xxxx;xxxx@xxx.xxx.xxx.xxx/xxx$', not responding KernelEventAgent24 tid 00000000 found 1 filesystem(s) with problem(s) loginwindow23 1 server now unresponsive kernel smb_iod_reconnect: The reconnect failed to xxx.xxx.xxx.xxx! error = 4 I found a solution, after trying many other things. It is probably due to a bug in the network software of Apple or the server. I use a laptop which normally uses a wired connection with fixed IP as a first choice, but there is wireless connection in the building, too, and my laptop pulls an IP number from the DHCP server at the same time via ...
published on Friday, the 4. April 2008, macosxhints
Security Update 007-009 finally fixes SMB problem
This is not really a hint, but a happy announcement. Since March 2005, I've been unable to connect to my university's server using SMB via the Finder on Tiger. I'd get a "Mount tree phase error -36," which happened only when connecting thru the Finder -- using the smbclient Terminal command did the trick. I finished my Masters degree, and yet this was still broken in the first release of Leopard. This bug appears to be solved, finally, with the release of Security Update 007-009 for 10.5.1. Maybe the 10.4.11 version fixes Tiger's problem, too, but I can't test that...
published on Wednesday, the 23. January 2008, macosxhints
How to unzip SMB-mounted zip archives in 10.4.11
I noticed that in the upgrade to 10.4.11, something broke -- sudently, BOMArchiveHelper would no longer unzip a .zip archive on a mounted SMB share. So I copied the BOMArchiveHelper.app (ion /System/Library/CoreServices/) from a 10.4.10 installation over to the 10.4.11 installation. This fixed the problem.[robg adds: I can't confirm this issue, so if you can, please comment. I never like recommending replacing system components, but in this case, it seems it may be a necessary evil to resolve what appears to be either a bug or an intentional behavior change. I would strongly recommend keeping a backup copy of the new version, however, just in case unforeseen problems develop. As with any hint such as this, be aware that you're changing system files, and anything bad that happens to your machine is your responsibility.]
published on Friday, the 28. December 2007, macosxhints
Mount Windows shares on proper paths in OS X
Often from my friends in Window's land, I get the paths like this:\SERVERsharepathtofile.txtWhen converted to a file URL on the Mac, this will look something like:file://SERVER/share/path/to/file.txtUnfortunately, when I mount the volume on OS X using the normal method, the share shows up under /Volumes with a naming scheme not compatible with the file URL above. My workaround involves making a directory and mounting:Mount the server the normal way (Command-K in Finder).Check Remember Password option when authenticating.Unmount the drive in the Finder -- very important!Make a directory in Terminal with the sever and share name: mkdir -p /SERVER/share.Mount the server with the command mount_smbfs //`whoami`@SERVER/share/ /SERVER/share. NOTE: if your short Unix username does not match your Windows server login, make it match. If it requires a domain, things like NNN	...
published on Friday, the 28. December 2007, macosxhints
10.5: Automount Bonjour-published NFS shares in Finder
Mac OS X Leopard does not discover and automatically mount NFS shares publsihed via Bonjour/ZeroConf as Tiger did. (If you own a Linux based server, you can publish all kinds of Bonjour servers via a daemon called avahi). 10.5 only discovers AFP and SMB Bonjour published shares as far as I am aware. To work around this temporary bug/missing feature, I wrote a simple Ruby-based daemon which you can install so it starts up every time Leopard boots. This daemon simply continuously browses for and resolves published NFS shares and will mount them automatically if they are not already mounted for your user account. Let's hope Apple will fix this soon so we do not need anymore workarounds like this. [robg adds: I have mirrored the source [4KB download] here o...
published on Friday, the 30. November 2007, macosxhints
10.5: A workaround for -43 error mounting SMB shares
After upgrading to Leopard, I found I was unable to mount any of the shares on my Linux file server, getting the following error: The operation cannot be completed because one or more required items cannot be found. (Error code -43) At first I thought this was because of the security configuration I was using on the file server, or perhaps because Leopard had changed the type of authentication method it was expecing from an SMB file server (NTLMv2 for example). It turns out it was a lot simpler -- it was because all of the shares on the file server were set as non-browseable (Browseable = No in /etc/smb.conf. Changing at least one share to be browseable corrected the issue and let me connect to the file server and mount the shares available, regardless of if they were set as Browseable or not. It should ...
published on Monday, the 26. November 2007, macosxhints
10.5: Extended character set passwords and SMB shares
After upgrading to Leopard, whenever I would try to mount SMB shares on my company's network, the Finder would hang interminably on the "Connecting to Server" progress dialog (the network is Active Directory-based).My password, like many that of many people, contains some extended characters. Today I tried URI-escaping the password, and it worked! I was able to connect immediately to all shares. To URI escape a password, try the following:ruby -ruri -e 'puts URI.escape("YourPasswordHere")'Copy and paste the result in the Finder's username/password dialog, and mount away!
published on Monday, the 12. November 2007, macosxhints
10.5: Automount Samba shares in leopard
NetInfo Manager disappeared in OS X 10.5, along with all my automount SMB shares from my Buffalo Linkstation. After poking around the net for documentation on the unix automounter, I came up with this solution to get my automounts going again:According to /etc/auto_master, the /etc/fstab file is now used to dynamically mount shares under /Network/Servers. So you basically just need to transfer the stuff you used to have under Mounts in NetInfo Manager to your /etc/fstab file; mine looks like this:excalibur:/music x url net,automounted,url==cifs://guest:@excalibur/music 0 0excalibur:/photos x url net,automounted,url==cifs://guest:@excalibur/photos 0 0excalibur:/videos x url net,automounted,url==cifs://guest:@excalibur/videos 0 0
published on Thursday, the 8. November 2007, macosxhints
10.4: Another fix for Windows 2003 share mounting
Many users have problems mounting shares from Windows 2003 Servers from OS X Tiger (10.4 - 10.4.10) clients. The following solution has been tested in our enterprise where we have W2K3 servers, physical as well as virtual, and some within a SAN. Problem: From the network view in OS X, we could browse to the servers, but when we tried to connect, we would get the Delete/Fix Alias error. When connecting from the Finder with Command-K (either with smb://servername, smb://ip.address, smb://servername.fqdn, cifs://servername, etc.), we would get the dreaded Error -36 and the Console would show: mount_smbfs: session setup failed (extended security lookup2): syserr = Socket is not connected mount_smbfs: could not login...
published on Monday, the 20. August 2007, macosxhints