Parallels Desktop
Parallels Desktop 8 for Mac Run Windows apps and Mac apps side-by-side, without restarting! Now supports Windows 8 on your Mac. Integrates Mountain Lion and Windows 8 features, such as centralized notifications, and Mission Control and Launchpad for Windows apps. Also runs OS X as a guest OS.

"I found Parallels faster at every common task, like starting and restarting Windows, and resuming Windows from a suspended state."
--Walt Mossberg, New York Times

Lion and File Sharing Tips and Reports

Working with Mac OS X 10.7 and SMB and AFP File Sharing

Updated May 23, 2012
Some of these solutions are known to work for Mountain Lion. If you find this .

On This Page:

- Tips and Reports


 

Mountain Lion Server for Dummies
How to Support Mac and Windows clients on a Mac server, connect your Macs to Active Directory

Steve Jobs by Walter IsaacsonOrder Now!

Check Amazon's pricing on:

Windows 7,GoToMeeting - Online Meetings Made Easy
for your Mac, for running with Boot Camp, Parallels or VMware

Amazon's Apple products pageFollow MacWindows_com on Twitter

MacDrive 8
Access your Mac OS X partition from
Boot Camp
GoToMeeting - Online Meetings Made Easy


Follow MacWindows_com on TwitterFollow us on twitter

Windows Servers and Macs
Tips and Reports


Windows on Mac




GoToMeeting - Online Meetings Made Easy

TIPS and Reports

Lion's broken connectivity to NAS and AFP servers

Friday, August 5, 2011

It seems like any new release of Mac OS X breaks some aspect of file sharing with non-Apple devices. This was true for Leopard, and Snow Leopard had (and still has) problems with SMB file sharing. With Lion, Apple replaced the under-the-hood workings of both SMB (Samba) and the Apple Filing Protocol (AFP). Almost immediately, users discovered that Mac OS X 10.7.0 has an incompatibility with many network attached storage (NAS) devices using AFP as well as other AFP file servers. Most NAS devices support both AFP and SMB, but Mac OS X's Time Machine backup software requires AFP.

For users, the Apple-provided workaround can prove tricky to work around than it first appeared. Readers have reported by success and failure with the procedure. Lion users who try to access some AFP devices get the error message:

The version of the server you are trying to connect to is not supported. Please contact your system administrator to resolve the problem.

The problem is with the Apple Filing Protocol (AFP) and applies to NAS devices and other AFP servers... Read entire story here

TIP: Workaround for Lion older AFP servers, including NAS, Novell

Tuesday, July 26, 2011

A new Apple support article states that the Lion client comes with several AFP file sharing authentication methods turned off, preventing Lion from accessing certain AFP servers. This could include most network attached storage (NAS) devices, according to PC Magazine, and, a reader reports that NetWare servers are also one of the affected servers. Group Logic last week issued an update to its AFP server, ExtremeZ-IP, which is not affected. Lion is using Netatalk 2.2 for AFP, and is using a new authentication method called DHX2. Apple says......Read entire story here

Apple workaround for Lion AFP fails reader; problem with Windows SMB shares

Thursday, July 28, 2011

George Gunzelman reports that Apple's procedure for enabling Mac OS X 10.7 Lion to access older AFP file sharing servers didn't work. He also reports problems with access SMB Windows shares:

I read your post on macwindows.com. I too am experiencing issues with mounting shares from a Windows 2003 server. It reports the server is too old for the AFP shares. I removed all of the disabled UAMs from the AppleShareClient.plist as described in Apple's article but it did not help. I get the same error. The Windows 2003 server is fully patched and up to date with MS updates. I also have difficulty mounting SMB shares.

Although I am still testing, so far as I am concerned, this upgrade has BROKE Apple networking so badly I may need to revert to 10.6. Apple better have a fix soon or I will steer my customers away.

If you've seen this .

Readers Apple fix for Lion AFP works for Novell file servers

Friday, August 5, 2011

Two readers report success with Apple's workaround for Lion accessing AFP file servers Lion. The readers reported success with Novell servers, though the procedure is also supposed to work with NAS devices. Rick Zeman said that enabling the MS2.0 authentication did the trick:

Lion clients can't mount volumes on Netware 6.5 servers using the afptcp.nlm (or OES 2's AFP server) giving the error: "The version of the server you are trying to connect to is not supported. Please contact your administrator."

