Parallels Desktop 8 for Mac is lets you seamlessly run Windows and Mac applications side-by-side

Mountain Lion File Sharing Tips &


OS X 10.8 SMB and AFP file sharing & printing with Windows

On this page:

Mountain Lion Server hosts Sage accounts data

Dave Hall reports that Mountain Lion Server unexpectedly can host Sage data:

Once upon a time I used to host a Sage (the UK accounts package) data folder on a Mac Leopard server and it worked. Snow Leopard and Lion killed this. However, i am happy to report that it appears to be fixed in Mountain Lion server. I look forward to test the SMB sharing with AIO copiers and the re-introduced FTP service in Server GUI.

If you've tried this

Reader says OS X 10.8.2 will not connect to Windows shares

Delarado can't connect to Windows SMB file servers and clients from the Mountain Lion 10.8.2 Finder. He gets a permissions error. He can, however, connect using Terminal to type a mount command. He posted his report in the MacWindows Forum. We post it here as well: I've been trying for a while now…

Clue for reader's Mountain Lion file sharing issue?

Sean Alexander responded to our report "Reader says OS X 10.8.2 will not connect to Windows shares". He points to an Apple article that talks about the difference in mounting SMB shares for different versions of OS X: The user did not say whether or not he had the problem with a different version…

TIP: Suggestion for Mountain Lion access to Win shares

T. Grades responded to our report "Reader says OS X 10.8.2 will not connect to Windows shares" with a suggestion for using a specific path in the Connect to Server dialog of the OS X Go menu (also accessible by typing CMD-K). Grades reports: I happened across this question and thought…

Reader reports Mountain Lion problem printing to Windows print queues

Anne Balish is seeing printing errors when printing to Windows print queues from Mountain Lion:

I have a printing problem that has vexed me for years. I stumbled on a work around that's done the job until Mountain Lion came along. When setting up Macs to print to Canon ImageRunner series printers via our Windows print queues, I can't immediately select the printer driver during the initial setup or I end up getting a prompt asking if I want to print via unidirectional or bidirectional printing. Regardless of which option I choose, I'm unable to print. If, however, I leave the printer driver as generic during the initial setup, add the printer, then go back and change the driver to the proper Canon driver, I don't get the prompt and it prints just fine. Another workaround was to print via straight IP directly to the printer, bypassing the Windows queue altogether.

With Mountain Lion, I'm unable to go back and change the print driver after the initial setup of the printer so my only option is to stick with a generic driver which means my users lose all of the multi-functionality of their printers. Additionally, printing straight IP to the printer has the same problem in Mountain Lion whereas earlier versions of the OS didn't.

If you've seen this problem

TIP: Changing printer driver in Mountain Lion for Windows printer

Thursday, January 3, 2013

Bruce Johnson responded to a previous reader's comment about not being able to change a printer driver with Mountain Lion for a printer connected to Windows. Johnson describes how to do it with the Mac's CUPS interface, accessible from a web browser, and a command in Terminal:

It's possible, but a pain in the butt. First go to the CUPS web interface at http://localhost:631 . Cupsd will tell you that the web interface is disabled and to enable it run: cupsctl WebInterface=yes

To do that, open Terminal and do: sudo cupsctl WebInterface=yes

Then you can go back to the CUPS Web interface and manage the printer. Under Administration, select Manage the Printer, log in with an administrative account username and password and you can then change the drivers about four screens into the management process.

As a general rule, I've never had much luck printing through Windows print queues and have always just printed directly to the printers. Also, this kind of nonsense about printer drivers (among other things) is why we abandoned Canon printer/copiers for Ricoh's.

If you've tried this please .

Reader's Mountain Lion filesharing problem with LaCie NAS

Ed McConnell reports that upgrading to OS X 10.8.2 prevents AFP connections to a LaCie network attached storage (NAS) device: I have two LaCie Big5 Network 2 NAS units. I have recently upgraded my Mac and I am running 10.8.2. I can no longer access the Big5's as a "Registered User"… (Read more here.)

