Leopard (still) sucks at shared Windows SMB
Leopard has been pretty good to me so far, but the whole Finder automagically finding local Windows / Linux machines and mounting their SMB shares has been the one thing I’m classifying a total joke. I’m sure some Mac fans are about to pipe up and mention AFP and the like, but let’s face it, like it or not SMB is an incredibly widely deployed standard, and I expected more after Apple briefed me on how much better Finder handles this stuff.
I’ve tried a few tricks, like adding a second network location and inputting my local network’s WINS workgroup (the second location is necessary because Leopard has a bug that prevents it from saving a workgroup name in automatic mode) and other such black magic, but this jaded old network engineer just can’t seem to fix the issue. I’m not feeling too defeated and alone, though — it seems like almost no one has been able to get Leopard to auto-mount anything but AFP drives, with or without Bonjour for Windows (even sans firewall). Any Leopard users in the house with a solution or any bright ideas?
I'm an editor and technology critic in the midst of founding a new web startup: 
Dunno if you could modify this for SMB. Also dunno if this still works on Leopard (I’ve yet to upgrade). It works a treat for NFS and Tiger.
I am not alone. I hope you find an answer. That’s my one complaint about Leopard too.
No solution I’m afraid, but I’ve had no problems with auto-mounting SMB shares – although these shares are shared using a Linksys NSLU2 rather than a Windows box.
Does it ever! I was all excited to no longer have to do the ol’ Command + K when I booted up Leopard for the first time. I have three Windows machines on my network with shares, and a grand total of zero of them showed up.
I’m confused. Is it not possible to drag and drop a network share into your startup items anymore?
Maybe this is what you mean.
http://www.macosxhints.com/article.php?story=20071028194033157
d’oh first comment and forgot to post link:
http://mactechnotes.blogspot.com/2005/08/mac-os-x-as-nfs-client_31.html
Still not tried it for SMB though.
Leopard finds the windows shares on my system, although it didn’t for the first week after I upgraded, the last change I made was the WINS workgroup but that did not seem to fix it until a couple of days later the windows shares just showed up, sometimes the shares disappear for a minute then reappear but it mostly works as expected now.
Go:
System Prefs > Sharing > File Sharing > Options… > (optionally) untick AFP, tick SMB.
This is what it took to get it working for me. Then just set up the SMB accounts properly and you’re good to go.
I fully agree. I love Leopard but I can’t help but despise how it works in a mixed AFP / SMB environment. Tiger worked better then Leopard did for me when it comes to this aspect of the OS.
THEY REALLY NEED TO FIX THIS PROBLEM!
Had the very same problem since “upgrade.” But now it sort of comes and goes. Sometimes the finder automatically mounts the windows computer, sometimes it doesn’t. One thing I’ve tried is turning airport off, then on again. Sometimes that gets the windows drives to show up.
SMB is definitely broken in Leopard – 10.5.1 – and there is no fix yet when connecting into a Windows environment. I have moved back to Tiger for now and have to wait until this issue is fixed. Wether Apple likes it or not, Leopard has serious flaws in it ever since it was released, not even mentioning the Finder bug and the Sleep mode bug. It is unfortunate that these good folks take a long time to fix and as such show that the kernel and Samba need some work.
I have an early 2006 Intel iMac I am using as a test system and my production system (iMac 24″) runs Tiger for the time being (have the upgrade Leopard but had to switch back).
I’m glad I found this post, cause gosh I felt alone. I liked that Tiger had a browse-able way of drilling down the windows workgroups … now with Leopard, all I have is this quick “shared” grouping, and sometimes all the computers are there, and sometimes only two.
This flaw has made it far under my finger nails.
I’ve maintained several osx stations that access smb shares on both samba and windows servers since panther (10.3).
All I can say is, there were problems all the time.
Tiger seemed to finally fix it with 10.4.9 or so, and now they break it again in Leopard.
It’s laughable.
It’s DRIVING ME INSANE!
I upgraded to Leopard a few days after I moved and hadn’t turned on my network storage devices. A few days later I did and nothing worked. I’ve replaced the hard drive thinking it was the problem but realized it is a leopard issue after testing the drives with 2 windows machines.
I’ve tried every trick I can find on the web. Adding a location and naming my workgroup actually had the computer listed for a minute then it went away! UGH!
But even if I do have it up I can’t drag and drop files they fail to write. This is insane. I really only upgraded to Leopard for spaces and time machine I think I could live without, but I’m just hoping Apple will fix this.
http://news.softpedia.com/news/Next-Leopard-Patch-to-Pack-Almost-100-Fixes-77118.shtml
This might be of use….. An update 10.5.2 fixing nearly 100 leopard problems, including SMB sharing.
I can’t tell you how fucking angry I was to find out that I couldn’t access my NAS using SMB. I’ve had to use FTP with in Finder to drag and drop files to the Mac, then CyberDuck to upload them back when I’m done; and this on both an iMac and MacBook :@
This link might help:
http://discussions.apple.com/thread.jspa?messageID=5731231�
Andrew, not sure that really helps the problem at hand.
Same problem here. My Iomega Home Network Drive needed a firmware upgrade to let it even mount under Leopard – but at least that works. Unfortunately, I can browse directories, but not copy files to it, like other people who commented here.. So I need ftp to transfer files. Additionally, I cannot use iTunes anymore.. I have my entire music library on the NAS, iTunes does actually see the files, but I cannot play them. If I browse to a specific folder and “get info” on one specific mp3, iTunes suddenly see it (and its cover) and is able to play the entire album – until I reboot. This issue is reported on the Apple forums as well (http://discussions.apple.com/thread.jspa?messageID=6485359), but no answer..
I’m anxiously awaiting 10.5.2!
[...] authenticate using Active Directory, although I did not re-map my home drive to the network (Leopard’s SMB/CIFS support is reported to be problematic and I felt that can of worms could stay closed for a little longer until I was comfortable that AD [...]
Hi Experts. I recently purchased a NAS to implement file sharing at home, which is aimed to served files to both my MBP and my PC laptops. After configuring the NAS, all my Windows based PCs can connect to the NAS (by entering and remembering my username:password) succcessfully with full R/W privileges, but the MBP (upgraded from Tiger to Leopard)only has read only access. I can connect to the NAS successfully with SMB on my MBP, see the drive and folders, but as soon as I try to copy content onto the folders, the OS jumps at me with “you do not have sufficient privileges to conduct this operation” (or something similar). I suspected it is a workgroup issue, but I can’t seem to be able to save the workgroup name under network settings (and if it is a workgroup setting issue, how was I able to SMB connect to the NAS anyways). I’m stuck and need advice!!!
i have leopard 10.5.2. now and my SMB/CIFS is missing from the Services tab. How do I add this back in?? My Tiger had this.
Without this I can still mount but it crashes into a black screen and it ask me to reboot by pushing the power button.
Any help would greatly be appreciated
Hi all,
glad I found this post. We are having all kinds of Windows network problems since I upgraded our one Mac machine to Leopard.
Anyone know if Apple is aware of this, and if there is intent on solving this? We are planning on buying a couple more Mac machines, and with Leopard as standard equipment, doing the downgrade to Tiger will be a pain.
I have an issue with OSX Leopard (10.5.2) , where by I can’t write to NTFS shares on W2K3 servers with SMB signing turned on and IPV6 disabled for the interface.
To recreate the issue:
Create a folder named test that contains two files one named ._test.txt and test.txt on OSX and copy to an SMB share on W2k3.
This results in spurious errors about permissions and locked files.
Copying a file larger than 4k results in the error:
“The operation cannot be completed because you do not have sufficient privileges or some of the items.”
Using mount_smbfs from a shell on OSX results in the error: “Permission denied”
host:~ user$ mount_smbfs //user@server/share /Volumes/test-smbmount/
Password:
host:~ user$ cp test.docx /Volumes/test-smbmount/
cp: /Volumes/test-smbmount/test.docx: Permission denied
Using smbclient from a shell on OSX results in SUCCESS!!!
host:~ user$ smbclient \\\\server\\\share -U user
Password:
Domain=DOMAIN OS=Windows Server 2003 3790 Service Pack 2 Server=http://Windows Server 2003 5.2
smb: \> put test.docx
putting file test.docx as \test.docx (784.7 kb/s) (average 784.7 kb/s)
smb: \>
There is an alternative solution if you do need to drag and drop in your gui world, it’ll cost you $120
link: http://www.thursby.com/products/dave-eval.html
I have mailed the developer as he has obviously identified the root problem of the issue and I urged him to share his patch/resolution with Apple in the interests of the user community and a darn nice thing to do.I had a response form the developer to my request. I sent my workaround solution to the developer and stated that in my opinion the pricing for the software seems unnecessarily high based on the functionality it provides and way above what I would be willing to pay to resolve one small issue.
Pricing is a difficult topic to discuss — but if you have no use for the product, any price is too much. As for reporting bugs to Apple, they’ll listen to customers much sooner than they’ll listen to developers. And they have some of the brightest engineers I know. If you report the bug to them, they’ll likely have it fixed in the next update.
I couldn’t find away to report the bug myself so I had a friend do it for me. The response I had back from Apple was less than satisfactory.
They believe that the issue is to do with NTFS streams and that a file containing “.com.apple.smb.streams.on” needs to be created and placed into the root of shared volumes. This is not a fix!
If you want to prevent writing the “Apple Double” files to a remote share, enter the following into a terminal:
$ defaults write com.apple.desktopservices DSDontWriteNetworkStores true
Problem still exists.
ref: http://docs.info.apple.com/article.html?artnum=301711
ref: fhttp://docs.info.apple.com/article.html?artnum=106510
Before Mac OS X, the Mac OS used ‘forked’ files, which have two components: a data fork and a resource fork. The Mac OS Standard (HFS) and Mac OS Extended (HFS Plus) disk formats support forked files. When you move these types of files to other disk formats, the resource fork can be lost.
With Mac OS X, there is a mechanism called “Apple Double” that allows the system to work with disk formats that do not have a forked file feature, such as remote NFS, SMB, WebDAV directories, or local UFS volumes. Apple Double does this by converting the file into two separate files. The first new file keeps the original name and contains the data fork of the original file. The second new file has the name of the original file prefixed by a “._ ” and contains the resource fork of the original file. If you see both files, the ._ file can be safely ignored. Sometimes when deleting a file, the ._ component will not be deleted. If this occurs you can safely delete the ._ file.
I am not the only one this issue. A quick peruse on http://macwindows.com/ will show that numerous people are suffering and numerous workarounds have been suggested. Sadly none of which work for me. Each work around is stranger than the previous. Such as disabling IPV6 and updating Daylight Savings Time.
The issue lies with the samba integration. I am primarily a Gentoo Linux user and this kind of bug would have been resolved almost instantly if present in open source software.
OSX Leopard (10.5.2) cannot write to remote windows SMB shares if SMB signing is enabled.
Ok so more and more in depth googling has shown that tons of people are experiencing the same issue. The ‘fixes’ and workarounds that people have suggested, tried and in some cases had some success with baffle.
* turn off IPv6
* enable SMB file sharing and assign READ/WRITE for EVERYONE
* re-install Leopard
* delete all credentials in the Key Chain
* add and remove the machine from the domain
* delete and re-create network service profiles
* delete and re-create shared folders on the server
* change computer name, NetBIOS name, DNS entries
* the list goes on and on…
The only way I can find that will allow OSX Leopard 10.5.2 clients to mount, read and write to remote SMB shares on W2K3 servers is…..
Turn off SMB signing. Apple have borked their implementation.
From: http://www.apple.com/macosx/features/300.html
Windows SMB Packet Signing
Enjoy improved compatibility and security with Windows-based servers.
To disable SMB signing:
Open Default Domain Controller Security Settings.
Go to Security Settings, Local Policies, security Options.
Disable the following:
Domain member: Digitaly encrypt or sign secure Channel Data (Always)
Microsoft network server: Digitally sign communications (Always)
Microsoft network server: Digitally sign communications (If client agrees)
To refresh the policy:
from a command prompt run gpupdate
now OSX Leopard 10.5.2 clients can mount, read and write to remote SMB shares on W2K3 servers.
** Good luck convincing your domain admins to downgrade their enterpise security for OSX users. **
Thanks for the information nmonkee. I ran across this problem today and it’s frustrating. At least I have a fix if I’m desperate.
This is a critical bug that Apple should take very seriously.
this F’n sucks… I have to reboot both my xp and os x machines to get file sharing to work. The ONLY thing I’m doing is copyfing video files from the XP to OSX. When I attempt this, it seems to start only to pause and hang and eventually states. “cannot be found” or share is disconnected on the os x side. On the winxp side if I \\osxmachine\share.. the cursor starts sticking every few seconds and it won’t let me copy/paste.
I only have success when I reboot both machines.
I have no idea why this is not working properly in LOS.
We consistently have a problem with our Windows shares disappearing at random. It’s so frustrating. It’s has got to the point where we transfer files via a 600mb memory stick. Thanks Apple!
It seems no one has found a fix.
I have had zero issues transferring large files or connecting to servers so long as I use smb:// under go menu, though cifs:// is a different story.
We do however experience issue with shared computers appearing & disappearing for no apparent reason.
It should also be noted that using the fully qualified domain name helps dramatically with connecting to servers. Just using takes a few seconds to connect & is less reliable, but .. is instantaneous & more reliable.
We actually have our Macs integrated with AD passing authentication first through AD & then through an OD XServe for policies. It’s freakin sweet when it works.
In general I think Apple has ignored the Windows issues because they didn’t really care about mixed environments, but I assure they have changed their focus with Leopard. They’re getting some pretty big pressure from some big name companies to get it right, which is far more motivating than joe enduser.
By the way Tiger uses smb version 2 & Leopard uses version 3. I’m pretty sure many of these issues come from the new features they have tried to implement from 3.
Just like #24 above, except that this happens for any file over 0k. What worked for us was: mount the volume as a Windows Folder Mount instead of as a Windows Share (if you can). This is on Macs bound to our domain, logged in as network users, non-administrators. This does not happen with local administrators.
ie: when we mounted a Windows Share as smb://fileserver/macfolder on a Windows 2003 server, we would get the multiple errors complaining that we don’t have access, and a zero k file with the proper name on the server.
If we go to smb://fileserver/shared/macfolder, it mounts properly and we can successfully copy files and folders to the mounted folder, and even move and rename folders already there (although we did not have a problem with this in the past).
i have done the fix posted in 25:
To disable SMB signing:
Open Default Domain Controller Security Settings.
Go to Security Settings, Local Policies, security Options.
Disable the following:
Domain member: Digitaly encrypt or sign secure Channel Data (Always)
Microsoft network server: Digitally sign communications (Always)
Microsoft network server: Digitally sign communications (If client agrees)
To refresh the policy:
from a command prompt run gpupdate
but it does not seem to fix my problem.
it still tells me that i do not have significant privileges. anyone have any other ideas?
#30 Can you please explain the difference between those two types of mounting. I don’t understand the “shared/macfolder” bit. Why do you need to mount the local drive?
I have tried every trick in google-land, smb signing turned off, etc…
What I dont get is why bind to AD if cant log in as a domain user and access shares. They are basically saying to create the equivalent of mapped drives using username and password (We could do this before binding to ad so what’s the sense) I have worked through so many issues to get to this point (the .local bug, smb signing, turning off bonjour…ect) I can log into my mac as a server 2k3 AD user, i can see the servers i can click on the servers and see the share, I click on the share and get “the operation cannot be completed because the original item for “share” cannot be found” Un-friggin believable.
I’ve had this problem, could only write very small files to the shared volume, and comment 25 worked for me — many thanks — we’re a small company and our network is not accessible from outside so the sysadmin had no problem making the change, The weird thing it hasn’t fixed is that while the volume on the desktop has the ordinary icon (of a drive with 3 little men) the same volume in the doc takes on the icon of a photoshop match colour saved file… and nothing will make it stop. It doesn’t matter, but I’m easily annoyed…
Adding to the general discontent with Leopard’s inability to properly handle SMB filesystems. At this point I’m 99% convinced this is a bug in the smbfs kernel module, and maybe even the smbfs_vnops.c file .. but that is a longshot.
Here is my situation.
1. V-Gear Landisk is my remote filesystem
2. NT LM 0.12 is the negotiated SMB protocol
2. Remote (smb) filesystem is FAT32
3. Mac OS X 10.5.2
4. Anonymous password with no password on SMB filesystem
Ok what works:
1. From Leopard .. “smbclient //landisk/netbackup” can browse move modify .. etc all files
2. Can mount from Panther with no problems whatsoever. I currently backup to this drive via an rsync script I wrote on my laptop.
Now here is what happens on Leopard which I really just can’t figure out and its driving me nuts. Below is the script .. but in summary, I can mount the drive but can not browse its contents and it has something to do with ( I believe ) the way the kernel rewrites the permissions of the mount point. OK by example:
/$ sudo -s
Password:
root:/$ ls -ld /mnt
drwxr-xr-x 2 root admin 68 May 10 23:14 /mnt/
root:/$ mount
/dev/disk0s2 on / (hfs, local, journaled)
devfs on /dev (devfs, local)
fdesc on /dev (fdesc, union)
map -hosts on /net (autofs, automounted)
map auto_home on /home (autofs, automounted)
/dev/disk0s3 on /Volumes/BOOTCAMP (msdos, asynchronous, local, noowners)
/dev/disk1s1s2 on /Volumes/Nemo UWF SE (hfs, local, nodev, nosuid, read-only, noowners)
root:/$ ls -ld /mnt
drwxr-xr-x 2 root admin 68 May 10 23:14 /mnt/
root:/$ mount -t smbfs //landisk/netbackup /mnt
root:/$ ls -ld /mnt
ls: /mnt: No such file or directory
root:/$ cd /mnt
cd: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
root:mnt$ stat .
stat: .: stat: No such file or directory
root:mnt$ ls
ls: .: No such file or directory
root:mnt$ ls *
blackfire:
.DS_Store* My Music/ My Videos/ Shared Pictures/
My Documents/ My Pictures/ Shared Music/ ancestor_docs/
krakamac:
.DS_Store* Applications/ etc/
._Users* Users/ private/
krakamac.old:
.DS_Store* Users/
starless:
.DS_Store* albums/ famtree/ mysql/
root:mnt$ cd /
root:/$ mount
/dev/disk0s2 on / (hfs, local, journaled)
devfs on /dev (devfs, local)
fdesc on /dev (fdesc, union)
map -hosts on /net (autofs, automounted)
map auto_home on /home (autofs, automounted)
/dev/disk0s3 on /Volumes/BOOTCAMP (msdos, asynchronous, local, noowners)
/dev/disk1s1s2 on /Volumes/Nemo UWF SE (hfs, local, nodev, nosuid, read-only, noowners)
//landisk/netbackup on /mnt (smbfs)
root:/$ umount /mnt
root:/$
.. I’m at a loss.
Well, i also have the same problem. I can’t acces my samba share on a BSD computer. It works with 10.4 , but not on 10.5.2
i hope someone will find the solution soon :/
Thanks!
Was told today by a developer friend of mine with access to 10.5.3, that “all of my smbfs woes” would be solved with the next patch.
Let’s hope he’s right.
Kraka40, they said that the last time. Not sure if I believe it…
Well nothing is guaranteed, but my friend has a copy of 10.5.3 .. though I DON’T and I’m not sure if he had the same problem I have.
.. fingers crossed ..
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.
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!
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?
same here .. 10.5.3. has not solved any problems. this blows chunks.
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.
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)
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
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
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.
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
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.
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
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).
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.
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.
PS. it works over VPN as well.
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.
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.
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.