Apparently, Lion's AFP client only supports the DHX2 authentication mechanism which Novell evidently never rolled into either Netware or Open Enterprise Server. While Novell might fix the latter, I'm not holding out hope for the former.

Interesting KB article. Based on a sample of 1 Lion client and 1

Netware 6.5 server, the Mac needed to have MS2.0 activated. I backed them out 1 at a time from most complex to the most simple.

Anderson Lam also reports success with Apple's procedure:

We experienced the problem that Lion has connecting to Novell on my campus and the fix that worked for me (based on Apple's support document) is to follow the steps below. This re-enables only the older authentications methods that are needed to connect to the Novell on my site while leaving DHX2 authentication intact for the times when users want to use the more secure authentication method.

In Terminal, type:
sudo chmod o+w /Library/Preferences

Then type:
sudo defaults write /Library/Preferences/com.apple.AppleShareClient afp_host_prefs_version -int 1

Restart the computer. After restart, type the following commands in Terminal:
sudo defaults write /Library/Preferences/com.apple.AppleShareClient afp_disabled_uams -array "MS2.0" "2-Way Randnum exchange"

Then type:
sudo chmod o-w /Library/Preferences

Your readers may have to enable or disable other authentication methods depending on what they are using.

If you've tried this .

LaCie releases beta Lion-compatible NAS updates

Thursday, August 18, 2011

LaCie has released beta Lion-compatible software for three of its network attached storage devices, the d2 Network 2, 2big Network 2, and 5big Network 2. The updates enable Macs running Lion to access the devices using AFP file sharing and Time Machine. Mac OS X 10.7 isn't compatible with many NAS devices and AFP servers. Uses receive an error message when trying to connect: "The version of the server you are trying to connect to is not supported."

LaCie is recommending that customers with Macs running Lion install the beta software on the NAS device. LaCie recommends against installing the beta software for customers who are not running Lion.

Another take on Apple Lion AFP problems

Tuesday, August 30, 2011

Chris Norris sent an article about his attempts to get around Lion's problem accessing AFP servers. Norris has a Netgear network attached storage (NAS) device. The first part of his report is similar to Apple's workaround, which we've previously reported. This didn't work for him, so he goes on to describe what he tried. Here's Norris' report:

Control of some protocol elements are in the /Library/Preferences/com.apple.AppleShareClient.plist, which doesn't seem to be created in a default installation of OS X 10.7 Lion. I tried copying the file from a Snow Leopard system at first, but then the configuration is different than what you would create in this process. So I deleted the file, then rebooted, and started from scratch......Read entire story here

QNAP announces Lion-compatible NAS firmware

Tuesday, August 9, 2011

QNAP announced yesterday that it would update the firmware for its Turbo NAS series of network attached storage devices (NAS). This includes full support of Time Machine backup and file access by Lion clients. Because of changes to AFP, Lion is not compatible with many NAS devices on the market, and may AFP servers as well. (See "Lion's broken connectivity to NAS and AFP servers.")

Version 3.5 of QNAP firmware will also include security improvements, virus scanning software, and the ability to join an LDAP domain (such as Open Directory and Active Directory) and allowing LDAP domain users to access the NAS. QNAP expects to ship the update later this month.

Netgear has updates to NAS devices for Lion compatibility

Tuesday, September 6, 2011

John Lockwood responded to the last week's post "Another take on Apple Lion AFP problems," which provided an approach to working around Lion problems with network attached storage devices:

While the tips I am sure do indeed do what they claim, in Chris' own particular circumstance of using a Netgear ReadyNAS they are unnecessary. Their are two main branches of ReadyNAS models, the older ones powered by a Sparc CPU, and the newer ones powered by various Intel CPUs. *Both* branches already have beta firmware available which fully resolves Lion compatibility issues for both basic AFP access and for Time Machine compatibility. Details can be found at Netgear's blog.

As always, Netgear are providing firmware updates free of charge.

It should be noted that Netgear are the leading sponsor of the open source Netatalk project and generally are more up to date with newer Netatalk releases than some other NAS makers.

More NAS vendors add Lion support

Tuesday, September 13, 2011

Four more manufacturers of network attached storage (NAS) devices continue to release upgrades that enable Lion users to access them over AFP. The is the latest round of updates responding to Apple's changes to the Apple File Protocol in Lion, which left many NAS devices incompatible with Lion, and in particular, Time Machine backups, which require AFP. The companies are LaCie, Synology, QNAP, and Thecus.

LaCie shipped final versions of its Lion-compatible NAS firmware, NAS OS 2.0, which it first released as beta software. Also new is a new user interface and automated RAID modes......Read entire story here

iXsystems FreeNAS Version 8.0.1 is Lion, Time Machine ready

Tuesday, October 4, 2011

iXsystems updated firmware for its FreeNAS network attached storage devices, which are based on the Open Source FreeBSD. FreeNAS Version 8.0.1 updates AFP file sharing protocol so it is compatible with Time Machine under Lion. FreeNAS 8.0.1 also includes new front end user features in its web front end, as well as backend changes and bug fixes.

With Lion, Apple changed the AFP protocol, rendering NAS devices and other some AFP servers incompatible. Since Mac OS X 10.7 was released last summer, several NAS vendors have updated their software to be compatible.

FreeNAS is a free and open source network attached storage server operating system based on FreeBSD. It uses a Django-based web user interface and includes full ZFS file system implementation. iXsystems is the company that builds FreeBSD-certified server hardware and enterprise storage solutions, and which oversees the development of FreeNAS software.

Lion cannot connect to AFP Share on Windows 2003 Server

Friday, October 7, 2011

Bob Arene found another AFP server that is not compatible with Lion: an older Windows 2003 Server running Services for Macintosh. Arene said:

Mac OS X 10.7.1 can't connect via AFP to the shares on our Windows 2003 Server. I removed all authentication methods from the disabled list per the Apple procedure but still no luck. I can connect to the Windows shares only via SMB.

Some other readers previously report that the Apple procedure didn't work, but it did work for some readers with Novell's server.

If you've tried Apple's remedy with an older Windows Services for Mac file server .

Lion 10.7.4 does not connect to old AFP shares

Wednesday, May 23, 2012

Jeffrey Mehlhorn reports that the recently released Lion 10.7.4 update still has the problem with connecting to older AFP Windows servers (with Services for Macintosh):

I too have just got a new Lion machine running 10.7.4. It will not connect to Windows Server via AFP, although, all the pre-Lion machines have no problem connecting via AFP. I tried Apple's suggestion over and over and it does not work. Even talked to Apple support and they didn't have faith in the solution either. They just said upgrade the PC server. Arrrgh!

Note that we also have another suggestion here. If you've seen this problem


Lion issue with SMB Windows share in column view; an AD issue

Thursday, July 28, 2011

Noe Gonzalez is happy with Lion accessing Windows shares, but found that shares don't appear Finder windows in column view in some circumstances, and reports one Active Directory issue:

Just some feedback per your article "Apple ships Lion with new Windows-compatibility features."

So far in my organization Lion has been working well. The only bug we noticed, and made me mad for a couple days was that when accessing some Windows shares (SMB) where the main folder is protected, but a user has access to a subfolder. In column view it appears that the sub-folder isn't available, it just shows the main folder with a restricted sign on it. However, change your view to icon or list view and you can see everything in the sub-folder and make any changed you want.

I hope that made sense. Only other problems I've run into is with Active Directory search policies not always working. But usually a reboot, or 'killall opendirectoryd' takes care of it.

If you've seen these issues

Reader confirms Lion problem with SMB folders in column view

Monday, August 29, 2011

Jorgen Ivarssons confirmed the previous report "Lion issue with SMB Windows share in column view."

I can confirm that SMB folders show up when you switch from column view to list view in Lion 10.7.1.

If you've seen this problem .

Reader says Lion Mail crashes with column view attachment

Monday, April 23, 2012

Brett Rutherford verified "Lion issue with SMB Windows share in column view":

Confirmed, 10.7.3. Was crashing mail.app when trying to attach a file from a network share in column view. IMHO most ridiculous bug EVER.

If you've seen this problem

Lion SMB file sharing can't get past top-level of Windows share

Friday, August 5, 2011

Will Wade can't get inside Windows SMB shares using Mac OS X 10.7. It sounds similar to a previous report, Lion issue with SMB Windows share in column view:

There seems to be several bugs here in Lion. Regarding George Gunzelman's report, I'm finding it's partly right but not entirely. For me, I can mount and see all my Windows shares but I can't get past a top level folder using the Finder (either using list, icon or column view).

However using the Terminal and cd'ing then open does work. Then, in the Finder, stay in icon or list view.

If you've seen this problem .

TIP: Workaround to Lion bug in mounting DFS shares

Tuesday, August 9, 2011

Matt Whiting responded to Friday's report "Lion SMB file sharing can't get past top-level of Windows share" with a workaround. He believes the problem is not related to another SMB problem was first reported, but is instead a bug in Lion's ability to mount DFS. Whiting report and workaround:

Just to follow up Will Wade's comments, I believe what he and I have experienced is a completely separate issue to the 'change Finder view' one; this is all about mounting DFS shares - a new feature introduced in Lion - and should probably be blogged as such.

On the Mac we never used to be able to access, for example, \\company_domain\files\fileshare1 (as it's addressed on Windows, or smb://company_domain/files/fileshare1 on the Mac). Under the hood, this points to a specific file server that might be separate to another which serves up fileshare2. Unless you used third-party software (e.g. Thursby) you'd have to work out the name of that server and mount it directly (e.g. smb://server_name/fileshare1) which apart from being technically difficult also gives you problems if, as is possible under DFS, the file share moves onto another server. (I think of DFS as DNS for file shares, where the address is abstracted from the actual server doing the work.)

Anyway, the good news is that 10.7 does support this, albeit with a bug. To expand on Will's work-around: 1. Mount the file share from Finder (e.g. smb://company_domain/files/fileshare1). You'll probably get a window with nothing in it. 2. In a Terminal window, type 'open /Volumes/files/fileshare1' (but obviously replace the bit after Volumes/ with the rest of the path from step 1. If you get 'no such file or directory, you can figure out the whole path by starting off with 'open /Volumes/', then repeatedly hitting tab twice and typing the first letter of each bit of the path, until you get to the end.

Hope that makes sense, and it can help out some other users.

If you've seen this issue or tried this approach

Fix for Lion DFS problem didn't work for reader

Friday, October 7, 2011

A reader going by "LD D" tried the suggestion described in "TIP: Workaround to Lion bug in mounting DFS shares," but it didn't work:

When I tried the suggestion to open /Volumes/MyDFSMount/MyDFSVolume but I get an error: Authentication Error. That is all it says. But, when I view this from a Windows 7 box it works with out issue. So I do not think it could be a true authentication error. My Mac is configured to be in AD using Open Directory. Also, I checked the console.app for messages and this is what appears: 10/5/11 10:08:18.365 AM NetAuthSysAgent: smb_mount: mount failed to mydomain.com/dfs, syserr = Authentication error.

If you've seen this problem, or have an idea about it .


Lion problems connecting to network scanners and printers

Lion problem with SMB network scanning

Thursday, August 11, 2011

Duane Armstrong can't use Lion to scan to network SMB scanners:

Ricoh copiers send scanned documents using SMB, which uses the port 139 (netbios-ssn), and this port will NOT open on the Lion Mac. These are ports that open on Mac OS X version 10.6.5. Settings:

File sharing :ON
Options: Share files and folders using SMB (Windows)
Ports 139 and 445 =open

If you have this problem .

Reader confirms Lion issue accessing Ricoh network scanner

Monday, August 29, 2011

Mark Miller confirmed a problem reported in "Lion problem with SMB network scanning":

I have the same problem. Since upgrading to OS Lion, my Ricoh printer will not fax or scan to folder.

If you've seen this issue .

Another reader can't get SMB scanning with Lion to work

Thursday, September 22, 2011

David Geric reports:

I also have problem with SMB scanning with Mac Lion. Has anyone found a solution?

We haven't found a fix. Have you?

Reader has problem with Lion Server and network scanner

Thursday, August 11, 2011

Jaap Schokkenbroek reports a problem with a with a network scanner after upgrading from Snow Leopard Server to Lion Server:

I've got a simple HP Officejet Pro 7780 which could scan to a network volume 'scans' on the server. After the update to Lion Server the HP isn't able to log-in anymore, very anoying. I made a new user on the server, I made a new sharepoint etc etc but no go. Other Mac's (10.6 though) can log-in with the smb://ip-adres routine...

If you've seen this problem .

Another report of Lion problems with network printer/scanner, now with HP4215

Friday, November 4, 2011

Brian Bielanski is having the previously reported problems with Lion accessing printers and scanners over a network, which connected to a Windows XP PC. However, he also can't get Windows 7 to see the device. He reports:

I'm having the same problem with my networked HP 4215 and my new MacBook Pro with Lion. The 4215 works when I hard wire the 4215 to the Mac, but doesn't work when it's networked via Wi-Fi to a Windows XP computer. I also can't get a Windows 7 computer to Wi-Fi network to the 4215 through the MPB.

If you've seen this problem

Lion can't connect to networked HP 4215 printer/scanner

Friday, January 6, 2012

Rob is another read with problems using Lion to access a HP 4215 printer/scanner over a network. His problem is a bit different than the previously reported problem with this unit:

Trying to add the printer over Bonjour (LION OS) and says software not available _ contact the manufacturer. The HP site doesn't give out the drivers there; It says it's all through Apple Software Update.

If you've seen this problem

Lion problem with Kyocera scanner via SMB

Monday, November 21, 2011

Njuguna Waitara confirmed a previous problem report with Lion and SMB scanners. He writes:

I am responding to the post "Lion problem with SMB network scanning" about Port 139 being closed." The only difference is that my Multi Function Printer is a Kyocera.

If you've seen this problem

Using FTP instead of SMB to scan with Ricoh Multifunction Printer/Scanner

Friday, January 6, 2012

Eric Novikoff commented on Lion problems with Ricoh network scanners:

I saw your postings and can report success with switching to FTP. However I do have security concerns and am pressing Apple for a solution that will allow inbound SMB connections to start working again.

If you've seen this

AppleCare tells reader "don't mix Macs and Windows" for Lion and SMB scanners

Tuesday, January 10, 2012

Eric Novikoff followed up his previous report about Mac OS X 10.7 Lion problems accessing network printer/scanners (in his case, a Ricoh multifunction):

This entire episode is a disaster, since the scanner failure can be duplicated simply by trying to connect to a Mac from Windows via SMB. Nearly 9 months after Lion came out I would have expected this solved, but neither AppleCare nor the web seems to offer a solution. But the scariest part was the Level 2 AppleCare people telling me I shouldn't mix Windows machines (in this case a Ricoh multifunction machine that also has SMB running on it but not Windows) with Macs. I felt as though I was talking to someone on LSD. If that's really Apple's position, despite years of trying to build legitimacy as a highly interoperable OS, I'll be going back to Windows forthwith, because I can't live without my peripherals...

If you've seen this problem

Ricoh on Lion incompatibility with network scanner

Thursday, January 19, 2012

Ricoh is aware of the problem that MacWindows readers have been reporting about Lion not being to scan to network printer/scanners. A reader thinks Apple is also aware of it.

A Ricoh support article recommends using scan-to-FTP:

Information for "Scan-to-SMB" and "Fax Folder Transmission (SMB only) & Fax Forwarding (SMB only)" support

Due to architectural changes in Mac OS X 10.7, both "Scan-to-SMB (Scan to Folder via SMB command)" and "Fax Folder Transmission (SMB only) & Fax Forwarding (SMB only)" can't be used.

We expect a resolution to this problem in November so please continue to revisit the website for updates.

As a temporary solution please use Scan-to-FTP (Scan to Folder via FTP command).When using Scan-to-FTP, please activate FTP on Mac OS X 10.7 and follow the settings announced on this website: http://support.apple.com/kb/HT4704?viewlocale=en_US

Readers have previously reported that scan-to-FTP works.

Michael Speranza believes that Apple is aware of the problem:

Yes, we are having the exact problem described. After upgrading to Lion, can no longer scan to folder from our Ricoh printer. My local Ricoh/Lanier supplier claims that Apple is developing a solution for this.

Readers have also reported the same problem with the HP 4215 printer/scanner. If you've seen this problem

Another net scanner Lion doesn't like: Konica BizHub

Tuesday, January 24, 2012

Eric Carr adds another scanner to the list of network scanners that Lion doesn't work with:

I have run into this same issue with a Konica BizHub C351. I upgraded a server to Lion over this past weekend and lost the ability for it to scan to an SMB share. I had to download an FTP server and set it up on the server to get the Scan to FTP option in the BizHub working.

If you have a network scanner or multifunction printer/scanner that Lion doesn't like

Reader says Kyocera knows about Lion's SMB scanning bug

Tuesday, January 31, 2012

George Walker in Ontario, Canada, reports that Kyocera told him that Lion's problem with SMB network scanning is Apple's bug and must be fixed by Apple. Readers have previously reported the problem with Kyocera Ricoh, and HP multifunction printer/scanners. Walker wrote:

After upgrading to Lion, we can no longer scan (SMB only) to a Drop Box folder from our Kyocera 455oci printer. The machines using Snow Leopard (10.6.8) work fine. We can see the Dropbox of the Lion machine when we navigate through the printer's interface but it errors when trying to send the file. Kyocera is not working to fix the problem as they claim that it is Apple who have damaged the SMB.

Does anyone have a Terminal fix that can change the SMB port settings back to how they were in Snow Leopard?

File sharing: ON
Options: Share files and folders using SMB (Windows)
Ports 139 and 445 =open

It should be noted that with Lion, Apple comply change the SMB software in Mac OS X, ditching the open source SAMBA with new code of its own. If you've had any success with Lion and network scanning


TIP: Lion SMB problem fixed with streams=no in nsmb.conf

Thursday, August 18, 2011

Darren Purvis had an SMB file writing problem with Lion and large files. With Snow Leopard, he successfully used the tip of setting net.inet.tcp.delayed_ack=1. This didn't work when he upgraded to Lion, but another Snow Leopard trick, editing the nsmb.conf file to turn off streams, did work:

I've had problems in the past with my Mac (Snow Leopard) writing to samba/CIFS shares -- reading has been fine. When the shares were on a Unix server, the fix was to set "net.inet.tcp.delayed_ack=1" (1 worked best for me). Then two things happened: 1.) I changed my home NAS to Windows Home Server 2011, and 2.) I upgraded to Lion. The result was that I could not write large files (> 200MB) without the file copy hanging and putting the network connection in a "zombie", non-functioning state. Multiple writes at once were an immediate network connection killer. The delayed_ack fix didn't help, so I assumed it was something to do with the underlying NTFS on WHS2011 and the way that SMB was interacting with it. Further assuming it was related to .DS_store files, I then created (it didn't exist) the /etc/nsmb.conf file, with the contents:

[default]streams=no

After a reboot, file writes are "normal" again - I get sustained 45MB-75MB transfer rates, I can write large files > 1GB, and I do them concurrently now too. Hopefully sharing this with others will help.

If you've tried this .

Lion SMB Error -51 fixed with streams=no in nsmb.conf

Monday, August 29, 2011

Andi Kunar confirmed the tip "Lion SMB problem fixed with streams=no in nsmb.conf."

This works great for me as well. Thanks! I have a MacBook Pro (2011) OS X 10.7.1 (clean install) connecting to Windows Server 2003 (Windows Home Server 03 with all SPs/fixes installed). I got a lot of Error -51 (e.g. when starting a 2nd Finder copy-job while 1st one was still running). After streams=no fix, I don't get the Error -51 any more.


Reader reports problem printing in a Window corporate environment

Monday, August 22, 2011

Eric reports a problem with SMB printing in a Windows network after upgrading Macs to Lion:

A user who upgraded to Mac OS X Lion could no longer print to the Samba hosted printers in our corporate network. Printing in our corporate windows environment always worked via SAMBA printing. Typically, one configured the printer using the CUPS interface by entering smb://domain/username:password@ipaddress_of_the_printer/queue. With Lion, that seems to be broken. Printers now report each time: "Access Denied".

Checking the Samba logs showed that OS X Lion was sending "workstation" as the NetBIOS name instead of the configured NetBIOS name.

This is apparently a bug in the SPOOLSS, Lion's replacement of SAMBA by Apple. Because allowing that user rights from workstation "workstation" the printers worked just fine. However, this fix demands all Mac users to be allowed rights to workstation "workstation" when they upgrade to Lion. Not acceptable.

If you've seen this problem .


TIP: How to have Windows access Lion with FTP instead of SMB

Friday, November 4, 2011

David Scott has given up trying to fix Lion's SMB file sharing with problems with Windows trying to access Lion. Instead, he uses FTP. Problem is, FTP is turned off and "invisible" in Lion. But, you can turn it on using Unix commands in Terminal. Here is Scott's report:

SMB seems to work from Windows XP to a folder on the Mac. But it seems some files refuse to be opened or copied -- like Word documents and Publisher files, for example. Even renaming the file doesn't help. Our workaround is to use FTP. Connecting to the Mac through FTP allows me to copy the files. One drawback, though, is I cannot map a drive letter to an FTP location in Windows XP.

At first it seems FTP is no longer available, but it is. See the following Apple article, Lion Server: Enabling the FTP service, and this CNET article, Managing FTP Services in OS X Lion. I do not yet know whether the commands stay current when the computer is rebooted.

We also have trouble with SMB scanning since 'upgrading' to OS X Lion.

If you've tried using FTP instead of SMB


Reader problem with WINS and Macs

Friday, December 23, 2011

Dominic Breen has a problem with his Macs and WINS restristation on a Windows network:

We configured WINS Server role on our Windows 2008R2 server (non-Active Directory). Also DHCP. We see Mac DHCP leases on DHCP Server, but do not see WINS registrations for Macs, even though WINS entry is in leases. Windows clients register OK. On the Mac clients, in System Preferences>Network>Advanced>WINS, the address of WINS server is there.

Are we heading for browser wars or some other issue? Any thoughts on how we can see registrations?

If you've seen this problem


Unable to disable SMB file sharing in OS X

Friday, December 23, 2011

Topher Kessler of CNET describes how to fix a problem where SMB file sharing can't be disabled. He describes how to use Directory Utility to fix it:

In addition to offering file sharing using the Mac-native Apple Filing Protocol (AFP), Apple also includes an option for the Server Message Block (SMB) protocol so you can share files with Windows machines.

Unlike the AFP option that is enabled for the whole system, the SMB service is enabled or disabled for individual users in the Sharing preferences pane. Unfortunately, in some instances after upgrading from OS X 10.6 to OS X 10.7 Lion, some people who have had the SMB service enabled are finding they cannot disable it for their accounts. When they enter their passwords at the prompt, instead of turning off SMB the system claims the incorrect password was given, and keeps SMB enabled......Read entire story at CNET

If you've seen this problem


AD-bound Lion clients not connecting to 10.6.8 server over AFP

Tuesday, December 27, 2011

Mark Lewis reports that Mac Lion clients bound to Active Directory can't connect to Snow Leopard Server via AFP. He also found a workaround:

We have had several reports from offices that their AD bound 10.7.2 clients fail to connect via AFP to bound Snow Leopard servers. Clients would receive the following error: "The version of the server you are trying to connect to is not supported. Please contact your system administrator to resolve the problem." The resolution we found is to use the FQDN of the server. We are currently working with Apple to determine why the short name no longer works. I posted full details on our KB site:

(This does not appear to be the same problem regarding Lion clients and AFP authentication.)

If you've seen this problem


Windows-to-Mac File Permissions Propagating Problems

Tuesday, December 27, 2011

A reader in our forum has a problem with Windows clients and Mac OS X Server on an Active Directory network. Here is a portion of the post:

...if a user copies a file to this new OS X server the permissions only show for that user so other users can't amend and sometimes can't access the files. I read using SMB only on the Macs might solve but hasn't. I read that Lion Server would be the answer so tried that but it's a nightmare to get connected to Active Directory but it was doing the same. I setup in the Server to Propagate the Permissions but as soon as any Windows user adds a file to the OS X Server the permissions revert to that user.

If you've seen this problem or have a suggestion, please post a reply in our forum.


Lion 10.7.3 disconnects from Windows shares

Friday, March 9, 2012

Banu Tanguler reports a file sharing problem with Lion losing connection to Windows shares:

I have a small workgroup set up at my office. The PC is Windows 7 and the MacBook Pro is running Mac OS X 10.7.3. The Mac keeps losing the connection to the shared folders on the PC and I can only restore the connection by rebooting both machines.

If you've seen this problem (More reports like this on Lion File Sharing Tips and Reports.)


Reader says Lion file sharing worse than Snow Leopard

Friday, March 9, 2012

Eelko de Groot is not having luck with file sharing in Lion:

I read your article "Apple ships Lion with new Windows-compatibility features" on where you ask our experience with Lions new SMB file sharing engine. Alright a bit late since you wrote it July 22th, 2011. Anyhow I wanna share my experience.

As up to this moment I'm not very fond of this new SMB engine. With Snow Leopard I never had problems, but since my upgrade (some months ago) I cannot connect to any of the Windows shares from my Mac. But from Windows towards the Mac I don't have any problems. I have to say that I did not investigate the problem in depth until now. I hope I will find the cause of the problem soon.

Our Lion File Sharing Tips and Reports page contains suggestions for fixing Lion problems.


TIP: SMB permissions for Lion users

Tuesday, March 13, 2012

Britt Dennis figured out how to set SMB permissions to allow Lion users permission to "traverse" a directory to get to a directory inside nested folders, but with permissions to see the upper level directory:

We have some users accessing a NetApp SMB/CIFS share with Mac clients. With OS X clients prior to version 10.7 we were able to set upper level directory security permissions to traverse and allow people to access subdirectories that they had explicit permission to. The users would connect just fine. With Lion this came to a screeching halt.

We stumbled across the Apple KB http://support.apple.com/kb/HT4829 that mentioned that in Lion permissions, on all directories leading to the subdirectory with explicit access, it needed to have read access and not just traverse permissions set. In our setup this was not desired, as we did not want users to have visibility into the contents upper level directories but rather simply pass through on their way to their final destination. We discovered that setting the advanced permissions at the folder only level to "Travers folder/ execute file", "Read Attributes", and "Read extended attributes" allowed the traversal effect that worked under Snow Leopard, Leopard, and prior to work again without providing users unnecessary visibility to files and folders in the upper levels.

Big Thanks to Chris Davis and Mark Adkins for their help on this!

If you've used this tip (Related: Lion File Sharing Tips and Reports)


Reader can't open .XLSX files in Lion

Monday, March 26, 2012

A reader in our forums reports that he can't open .XLSX Excel files in Lion:

I have encountered an issue with the shared workbook feature in Microsoft Excel 2008 on Mac OS X 10.7.2. Shared workbooks are .XLSX files stored on any network volume. Open as Read Only is not working and I encounter the following error: "Excel cannot open this file. The file might have been damaged or modified from its original format."

Issue does not occur for shared workbooks that are in the older .XLS format.

If you've seen this problem , or post a note in our forum.


-36 file copy error seen with Lion

Monday, April 23, 2012

Louie Campagna is getting Error -36 when copying a file on an SMB share with Lion. This was a widely reported Snow Leopard problem, but we haven't heard of it with Lion. Campagna reports:

I've been running into a problem with copying files on SMB shares. This could be creating a duplicate in the same directory, or even copying a file from one share to another. The file copy will always complete, and the file will be usable, but the following error is always thrown:

The Finder can't complete the operation because some data in <filename> can't be read or written. (Error code -36)

I'm currently running OS X 10.7.3, but this was happening on previous versions as well. I've tried a bunch of different things to try and alleviate the issue, but nothing works. Obviously since the file copy does work, it's more of an annoyance than a hindrance, but I'd still like to try and find a solution.

There are a number of different workarounds on our Snow Leopard File Sharing Tips page. If you've tried any of these for the problem in Lion

Lion 10.7.4 update didn't fix error -36

Wednesday, May 23, 2012

Louie Campagna updated his previous report about a file sharing error in Lion:

Just so the info is out there, 10.7.4 has not fixed the SMB issue I reported to you (error -36 when copying).

If you've seen this problem

Current news on the MacWindows home page

Run Windows apps directly in Mac OS X without Windows

CrossOver 12 runs Windows apps on a Mac--without Windows or Boot Camp
Installs Windows apps directly in Mac OS X with 1 click. Office, Outlook support, Quicken, ActiveX in Internet Explorer and more, launched directly from the Finder -- just as if they were Mac apps.
Runs games, too, including Left4Dead, Warcraft, Steam, Spore, and others on your Mac.

Starts at only $40 (and no need to buy Windows!) Free trial from CodeWeavers.
Click here for more.


Other MacWindows Departments

| Product Solutions | Reports and Tips | News Archives | Site Map |
|
MacWindows Home |

| Top of Page |

This site created and maintained by
Copyright 2011- 2012 John Rizzo. All rights reserved.