Comments on: Leopard (still) sucks at shared Windows SMB

By: Brett

Brett — Sat, 18 Sep 2010 23:52:14 +0000

Still here with Mac OS X 10.6 “The operation can’t be completed because the original item for “movies” can’t be found.”

By: Jason

Jason — Thu, 13 May 2010 19:41:11 +0000

expensive option but it this seems to be the only solution:
http://www.grouplogic.com/products/extremeZ-IP/

Needs to be installed server-side. Tricks finder into thinking SMB is AFP.

By: Erino

Erino — Mon, 28 Sep 2009 18:30:30 +0000

I think I’ve found the solution: In my Samba server I changed the Global Setting “unix extensions” to “No”. This seems to disable the mapping between unix permissions and samba permissions that were set to your share. Although both systems (Mac and Linux) are Unix-like it seems that the mapping doesn’t work very well… After disabling this feature my clients started to write in the Samba share without any problems. The only problem I still have is the shares in my Linux box convert the capitol letters in filenames to small caps; If I copy a file from Mac’s desktop which was in capitol letters dragging it to the window which was exhibiting the share im my Linux box, Mac OS X 10.5.6 (snow leopard) keeps showing the filename with the capitol letters inside this window… This ends up denying me to delete the file because the filenames now are different – the one shown in the window presents the filename with capitol letters while the filename recorded on the Linux filesystem is in small caps. I hope someone can find the solution.

By: Dale

Dale — Wed, 16 Sep 2009 17:14:10 +0000

This problem has returned to my network. Fileserver is Ubuntu Jaunty running Samba file sharing services. Work stations include 2 desktops running WinXP, 1 laptop running Mac Leopard 10.5.8 and 1 dual boot laptop running Leopard 10.5.8 and WinXP. All the Windows machines (including laptop) can read and write with no issue. Mac laptops running Leopard can read and write to XP’s, read but not write to file server. The error message is “Operation cannot be completed because you do not have sufficient write privileges”. I’ve tried every suggested solution in this post with no success.

I have to agree with Allen’s post of Mar. 29, 09: “I believe that the final upshot of all this is that if you want to network a mac especially leopard, you can only network it with other macs, and any claim by Apple to the contrary is false advertising.”

I’m a serious user of computers. Mac, Windoz, Linux, I don’t care. They’re just tools, like a screwdriver or a lawnmower. An end to a means. But I truly believe Macs do not play well with others. I’ll keep searching for a solution and if I get luck enough to find on, I’ll check back here. Thanks to all who have posted.

By: Peter

Peter — Wed, 05 Aug 2009 03:48:12 +0000

PS. it works over VPN as well.

By: Peter

Peter — Wed, 05 Aug 2009 03:40:50 +0000

I don’t have a problem mounting or automounting SMB share by writing a simple mount volume script with script editor.
1) open script editor (spotlight works well for this if you type script it will appear).
2) type: mount volume “smb://username:password@192.xxx.xxx.xxx/Shared” (you must use the ip address).
3) save the script as an app (in the save dialogue) and there it will mount SMB shares as needed. simple double click or add to the users startup items.
For laptop I just make a link in the doc so the users can click when them come in.

By: Alan

Alan — Tue, 24 Mar 2009 10:30:54 +0000