TIP: Connecting to older AFP NAS devices with Mountain Lion

Geoff Howard sent us a solution to the problem of getting Mountain Lion to work with some AFP network attached storage (NAS) devices. He basically describes Apple's solution for Lion, which is to enable older authentication methods on the Mac, but adds more detail… (Read more here.)

Readers' file sharing problems after 10.8.4 update

Although Apple's OS X 10.8.4 update for Mountain Lion is supposed to improve SMB file sharing, two readers reported problems with SMB fill sharing in a Windows environment after updating. Vitaliy completely lost connectivity to his Windows server:

I have updated to 10.8.4 from 10.8.2 because I had problems with the trackpad (jittery), but I lost the connection to the SMB server. The old links and the old address in Connect to Server do not work. I have read of the similar problems on the forums.

Ulrich Wesche's found that at first, the 10.8.4 update fixed problems with Windows servers in Active Directory. But the improvement didn't last:

I have had immense problems with my (late 2011) iMac in a Windows Active Directory surrounding. Took minutes to open a Windows share, sometimes opening was not possible. A lot of trials, Centrify and all sorts of "hacks" did not solve the problem.

Having installed 10.8.4 I reached all Windows shares within seconds, wonderful! Now five days later it all comes back, some shares cannot be reached at all, connection to some takes 5 minutes or even longer, seems, like all is set back to the state before the update.

(Great job you are doing here, I always appreciate reading your site on hints and how-tos!)

If the OS X 10.8.4 update has affected your connections to Windows servers (negatively or positively)

OS X 10.8.4 problems with Word file sharing to Windows

Two more readers confirmed previous reports about problems connecting to Windows SMB file shares after applying the OS X 10.8.4 update: One reader reports problems open and saving server-based files from Word. Ali Davis can't connect to a Windows share. Davis reports:

I just saw your post and I've been trying to figure out how to fix these issues. I updated to 10.8.4 this morning and now cannot connect to my work (Windows) shared drive. If I restart it will connect for about 2 or 3 minutes then it comes up with an error saying the connection was interrupted. After that I cannot connect at all. However all the windows computers are connecting without problems. I've seen a number of posts online about this, but no workaround.

If you've seen this problem .

A reader posted a message in our forums about getting error messages when trying to save from within Word 2011 to a Windows file server ("There has been a network or file permission error"). When trying to open a file on the server from within word, an error message states that the document "might be in use," "might not be valid," or that the "file name might contain invalid characters."

If you've seen this problem or post a reply in the forums.

TIP: Office update may fix OS X 10.8.4 file sharing bug and Outlook issues

Microsoft has released an update to Office that may fix a problem readers have been reporting about saving files to a Windows server from within Word. The update, called Office for Mac 2011 14.3.6, also fixes several problems with Outlook 2011 for Mac, including sending and syncing messages.… (Read more here)

OS X 10.8.4 problem opening Word docs

Darin Sanders reports that after updating OS X to 10.8.4, Word won't open files with more than 32 characters if the file starts with a hash sign (#), which is a permitted filename character. We note that the Office 14.3.6 update fixes problems saving files, though not opening. Sanders reports:

I can no longer open some documents with Word since installing OS X 10.8.4. Error: "Word cannot open this document. The document might be in use....or the file name might contain invalid characters." The Same documents open without issue if on the Mac desktop, but do not open if on a Windows File Share.

How to produce:

This document name will generate the error: "#this_is_a_long_file_name_test.docx"

Removing the last 4 characters will work: "#this_is_a_long_file_name_.docx"

Also, oddly, replacing the "#" character with something else will allow the longer file name to open "_this_is_a_long_file_name_test.docx"

If you've seen this problem .

File locking not working on OS X Server with Windows clients

You may remember the reader report, "Mavericks ACL bug keeps Windows users locked out," where Windows users could no longer open server-based files after Macs had opened. Mark Gilbert seems to be having the opposite problem with OS X Server and Windows clients, where file locking doesn't work at…