SMB or AFP?

Hi,
I have just installed a LaCie NAS on my network and all is working well. I note that I can establish the connection to the share uysing either SMB or AFP and just wondered if there is any practical difference between the two?
David

As for your other question, I am curious. Would
connecting your LaCie disk drive directly to a Mac to
format it as HFS+ and then returning it to your
network hub pose a problem?
Not sure if that is or is not possible - I have at the back of my mind from the manual that even if you connect via the USB cable it still uses its own BIOS and doesn't show up in disk utility - may be wrong, but having now got over 30GB of files on I don't think I'll experiment! I don't see me wanting too many 2GB plus files stored which, of course, is the main FAT limitation.
David

Similar Messages

SMB or AFP? Connecting to an XRaid/XSan from a Mac

What's the preferred protocol when connecting from a Mac to a network volume on either a single XRaid or an Xsan volume? Any advantages to AFP? Any known issues? Any reasons to use SMB?

Thanks for input but must disagree, I have several successful installations with 3rd party network-based RAIDs, with dedicated GigE line to each machine. Works great, multiple DV25 streams to 3-4 concurrent Macs. No dropped frames
Struggling with a current setup involving one XRaid and 3 GigE clients. Have seen suggestions that there is differences between SMB and AFP but nothing specific...

10.5.2 totally broke SMB and AFP shares (and kerberos) on my network

Hey Folks,
I'm really kicking myself for not testing 10.5.2 first... this is a disaster for me.
After installing, I can no longer access any SMB or AFP shares (regardless of host OS) using my kerberos ticket (granted from Tiger Server).
If I use the GO menu and Connect To Server it also fails, almost instantly. The server logs suggest its not even trying.
I have totally lost access to all of my shares, ssh with kerberos is broken...
Anyone else seeing problems?
Leopard in general introduced some issues with the local KDC on each machine trusting mdns...its a way to make back to my mac work ... and it broke SMB for me and a lot of people, but it wasn't the end of the world since I was sharing everything via AFP as well. Now that AFP is broken too I'm at a loss...100% down.

Something I have been messing with is my mit.edu.Kerberos file, located in System/Library/Preferences.
Take a Tiger machine, and use Text Editor to look at it's mit.edu.Kerberos file. Then, do the same with the Leopard machine. I've been trying to get Leopard to work with the Tiger kerberos settings, without luck so far. But it's a step in the right direction. Try this for starters:
On my system, when I try to use Connect to Server with the Finder, it gives me the vague "Volume Couldn't Mount" error.
Make a backup of mit.edu.Kerberos on your Leopard machine (use a test machine if possible, not a production machine). Then, delete the original file and reboot.
Try to COnnect TO server again. On my machine, I'm given a login prompt, which if I re-authenticate, I'm able to connect to the share. Your previously deleted mit.edu.Kerberos file has been recreated after this point. I'm not sure how permanent of a solution it is, however.
But it's something to tinker with if you're so inclined.

Saving to SMB or AFP Server

