Escolar Documentos
Profissional Documentos
Cultura Documentos
Page 1 of 10
I am beginning to wonder just how much quality assurance work Apple put into its latest Mac operating system: Mac OS X 10.9, Mavericks (http://www.zdnet.com/os-x-mavericks-gets-official-release-date-today-7000022283) . Sure, Mavericks can make Macs faster (http://www.zdnet.com/macbook-air-with-os-x-mavericks-like-getting-a-new-system7000022411) mavericks-gmail-compatibility-7000022481/)
, but did anyone test it to see how it worked with Gmail (http://www.zdnet.com/concerns-rise-on-os-xor network-attached storage (NAS) and file servers using the Server
Message Block 2 (SMB2) file transfer protocol? It doesn't look like it.
Is Mavericks really ready for prime time? If you need to use network drives, it doesn't look like it. SMB2 is a later version of the old SMB protocol. Both were introduced by Microsoft for local area network (LAN) file sharing. Since SMB showed up in the late 1980s, the SMB family has become the most common LAN file sharing protocol. It's used by most network-attached storage (NAS) devices and file servers. SMB2, which was introduced in Windows Vista in 2007 (http://blogs.technet.com/b/josebda/archive/2008/12/05/smb2-a-complete, is now supported by Samba and Linux (https://wiki.samba.org/index.php/Samba3/SMB2) and, so Apple says, by Mac OS X.
redesign-of-the-main-remote-file-protocol-for-windows.aspx)
Page 2 of 10
in earlier versions.
Fortunately, there are ways to mitigate this problem. First, and both crudest and simplest, is to force your Mavericks Mac to use SMB instead of SMB2. To do this you'll need to create a nsmb.conf file in your home directory
(http://cammodude.blogspot.com/2013/10/os-x-109-mavericks-workaround-forsmb.html)
several ways to do this. First, you can up a terminal from Utilities and paste in the following line from the shell prompt: echo "[default]" >> ~/Library/Preferences/nsmb.conf; echo "smb_neg=smb1_only" >> ~/Library/Preferences/nsmb.conf The above must be entered as a single line with a return at the end. You can also create this configuration file with a text editor such as vi from the terminal. Do not, however, try to create this file with a word
processor. You'll end up with formatting characters in the file that will ruin it for configuration purposes. You can also try forcing Mavericks to use the older SMB variant, Common Internet File System (CIFS) (http://technet.microsoft.com/en-us/library/cc939973.aspx) . To do this, simply edit your server connection URL so that it uses CIFS (http://www.tuaw.com/2013/10/27/did-mavericks-kill-your-network-drive-access-heres-a-fix) . Use the Finder to choose the "Go" menu and select "Connect to Server..." (or just use command-K) and type "cifs://YourServerName" and hit Return; the server should mount. If it doesn't, try entering the share's designation as well (http://www.novell.com/support/kb/doc.php?id=7005113) , e.g. "cifs://YourServerName/YourDriveName." However, none of these may work depending on whether your file server or NAS supports SMB or CIFS. While they're almost certain to support them, their default settings may not support these older protocols. In that case, you or your network administrator will need to set them to support SMB and/or CIFS. The best thing you could do which is probably too late if you're already reading this is to hold off "upgrading" to Mavericks. It seems to me to be one good update away from being ready for prime time. Related Stories: Concerns rise on OS X Mavericks' Gmail compatibility (http://www.zdnet.com/concerns-rise-on-os-x-mavericks-gmailcompatibility-7000022481/)