The above reading has just fueled my frustration, although my problem is slightly different, and from what I can gather from what I have read, it is insurmountable.
My situation:
An office with 4 x OSX 10.4 , 4 x OSX 10.5 and 1 x WinXP Pro.
Office was using one of the OSX 10.5 machines as a server(via an external HDD) with TimeMachine as backup. This failed and the OSX 10.5 machine died and needed a re-install and data could not be recovered from TimeMachine (Mac support tech said TimeMachine cannot be used to recover data, only to back it up!)
So I stepped up and built a server using Linux Ubuntu 8.04 LTS Server and Samba (latest 3.2.3). Ubuntu on a small HDD ext3, DATA (Samba share) on a second HDD ext3. I had read that this would work as Mac has Samba client built in.
I have the Samba Share setup with No Authentication. It is a publishing office so the primary program used is Adobe InDesign version CS.
WinXP has absolutley no problems with this setup.
Tiger 10.4 has no problems with this setup
Leopard 10.5.6 initial had no problems but within days the problems started showing.
If a 10.5 machine has had a indd file open and saves the changes, the file randomly appears as an alias and cannot be opened by either 10.4 or 10.5. WinXP will open it however and saving under a different filename will cause everyone to be able to access it again. This has never happened when a file is opened by a 10.4 machine.
I have since discovered that If I simply browse to the file on the XP machine and delete the “._” copy of the file, the file instantly becomes openable again.
Next problem to appear is that files that have been accessed by 10.5, randomly create copys of themselves when trying to open them, and the only fix is to open from within InDesign and choose ‘open original’.
And now when 10.5 machines move a file from one folder to another, the links to most of the images are broken and need to be relinked.(yes this happens to files that I haven’t deleted the “._” file).
The worst thing is that this behavior is completely random and never happens when files are accessed by 10.4, but once the problem appears it prevents 10.4 machines from working on them until I fix them with WinXP.
I have posted on many forums and no answers are forthcoming.
This has been happening for nearly a month now and it is considered a deal breaker for the office of designers who are only interested in it working not being broken.

I believe that the final upshot of all this is that if you want to network a mac especially leopard, you can only network it with other macs, and any claim by Apple to the contrary is false advertising.
The damage to my reputation and standing as the sole IT person in the office is also irreparable especially as it seems that I will have to go with my tail between my legs and make one of the mac work stations the server again.
Thanks Apple.

By: Dave

Dave — Thu, 22 Jan 2009 12:07:00 +0000

If your SMB share is under an Active Directory and you have an Active Directory user, AND the AD administrator lowers the log in security policy to Windows2000 or lower, you can actually access anything on the Active Directory resources.
It looks like Finder SMB log-in library is still on some pre-2000 year standard, which makes workgroup-based SMB access impossible and, the funniest part of this all, it makes LINUX-based SMB shares access impossible (they work under terminal with smbclient command).

By: Tom Green

Tom Green — Wed, 31 Dec 2008 19:30:52 +0000

Try changing the IRPStackSize in the Windows Registry.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows
To resolve this behavior, increase the IRPStackSize value in the registry:

1. Click Start, and then click Run.
2. Type regedit, and then click OK.
3. Navigate to the following key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
4. In the right pane, double-click the IRPStackSize value.

NOTE: If the IRPStackSize value does not already exist, use the following procedure to create it:
1. In the Parameters folder of the registry, right-click the right pane.
2. Point to New, and then click DWord Value.
3. Type IRPStackSize.

IMPORTANT: Type “IRPStackSize” exactly as it is displayed because the value name is case-sensitive.
5. Change the Base to decimal.
6. In the Value Data box, type a value that is larger than the value that is listed.

If you created the IRPStackSize value using the procedure described in step 4, the default value is 15. It is recommended that you increase the value by 3. Therefore, if the previous value was 11, type 14, and then click OK.
7. Close the Registry Editor.
8. Restart the computer.

If the problem persists after you complete the preceding procedure, try to increase the value of IRPStackSize even more. The maximum value for Windows 2000 is 50 (0×32 hex).

If you are running Windows NT 4.0, and the problem persists after you complete the preceding procedure, you may have to apply Windows NT Service Pack 4 or Service Pack 5.

************************************

In Windows NT 4.0, the default value of IRPStackSize is 0×4, and the range is from 0×4 to 0xC (4-12). Windows NT 4.0 with Service Pack 5 or later ignores values less than 0×7.

In Windows 2000, the default value of IRPStackSize is 15, and the range is from 11 to 50. In Windows XP, the default value for IRPStackSize is 15, and the range is from 11 to 50.