When using the save function on some documents (not all) from pages to a network server (either SMB or AFP) I get the error: "The document (document name) could not be saved." I can hit "save as" and save it in the same directory with no issue. This "save as"'d document then cannot be saved, but can be "save as"'d yet again. Thus I end up with version 1, 2, 3, 4, 5, ad infinitum... Alternatively, I can bounce back & forth: 'version 1', then 'version 2', then 'version 1' again, then 'version 2' again.
This behavior only happens when going to the network server, saving locally always works fine. I've also found that I only get the error on certain documents, a document from the template "personal photo letter" works fine, but a document from "Modern photographer Letter" exhibits this behavior. With the good templates it always works, and with the bad templates it always doesn't work. I have tried using both the default save type and the "save new documents as packages" option with no apparent difference.
This behavior also exhibits itself across multiple mac clients on our network (all running iWork '09/Pages 4.0.2 (751), and Leopard 10.5.7). The behavior was also there for iWork '09/Pages 4.0.1 (746) and previous releases although I don't know all the previous iterations. The behavior was also there for Leopard 10.5.6 and previous releases although I don't know all the previous iterations.
When the error displays in pages, I get the following 2 messages on the console.app/all messages screen:
7/23/09 3:36:05 PM Pages[8521] NSDocument called FSPathReplaceObject() and -47 was returned.
7/23/09 3:36:05 PM /Applications/iWork '09/Pages.app/Contents/MacOS/Pages[8521] Had to sleep for 200 milliseconds to clear transactions race for -110/(.TemporaryItems/folders.501/TemporaryItems/(A Document Being Saved By Pages),(null))
Anyone out there have a clue?

Hi,
I wish I could offer a solution, but I have the same problem: both Pages and Keynote 09 will not save changes to a file that has been opened from a network server.
More details: the problem only occurs with iWork 09 files. If I open a Pages 06 file in Pages 09 and make an edit, I can save the file as part of the conversion of the file to the Pages 09 format. However, the file is not savable from then on. So, the conversion process creates a saveable file, but subsequent "saves" are not possible.

Weird issues with file share using both SMB and AFP?

I use my Xserve with 10.4 server primarily as a file server (with a huge RAID array attached via Ultra320 SCSI). I've served files from this server over SMB ("Windows" sharing) to both PCs and Macs for a few years now with no big issues. The files are being shared in a collaborative environment with extensive user accounts and ACLs set up.
I would like to turn on AFP for these same file shares, so those accessing with a Mac can have the added benefits of AFP over SMB. However, I've heard some rumors of some complicated issues developing from the use of both AFP and SMB together on the same folders, in a mixed environment.
The rumors I've heard are things that would happen rarely but enough for it to be significant. For example, a file created over SMB and then edited over AFP would have some problems being re-edited over SMB again, due to some complicated feature that the rumor is unable to explain (something with a resource fork or file locking?). Maybe something weird that just involves the Adobe Creative Suite?
Anyway, I figured I'd throw this out there. Anyone who serves files over both protocols to a varied set of computers and applications having weird issues? Or is everything working for you? Thanks in advance.
Message was edited by: dtemp

Thanks for the responses!
re:crop
It's coming in as cropped with no way to fix it that I can see.
Pressing space or opening in preview shows the full image but if it gets anywhere near Photoshop it comes in auto-cropped.
I'm starting to this it's a bug and will be reporting it to Adobe.

Can smb and afp coexist on the same host?

Greetings all!
I've been using Macs and OSX for a year. And recently I bought another MBP so I am seriously considering Time Machine backups. I have a Linux home server running Ubuntu 12.04 and Samba and my previous MBP running Mountain Lion connects to it happily without any problem. But my trouble started when I tried to setup afp on the same box.
I followed this post and this post and got the fake time capsule showing in Time Machine without any problem. But soon I found myself unable to connect to the old samba shares. The smb host now displays as a Time Capsule. If I click on that OSX will say 'failed to connect'.
As I understand there are 2 pieces involved on the server side, avahi to broadcast the service info and netatalk to provide the service itself. It's a bit like nmbd and smbd in Samba. If this is true then it's somewhat understandable that OSX can not display the same host as 2 different types of services at the same time. So I stopped avahi-daemon and very soon the old Samba shares appeared again.
I am able to connect to both services using command+k but I would rather have them running normally so that my wife will be able to use them without extra tech support. Can anyone tell me if what I said above is true and/or if there is a graceful way around this? If answer is no then I will have to create a virtual machine or nic alias just for time machine and I think it's quite a waste.
Thanks!

tristonej wrote:
I don't quite understand why people buying non-Apple devices should not expect OSX to work with them
Because Apple has no control over 3rd parties. They can do what they want. If Apple publishes a new authentication mechanism in 2002, the 3rd party doesn't have to implement it. That isn't Apple's fault. If they do get around to supporting it in 2009 and then some 4th party doesn't bother to use the 2009 code in 2011, Apple still can't do anything about that. If anyone else wants to advertise, and support, Time Machine compatibility, they are welcome to do that. They definitely have the advertising part down, the support, not so much.
There is a time when apple only worked with apple but that aparently was not sustainable. And that's why now Apple is embracing smb
Apple's goal is to choose the best solution for its customers. Sometimes that is a proprietary connection or protocol and sometimes it is something industry standard. In all cases, there has to be some cut off for testing and support. That is why Apple eventually stops supporting its own hardware and technologies at a certain point. That is also why Apple will support SMB as deployed by Microsoft but isn't going to waste much time on home-built Linux servers.
(it's said even samba was used shortly on OSX, not quite sure) and allow users to install windows on macs. Even OSX itselt is based on FreeBSD and uses quite a lot of open source components.
Apple uses a lot of open source software. Samba was one of those projects. Unfortunately, the people that made those products didn't want Apple using them so they changed the licensing to prohibit Apple (and pretty much only Apple) from using their source code. That is why some of the open source packages in OS X are stuck in a 2007 version. That is also why Apple abandonned Samba and wrote its own SMB implementation.
OS X is not based on FreeBSD. It has a BSD-flavoured POSIX layer, but it is a distinct operating system at its core.
IMHO there is no magic in throwing money at propiretary hardware/software or praying to Steve Jobs. If something is not working, it must be that there is a bug in the code or the design. And neither OSX nor Macs are built by God, which means they are bugged as other software/hardware.
I'm confused. When did anyone say anything about praying to Steve Jobs or divine technology? You asked about using Linux as a Time Machine server. I suggested you avoid that if you value your data. I also asked why you would want to keep running Linux now that you have a Mac. A Mac can do anything Linux can do with a fraction of the effort.
The answer is simple, Macs can not do what I want.
Which is?
Withe a standard mATX case I can have quite a few 3.5" drive bays while there is only one 2.5" in a Mac mini. And with Ubuntu/Debian, getting/updating the software or the system is quite easy, just one or a few lines of apt commands, not quite possible with OSX.
That's certainly true. OS X updates itself without having to run any apt commands.
If you must compile something from the source to get a Linux running then something must be seriously wrong.
My thoughts exactly. But perhaps you didn't follow me entirely. Apt, yum, etc don't have everything one needs to setup something as fancy as, I don't know, a web server. While I did have to compile a number of things from source, I had to actually edit the source a couple of times as well.
The best thing I love about Linux is openess. You can customize almost everything and change it whatever way you want. With Mac, for example the 2013 Retina MBP I just bought, it's not even possible to change the power button behavior, which is very annoying.
Then why did you buy a Mac? That's no big secret. Some people like not have to configure everything just to get it running. I have other things to do than edit config files.
Back to my original question. I think the problem is not quite with compatibility of Bonjor but rather whether OSX can show this or not. Imagine you have a smb share and afp share on the same host, with the same name, how would OSX display it? And which icon will OSX use to display the host? I can not think of the answer so if you know please tell me.
OS X will just display it like it display any server. One of your links event has instructions on how to pick the icon you want to fake. If you are running both services then I am not sure which one it would try to connect with. Neither of your services are native, not matter how much they try to fake it. If you wanted a specific service you would have to manually use the correct protocol in Finder > Go > Connect to Server. However, bot of those links were posted before Mavericks. Obviously they don't work anymore. It's Linux. It's open. Right? So fix it and post it on your own blog. I do not know what modifications you would have to make to either Samba or Netatalk to make them work with Mavericks.
If all you need is to allow your wife to connect to one specific protocol, then manually connect to that service, saving your password in the keychain, and create an alias by Command-option dragging the server to some other folder. Then, she can just double-click on the alias to connect to the network.
Now, if you really want to be clever, you can setup an automount to that service instead. Then the server will be mounted and unmounted as needed.

Unable to authenticate from 10.5 client to 10.5 Server to mount SMB or AFP

We have been banging our heads for some time now and have no idea what is going on. Here's the scenario:
We have a 10.5.6 Server bound to an Active Directory Domain
The Server's role is: Connected to a Directory System
We have ensured that Active Directory/All Domains has been added in the Authentication Pane of Directory Services
We have made sure that single-sign on has been enabled by running dsconfigad -enablesso
We have verified that SMB and AD are using the same password
The shares are actually being re-shared from mounts added through XSan.
This has worked in 10.4.
Now, when a client tries to mount the smb share using domain credentials they get an error that they are unable to authenticate.
If an attempt is made to authenticate from a command line the error reads:
server rejected the connection: Authentication error
The smb logs fill with error -14090 [eDSAuthFailed] on each authentication type attempt meaning it tries kerberos and fails, NTLMv2 and fails, NTLMv1 and fails.
We really need to figure this one out. Anyone have any more ideas?

It does, in fact, fail the SHA-1 test, but how could that be? What could cause the download to be corrupt over and over and over? I've downloaded it both wirelessly and by wired connection, on both the MacBook itself and on a PowerMac G5.
MacOSXUpd10.5.6.dmg SHA comes back as e35035609abb3a0ac231d4d4cd8954a8d07d950e
accepted SHA is 684f67524a92b4314a4bdd52498fb3b6af8f9ded
MacOSXUpdCombo10.5.6 SHA comes back as 045e51a74376521931e563c64fa79ed5c1529d79
accepted SHA is 09de4ac2c5591ab75d51ef37dc70f9e5630150d4
i doubt that info really helps anything, though
Redownloading both AGAIN... we'll see what happens.
Message was edited by: chiefanalogist

Can't open Excel or Word files on share drive (SMB or AFP) after 10.9.2

After updating to Mavericks OS 10.9.2, I can no longer open excel or word files on my company file share. I receive the error:
'FILEPATH' could not be found.
Ckeck the spelling of the file name, and verify that the file location is correct.
If you are trying to open the file from your list of most frequently used files on the File menu, make sure that the file has not been renamed, moved, or deleted.
I am able to open files on my lcaol hard drive, and other external USB Flash drives. Word present's a slightly different error, with the same theme (filename).
I've tried rebooting both the client and server (both running 10.9.2). Was successful opening files when booting the client into safe mode. Any ideas?
Bill

I don't know if this will help but I had a similar problem that started yesterday. I have two macs. Once can't open MS Office files from the other Mac but can open Office files on each Mac. Drove me nuts for about 2 hours today - on the phone with Apple twice and Microsoft once. Finally found a similar post from 2007 that suggested to turn off and on file sharing by unchecking the "Share files and folders using AFP", on both computers and rebooting. That fixed it.
Funny thing, it was only with Office files I created since updating the software last week. Old Office files opened fine.

Blocking access to file sharing (AFP/SMB) from outside of network

Hello all,
Is there a way to block access to file shares from outside of our LAN? I have a machine that has some sharing turned on (it is also my email server) and I can reach it across the internet and mount shares as if I was in the office.
How can I block this access? Both SMB and AFP?
Thank you,
-John

Justin, thank you for your reply. The machine is on a public ip address and is not behind a NAT router. I've turned on the software firewall and that is working now. However, I imagine it would be better to use a hardware firewall. Any suggestions on a good one? Thank you.

Forcing afp over smb for default file mount

Looks like Leopard is defaulting to using smb, to mount network shares -- even IF the machine is a Mac! Here is my setup:
- iMac 2.8Ghz as "client" (Leopard)
- Mac Mini C2D as "server" (Tiger)
- Both connected to the same Netgear GigE switch, both showing GigE as connection speed.
On my client, I see the shares on the server and mount them by entering my password. Copying files, via smb, isn't that fast (~20MB/sec). Once I use Apple-K to force an afp mount, the file transfer is ~50MB/sec.
Is there any method to force Leopard's Finder to default afp for a Mac to Mac connection? Seems very weird that the default is smb when the machine is 100% Apple/OSX.

Alrite, have a little more testing done with this setup. As R-C-R has kindly pointed out, I should break it down one at a time. Here is what I did:
- Mount the share, via the Leopard sidebar
- Mount the share, via Command-K
Mounting via the sidebar shows this via bash:
imac:/ vash$ 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/Untitled (ntfs, local, read-only, noowners)
afp_393tmw0008OL0000oM0000VU-1.2e000007 on /Volumes/vash (afpfs, nodev, nosuid, mounted by vash)
imac:/ vash$
YES! It is mount via afp. My immediate assumption was wrong. Let's benchmark copying 2.78gigs from the mini to the imac: max of 32MB/sec. Why that speed? I haven't a clue, but that's the current speed using the Leopard sidebar to mount.
Disconnect all of it and mount via Command-K. Here is the cli output:
imac:/ vash$ 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/Untitled (ntfs, local, read-only, noowners)
afp_393tmw0008OL0000oM0000VU-1.2e000009 on /Volumes/vash (afpfs, nodev, nosuid, mounted by vash)
imac:/ vash$
Same 2.78GB copy maxed out at 78MB/sec.
My first conclusion of smb vs. afp is dead wrong. Sidebar vs. Command-K mounting is definitely different.

Server App does not change SMB AFP option as expected

I have been fighting SMB shares on Mac OS since upgrading to Mountain Lion (I skipped Lion) and I think I have the situation figure out at least in my case.
First Opportunistic Locking needs to be turned off in Windows 7. It does not appear that Mac OS supports it and this is why my connection got disconnected.
In the regestry at, [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Paramet e rs] add this, "OpLocksDisabled"=dword:00000001
Now for the SMB shares for people using the Server App. The Server App. is where you setup shares but I think there is a bug. In my case the Server App. was not actually turning on SMB and/or AFP services for the users listed in the server permissions. I had to go to Sharing under System Preferences then select the share I want the service to apply to then select Options. I found that the SMB and AFP services were not enabled even though they had been set in the Server App. Once I enabled them all was as it should be.

Same problem. I had to rebuild my LDAP database and when I imported the users and groups, they appear in Workgroup Manager but they don't appear in Server app. Well.. they do sometimes. If I click the "Add Users" button, sometimes they'll appear briefly then go away in Server app. I can also edit a user and look at their group membership via Server app and the groups from Workgroup Manager appear but they are grayed out... also, the users from the LDAP server will disappear at first and I have to click on another button, like "Configure Network" and then click back on "Add Users" and the network users will be there... but no group.
This is crazy. It's like working on a '74 Chevy Vega. Did ANYONE at Apple QA this?

AirPort DIsk User Accounts - SMB Access sees different files than AFP

I have two hard drives attached to my Extreme via a powered USB hub. Both drives are formatted HFS. I have multiple user accounts configured for Disk Sharing over Ethernet WAN. When I use SMB or AFP to access the same user account from an external network I see different files. Based on the space available it appears as if the Extreme has setup the SMB account on one drive and the AFP account on the other. Is anyone else experiencing this, and if so, how do I consolidate the accounts and prevent this from happening?

After some testing, here is my current theory. When your drives are mounted by the Extreme, it looks to find your user account folders on the first drive to mount. If the first drive to mount does not have your user folders, the Extreme creates a new set of user account folders on that drive. Consequently, when your drive with the user account folders finally mounts, you now have multiple sets of folders. I'm not sure why AFP or SMB accesses a different set of user folders, as I could not always recreate the same access patterns, but it appears that one protocol tends to see one set of user folders and the other protocol your other set of user folders. If I always mount the drives in the same order each time, new folders are not created and both protocols see the same sets of files.
This brings up a new twist on the question. Since I will not always be around to manually remount the drives each time the Extreme re-boots, does anyone have any theories on a workaround?
Secondarily, this means that all of your user folders need to be on one drive and any other drives mounted just become shared properties for all accounts. This doesn't seem like a very efficient use of storage space if individual users don't want a majority of their files available for everyone. Has anyone figured out how to get user accounts spread out over multiple drives?

AFP and SMB sharepoint in AD environment

We are currently migrating user accounts to authenticate to AD to make life easier for our students as we use both Macs and PCs on our network. We have AD working using our XServe to host home directories using AFP. When a user logs on using a Mac they can access the AFP share without problem. What we would like to achieve is users logging on using a Mac to use AFP on the sharepoint and PC users using the same sharepoint running on SMB.
We have set our ‘users’ sharepoint up using both SMB and AFP but can’t get this working; I remember seeing a method using dsconfigad to direct PC users to SMB and Mac users to AFP a while back but can’t remember where.
Any help would be greatly appreciated if someone can point me in the right direction
Thanks in advance,
Dan

Open Console app and Click the button to show the log file list.
There are various locations and they will be listed in the list. I'm not sure how to turn on more logging. Many of the config files for various services are in /etc.

AFP not working but SMB does Xserve 10.6.8

Hello All,
I have a Xserve running 10.8.6 running file shares. This is a mixe envirment so I have both SMB and AFP enabled on the server. My issue is today I found out that AFP is not entirtly working. Using Command+K I can connect to the server using afp://server.local authenticate and see all the folders. If I select a folder from the list it works just fine. If I try to connect to a folder directly for example, afp://server.local/folder, it gives me the authentication prompt and after I type in my password it get a connection error. It states just states that there was an error connecting and I need to check the server name or IP address. This erro comes up if I use server.local or the IP address. SMB works just fine on both Mac and PC. I've checked DNS settings and the server resolves properly. The reason I need AFP is to setup my Deploy Studio.
Thanks for any help.

Looked into the issue and came to conclusion that my server was corrupted. I was forced to reformat and configure the server. The issue is now resolved.

Unreliable reading from AFP server (NAS)

Following on from some earlier problems, I've started encountering a new, and much worse, problem. After I successfully connect to the AFP share, I can look at the contents of various remote folders in Finder. But, some of the folders are just showing as empty, even though I know they aren't. I tried waiting several minutes, nothing showing up (and there doesn't seem to be any way to tell if Finder is waiting for a response or not - with other folders you may get the same result, but the files usually show up after a few seconds).
There doesn't seem to be any particular pattern to it. Certain folders show all their contents, others just appear to be empty. Also, if I try to list the contents of these folders from the command line (ls -la /Volumes/Share/Folder) then once again it works for the same ones that work in Finder, but it otherwise it just hangs. I am getting similar problems sometimes trying to unmount certain shares from the command line with diskutil: again, it just hangs.
This wasn't happening when I tried it recently (as suggested in the thread referenced at the top of this post) and the only thing to have changed about my system since then is this update:
http://support.apple.com/kb/HT6207
I'm not sure if that's likely to have anything to do with it, or if it's just because I've not been using the NAS from the Mac so much lately (mostly been working on Windows stuff the last couple of weeks). Maybe it's just coincidence that this is the first time I've noticed it.
I've tried restarting the Mac and the NAS and the same thing is happening even from that completely clean state (so no chance anything has gone into sleep mode or similar). I can access the same folders with no problems from a Windows PC over SMB. For some reason when I try to connect to the SMB share from Mavericks it completely fails to read the contents of any shared volume, so I have to use AFP (or possibly figure out what's wrong with SMB, but that could be a much harder problem to solve).
I couldn't find much about this issue by googling, although I did find a recommendation to clear the Finder cache. However, on my system, ~/Library/Caches/com.apple.finder doesn't exist. Has this been removed from Mavericks?
There's always a chance this could be a problem with the AFP implementation on the NAS, whch is an Asustor AS-202T, running the latest software (ADM 2.1.1.R3B2). Is anyone else on here using an Asustor NAS?

hi,
any luck resolving this?
I am investigating the slow large directory reading problem between macbook OS X Mavericks 10.9.5 and NAS Asustor 202TE ADM 2.2.1.R863
Basically, reading a large directory (c. 2,000 files) is very slow.
Then, deleting a file is fast the first time, then any subsequent delete, in same session, seems to cause a file list refresh, and slow again.
This is very painful to review sets of files created daily from my garden cam, where most need to be deleted.
I really don't want to boot up a windows machine for this task.
Potential solutions / areas to investigate:
1. mac tcp parameters: delayed_ack, packet size, frames etc
     found a good resource here for this, but I haven't found any combination that makes a difference for me
2. turning off icon previews etc
     done this, no change
3. directory list cache: client side vs server side
     cannot find any info relating to the Asustor or mac implementation
4. finder replacement
     not sure this has any benefit
5. smb vs afp
     I haven't noticed any performance difference, so doubt this is significant
Any help would be appreciated.

SMB or AFP?

Similar Messages

Maybe you are looking for