NOTE: The default and range of Microsoft Windows Server 2003 is the same as that for Windows XP. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
106167 (http://support.microsoft.com/kb/106167/ ) Error message: Not enough server storage is available
NOTE: The preceding article recommends that you increase the IrpStackSize value; however, if you increase this value to its maximum (for example, if you increase this value to the maximum value of 12 on a computer that is running Windows NT 4.0, or to the maximum of 50 on a computer running Windows 2000), this behavior may still occur.

For more information, click the following article number about IRPStackSize to view the article about IRPStackSize in the Microsoft Knowledge Base:
198386 (http://support.microsoft.com/kb/198386/ ) Changes in IRP stack size in Lanman Server

By: Andy Kim

Andy Kim — Fri, 12 Dec 2008 08:31:13 +0000

Aside from all the real issues above, I simply don’t want to use SMB, I don’t need it at this time. Leopard is lacking in flexibility for the user to easily turn off unneeded features. If I need to go to the terminal to disable unnecessary junk taking up CPU time, I may as well convert to LINUX.

Is there anyway to temporarily “unload” SMB, or turn off whatever processes are constantly calling for port 139 scans of local PC’s?

Thanks.

By: Gareth Howell

Gareth Howell — Fri, 03 Oct 2008 17:44:02 +0000

I have also been getting this problem wen trying to access a shared folder on a Windows XP SP2 machine from a Leopard 10.5.4 Mac mini.

In my case, the problem lay with just this one XP machine, others were OK.

On accessing the same share from another XP machine I got a different error.

See http://blog.garethhowell.com/dx/03102008181845GHONBB.htm for how I solved it.

Gareth

By: Lefty

Lefty — Fri, 12 Sep 2008 05:41:50 +0000

I have a mega grudge against MAC with smb shares to UNIX and Windows environments.

1. DS_Store files are trash. Don’t allow these by default. Keep your rubbish on the MAC machines and don’t spread the garbage to other platforms. An add on is available to stop this but that is lame.

2. I was forced to change drive structure to NFS on both UNIX and Windows to even allow MACs to share with UNIX and Windows.

3. On doing the above copying to the drives on the other operating systems worked but editing of the files from a MAC fails. Doesn’t happen with UNIX and Windows.

4. I had to turn off SELINUX because MAC sucks. The same goes with disabling digital signing on Windows servers.

5. To all you MAC nobs, I reported this issue 8 months ago and it was made a joke of by MAC users. Go stick it up yours as MACS are UNIX based systems that are incompatible with other environments. Therefore if you thing working in a Luna Park enviroinment is cool because you are a designer and schools force you to use MACs grow up weener. The only powerful feature is on a laptop for local database driven demos to clients otherwise you probably have a small brain.

FIX the crap MAC.

By: Ben S-W

Ben S-W — Sun, 31 Aug 2008 17:19:19 +0000

I have recently upgraded to Leopard Server 10.5 and all but my WinXP machines (and connections via SMB) do not read the permissions correctly and and they can’t modify files. i.e all WinXP users see are read only files.

Given this issue has been around for months I am surprised at the Apple’s apparent silence on the issue.
Perhaps they got the Server Development Department to work on the iPhone 3G (back to work please lads!!) :)

I use the server for basic cross-platform file-sharing across 100+ users.
If anyone has any thoughts on how to serve files via AFP and SMB like the old days I would be happy to hear about it.

Think I will buy Windows next time!

Ben

By: Vivi

Vivi — Wed, 11 Jun 2008 22:16:21 +0000

I just ran over the site and havn’t read all comments. But I think I had the same problem. Adding :

unix extensions = off

in the [global] section off the smb.conf works for me.

Important: I do not know if this setting has any negative side effects

By: Alex

Alex — Wed, 11 Jun 2008 21:59:01 +0000

Hi!

I’ve finally found a solution for the problem, at least for me.
Part 1:
This is to get able to change the workgroup, found on http://discussions.apple.com/thread.jspa?messageID=6198136 :

“Open /Library/Preferences/SystemConfiguration and trash these files:

* com.apple.airport.preferences.plist
* com.apple.network.identification.plist
* com.apple.smb.server.plist
* NetworkInterfaces.plist
* preferences.plist”

Of course, you have to make sure that your firewall allows smb and that windows sharing is enabled.

Now you should be able to enter your Workgroup – of course, you also have to enter all other network data :-(

Part 2:
Found on http://digg.com/apple/OSX_Leopard_Another_Serious_BUG_Unable_to_Browse_SMB_Windows_Shares
Disable ipv6:
“This is NOT a bug. Apple chose to add IPv6 to Leopard, most SMB shares (in my work case win 03 server) are not using IPv6, so lets turn it off and play nice with Windows. Go to “System Preferences > Network > Ethernet (could be wireless if you connect that way) > Advanced button > TCP/IP tab > Configure IPv6 drop-down > set it to off” Now you should flush your DNS, open a terminal and type “dscacheutil -flushcache” Browse Away.”

If you feel like me and really dislike Apple’s userfriendly, undocumented “You-don’t-need-to-know”-attitude and prefer Win or Linux, you probably also want to give the BSOD-icons that Leopard uses for PCs a kick and change them: http://www.engadget.com/2007/10/30/mini-how-to-remove-the-windows-bsod-icon-in-leopard-make-os-x-a-little-less-smug/
But this is of course completly optional:-)

And funny fact: A Network-printer which was accessible in Panther only as ip-printer is now accessible only as bonjour-printer.

I hope this helps at least some of you.

Good luck,
Alex

(whose MacBook crashes or freezes every one or two weeks, while Windows 2000 and XP keep on running)

By: Daniel

Daniel — Sat, 07 Jun 2008 18:13:01 +0000

I’m surfing the net for what feels like hours now, just to make my Mac be seen by the Windows Laptop. It just doesn’t work, and after what I’ve read there’s no solution in sight.

At least the Finder discovers the Windows laptop when I manually set the workgroup in Airport’s WINS tab and turn off the firewall. Hooray. Firewall’s back on.

What is this supposed to be? Zero config? lmao. You know what? This reminds me of two things I almost thought were past: endless Google’ing for allowing simple things to happen (Linux) and just no solutions in sight (Windows).

I really don’t see any difference between Mac OS X and Windows in terms of reliability and ease of use anymore. The “it just works” feeling is long gone. Sad but true.

By: kraka40

kraka40 — Sat, 31 May 2008 22:47:07 +0000

same here .. 10.5.3. has not solved any problems. this blows chunks.

By: dmair

dmair — Thu, 29 May 2008 16:42:48 +0000

I installed 10.5.3 and it still doesn’t work. Interestingly my work XP Pro, Win 2003 Server machines all automagically appear in finder. My Win 2000, and XP Home boxes do not show up. What is the difference?

By: Jacques

Jacques — Thu, 29 May 2008 06:48:20 +0000

I installed 10.5.3 and just arrived in the office. I still do not see the shared drives. However, if I connect manually I can copy files larger than 5 kb. It’s fast and no problems so far.

I also tried to open a document from the server and save it right back after a small change. No problems either. Said that, I still prefer to copy the file to my disk first ;-)

Cross fingers that this is a stable fix!

By: dion

dion — Wed, 28 May 2008 15:47:54 +0000

Even when I can add the windows XP shares to my leopard machine, I cant drag them into my Favorties.

No matter what I have to drill down through the IP to get to them. Really annoying.

Tiger lets you Mount an XP share as a drive with no issue. I cant do the same thing in Leopard.

APPLE PLEASE FIX THIS! OR SOMEONE EMBARRASS ME BY CORRECTING ME.