SMB vs AFP

Similar Questions

• SMB or afp for itunes?

  Hello

  I have a problem...

  I use a synology NAS to my itunes library (4 TB of data to date, videos and music). I don't know why, my library files are on two volumes "iTunes" on my desk:

  • SMB://DiskStation/iTunes,
  • AFP://DiskStation._afpovertcp._tcp.local/iTunes

  When I look at the names of files in iTunes, some are in a volume of itunes, the others are in a volume of itunes-1.

  It drives me crazy; my files are spread over 2 formats and I don't know what to do. iTunes is already hard enough.

  I would like to have own unique access, how should I proceed?

  Thank you for the compassion ;-)

  back to iTunes seem not intended to be used in a NAS configuration. People do this, but it seems to be a little chance sometimes to how it behaves.

• AFP vs SMB performance

  I've just updated to the latest version of Sierra.  I thought I had read somewhere that SMB was preferred over the AFP in Sierra and that performance would improve.  I don't see any improvement.  My results are so radically different, I thought that I post to see if anyone can tell me why my performance SMB is so catastrophic?

  I have a Mac Pro (non-cylindre) on a home network wired gigabit.  Synology DS412 + NAS running 4 disks in RAID 5.  I mounted it my my Mac using the basic option "Connect to Server" in the Finder and typing "afp://server:share" and "smb://server:share" for testing.  Both were mounted and tested separately, which means I am disconnected from the AFP before Assembly and test SMB.  I used rsync with some verbose options to copy a 1.5 GB file in order to see the speed and get a transfer of the statistics.

  Here are the stats to transfer the file to AFP:

  [josh@jeter /joshtmp]-> transfer diskimage. ISO/Volumes/FILES/tmp /.

  Building file list...

  1 file to examine

  DiskImage. ISO

  1.49 G 100% 52.18 MB/s 0:00:27 (xfer #1,-check = 0/1)

  Number of files: 1

  Number of transferred files: 1

  File size: 1.49 G bytes

  The total size of the transferred file: 1.49 G bytes

  Literal data: 1.49 G bytes

  Matched data: 0 bytes

  Size of the file list: 121

  List of files generation time: 0.002 seconds

  List of files transfer time: 0.000 seconds

  Total number of bytes sent: 1.49 G

  Total number of bytes received: 42

  received bytes sent to 1.49 G 42 bytes 52,20 M bytes/s

  total size is 1.49 G speedup is 1.00

  I think it's a pretty decent speed, but my concern is not the top speed, is the disparity.

  Here is the SMB speed:

  [josh@jeter /joshtmp]-> transfer diskimage. ISO/Volumes/FILES/tmp /.

  Building file list...

  1 file to examine

  DiskImage. ISO

  1.49 G 100% 18.02 MB/s 0:01:18 (xfer #1,-check = 0/1)

  Number of files: 1

  Number of transferred files: 1

  File size: 1.49 G bytes

  The total size of the transferred file: 1.49 G bytes

  Literal data: 1.49 G bytes

  Matched data: 0 bytes

  Size of the file list: 121

  List of files generation time: 0.001 seconds

  List of files transfer time: 0.000 seconds

  Total number of bytes sent: 1.49 G

  Total number of bytes received: 42

  received bytes sent to 1.49 G 42 bytes 18,71 M bytes/s

  total size is 1.49 G speedup is 1.00

  Also, here is the info from statshare to see how it was mounted:

  [josh@jeter /joshtmp]-> smbutil statshares - a

  ================================================================================ ==================

  THE ACTION ATTRIBUTE VALUE TYPE

  ================================================================================ ==================

  FILES

  Server_name rivera

  USER_ID 1026

  SMB_NEGOTIATE SMBV_NEG_SMB1_ENABLED

  SMB_NEGOTIATE SMBV_NEG_SMB2_ENABLED

  SMB_NEGOTIATE SMBV_NEG_SMB3_ENABLED

  SMB_VERSION SMB_3.0

  SMB_SHARE_TYPE DISK

  SIGNING_SUPPORTED TRUE

  EXTENDED_SECURITY_SUPPORTED TRUE

  LARGE_FILE_SUPPORTED TRUE

  CLIENT_REQUIRES_SIGNING TRUE

  DFS_SUPPORTED TRUE

  MULTI_CREDIT_SUPPORTED TRUE

  ENCRYPTION_SUPPORTED TRUE

  SIGNING_ON TRUE

  -------------------------------------------------------------------------------- ------------------

  In addition, attached is a screenshot of my share of the Synology settings.  It shows the parameters of the SMB and AFP.  The pop-out box is the options 'Advanced settings' of the SMB section.

  Any ideas at all?  Please and thank you.

  See Image here.

  It seems that Apple still did not set their "quick and dirty" dose for such Badlock described in this thread: El Capitan 10.11.5 update slow SMB (bug)

  If you believe that your network is protected from man-in-the-middle attacks and the bug Badlock, then you can disable the client for signature.

  1. Create a nsmb.conf file in / etc with vim. sudo will be necessary.
  2. Write to the file:

  [default]

  signing_required = no

  
  

  Then restart your machine. Your SMB3 speeds should be comparable to the AFP again.

  Here is the post above: Re: Re: Re: Re: update of El Capitan 10.11.5 slow SMB (bug)

• El Capitan 10.11.5 update slow SMB (bug)

  Since I upgraded my Macbook Pro retina 2015 to 10.11.5 SMB transfer speeds to my Synology NAS are not go faster, then 25Mbit.

  When I use AFP I get 110Mbit speeds on my nas.

  A Mac Mini which has 10.11.4 and the SMB and AFP tested speeds are good 110Mbit.

  10.11.5 mac mini updated and I get speed via SMB 25Mbit!

  Looks like a bug in the release of El Capitan 10.11.5 SMB protocol

  Same thing here - very slow speeds to my NAS Qnap (SMB) (also the mentioned 25Mbit. Before 10.11.5 I had about 100 Mbit).

  My machine Windows 10 speed is still ok = > it is not a problem of the SIN.

• File server for Windows does not work after security update

  I just upgraded the security update that was released last week and all of a sudden the computers windows cannot access the server. I'm under 10.11.6 and everything was great until we started windows computers today. They can ping and access the internet, but they cannot access SMB on the server.

  Macs have no connection problems in the SMB and AFP.

  Any ideas, what has changed? Users of server are all still there and it seems like it should work. I can access the web page of servers too.

  Make sure you are including the domain in the user name when signing in. for example USER: groupe_travail

  Also, check that your windows machine has the correct set of LM compatibility level. For El Cap servers must be set to 3.

  Follow the instructions below to change the Windows security settings to allow Windows SMB connections.

  1. Click on the Start button and in the bottom search bar, type regedit . Select search results regedit and the registry opens.
  2. Using the folders on the left side of the screen, navigate through the tree to the following location: \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
  3. In the right window, find the following DWORD value: LmCompatibilityLevel . If it exists, double-click it and set the value to 3 (in decimal).  If it does not exist, right-click in an empty space in the right part of the window and create a new DWORD value called LmCompatibilityLevel and set its value to 3 (in decimal).
  4. Restart the computer.
  5. Re-try to connect to the server via the workstation.

  NOTE: The versions Home of windows may not the ability to set the LM, and unfortunately I have not found a way around that.

• copy or duplicate in sharing files cannot point

  IM currently on 5.0.15 Server with OSX 10.11.3 3 computers (clients) on OSX 10.11.5 and have found that they can not copy or duplicate in sharing files to point to the server. When you attempt to reproduce or copy a file you get the following message "unable to connect to the server because the name or password is incorrect." However copy on another share point is fine. Just won't work in this share point. Moving the file is fine. Any other Client computers are on OSX 10.11.4 or lower do not experience this problem. Should I update it with OS and App Server and hope that this question will far more recent?  Thank you

  I just checked using the latest version of the Server 5.1.5 and client OS X 10.11.5. and duplication and copying files works very well for the actions of the SMB and AFP.

  If you have only tested using higher level, create a folder and see if the problem occurs when you are working on files inside this folder. If it isn't, then you have your bad permissions/ownership/ACL on the server. You should check the ACL as well as Posix ownership and permissions.

  Also, try to remove the part in the sharing Panel and then Server to add it again.

  C.

• username does not file sharing

  Trying to file on network share local wifi between MBA and iMac. Both on Yosemite.

  MBA sees the iMac on network:

  

  I click on "Connect under...". "and enter the name of the main account and the password (note: this combination works great on iMac when connecting at startup and for other operations).

  

  However, this same combination usr/pwd is rejected for sharing.

  Password sharing is somewhat different to the local password on iMac?

  Any ideas?

  OSX 10.11.1 (B 15, 42)

  Hey SaltSeaShark,

  It seems that if you try to connect to your iMac for file sharing on your local network and trying to connect using the user account name and password for this iMac, but it does not allow you to connect. Is this fair?

  One thing to check here would be to see if the iMac is configured for file sharing, because it is not enabled by default. Follow the steps in this article - OS X El Capitan: share your files with other users of Mac

  Note that you can set up file sharing for all users of the iMac or select specific users. Do not forget that you have configured the correct or users to share.

  Also, in System Preferences > Panel sharing > file sharing select the Options button. In the next window, you should at least have selected share files and folders using AFP . (Windows users would normally connect via SMB).

  How to connect with the file sharing on your Mac.

  Advanced options

  If you want to restrict the protocols can be used to connect to your computer using file sharing, click the Advanced Options in the sharing pane. You can then select the protocols are used by your Mac. By default, OS X Mavericks and later automatically enable SMB and AFP for compatibility with Windows, Mac using the Mavericks and Yosemite and Macs computers with older versions of Mac OS X.

  

  After ensuring it is properly configured, use the steps in this article to connect to shared iMac - volume OS X El Capitan: connect to shared computers and servers for files on a network

  Thank you for using communities of Apple Support.

  Calculation of the happy.

• Network drive cannot be selected in Time Machine, but works in the Finder

  Hello

  I have a NetGear wndr4500v2 router in which I now have my 1 TB HD plugged (HFS formatted). I've always used this drive for backups TM via the USB in my MBP, but decided it would be good to have all it wireless. Unfortunately I was not able to select the player in Time Machine.

  -I cannot connect / to connect/change player/server and all of its files in the Finder, no problem

  -Already played a bit with SMB and AFP sharing settings

  -Tried with router via an ethernet cable connection

  -NetGear Vaucluse to Time Machine support

  -Of course restarted devices

  -I run El Capitan on a 13 "MacBook Pro 2012

  All this with no result. I have not yet tried to do the old-fashioned way (https://www.youtube.com/watch?v=_VwHGSHSnDk) as I was hoping for an easy solution and beside that, I'm not sure that this guide still works on OSX 11 all thoughts about it, guys? Let me know!

  A device third-party network attached storage (NAS) or a router is unsuitable for use with Time Machine, especially if it's your only backup. I know that's not what you want to hear. I know that the manufacturer declares that the unit will work with Time Machine.

  Apple has published a specification for network devices that works with Time Machine. No third party provider, AFAIK, does meet this specification. They all use the application of Netatalk incomplete, obsolete Apple Filing Protocol.

  Apple does not endorse any device third-party network for use with Time Machine. See this support article.

  Network backup, use as destination an Apple Time Capsule or an external storage device connected to another Mac or a 802.11ac AirPort base station. Only 802.11ac base stations support time Machine, not older model.

  Otherwise, use Time Machine at all. There are other ways to save, although none of them are nowhere near as effective or as well integrated with OS X. I don't have a specific recommendation.

  If you are determined to continue to use the device with Time Machine, your only remedy for any resulting problem is the manufacturer (who will blame Apple, neither you nor anyone else but herself.)

• Computers stops after the connection to the server

  Hello geniuses.

  I'm having a strange problem and I know it won't be easy to diagnose, but let's give it a shot.  I have two iMacs in my studio, a 4 k and a 5 k, with El Capitan 10.11.2 and both connected to an ethernet network and talk to a server on a Mac Mini (latest OS and OS X Server).

  I mention the server, because I think it may be interesting, but that's just a guess.

  Basically both of these computers have a strange inability to stop.  You choose stop and they go through the motions all the way to the black screen with the toothed wheel turn, and then it just lingers there.  Forever.  Well, at least 24 hours because it is the longest, that it went unnoticed at the time.  Usually, I wait a few minutes and then make a stop of the force.  (I wait a few minutes because sometimes, not often, but sometimes, the computers will be correctly closed.)

  Both machines are wired on the server and use frequently shared fire (SMB and AFP) to load files on networked drives.  Yet once again, I mention this because this is the common point between these machines that seems to be the exception to a common use, and I wonder if the connection to the server is the process that prevents computers from closing properly.

  If anyone can help point me in the right direction would be great.

  Thank you!

  Well I guess this problem is unique to me, however, if someone else liquidate the same problem, I think I have it solved.  I changed the file sharing preferences to just AFP (disabled SMB).  This seems to have solved a variety of issues that I had with my network, including iMacs hanging on closing down.

• MacBook can't connect to iMac, iMAC, but can connect to Macbook

  I have a problem, I can not get my course around and I need help.  I have an iMAC (2009) and Macbook Pro (2010).  Recently, I upgraded the two systems to El Capitan (both systems run the updates).  Before the upgrade, via file sharing, I was able to connect and read/write to all shared folders and devices connected to my iMAC to my macbook after some tedious tweaking configurations - the largest in realizing that I had to disable SMB and AFP only.  I use the iMAC as a home port and have all my external hard drives attached to the iMAC, and before the upgrade, I could see all the readers (and their scores) as well as all files, I had set up the iMAC to share.  Vice versa for the iMAC for Macbook - I could read/write in all the shared folders on the iMAC Macbook.

  After the upgrade to El Capitan, right at the start, the MacBook has emerged as a player immediately shared in the finder and connected without problem.  I can currently read/write of the iMAC on the hard drive of the macbook.

  The problem is, the Macbook will connect is more of the devices connected to the iMAC or iMAC.  I've fiddled with settings as much as I can think of, such as disable sharing of files, it reactivated, remove shared folders and add them, check all the settings for all readers shared on the iMAC, etc.  Everything seems to be configured exactly how it was before the upgrade, but for the life of me I can't have the Macbook to connect to iMAC.  In the finder, I see the iMac in the list of shared devices, but it just says: the connection has failed, and when I click on the button "connect as", it returns the following error: "there is a problem connecting to the server"IMAC of Pottsy".  Check the server name or IP address, and then try again.  If you continue to have problems, contact your system administrator.  Whenever I click on the button "connect as" it just trying to connect, never offered me a way to enter a user name or password, so I don't know which credentials that it uses at this stage, although I guess they are the same as before the upgrade when everything worked.  I have not changed the passwords for one of the user accounts and the user name and master password on both machines are the same, if that matters.

  Does anyone have suggestions as to what might be causing this unit or a possible way to fix?  Recently, I received this iMAC to a friend and was completely in love with the configuration of shared devices and the way everything worked before the upgrade and find this problem.  It allowed me to share a hard drive that is partitioned as a time Machine to the two machines without having to unplug anything, among other things.

  In addition, AirDrop does not currently work in both directions which is really weird.  I am able to navigate to the MacBooks HD of the iMAC via devices shared and drag and drop the files, but said dropping "transferred failed" if I try that.

  I'd appreciate really no guidance that someone might be able to provide.

  Screenshot of sharing iMAC below settings:

  

  MacBook Pro sharing settings screenshot

  

  Thank YOU and GOOD VACATION.

  Well, I solved my problem after HOURS of madness, it's obviously something so incredibly simple that I could cry.  The MacBook was somehow not connected to iCloud - signature in iCloud enabled the MacBook to connect to the front just like iMAC.  I can't believe it wasn't an error message asking me to sign in iCloud.  I wonder to re-sign in iCloud always for reasons beyond me, and of course, once you done would have saved me countless hours of attempts without meaning, don't ' you must connect in iCloud message appeared.  SMH.

  So there you go people, if you are experiencing something similar, make sure that both systems are signed in iCloud.

  PEACE!

• M277dw MFP: MFP M277-DW Scan to network folder

  In the settings of the printer - tab analysis - scan to network folder Option. I tried to capture the information of folder in smb and afp format. None is accepted by the printer. Can anyone help? Note that this is to connect the printer to a shared folder on a MAC

  Thank you

  Hey @Hopflys, welcome to the Forums of HP!

  If I understand correctly, you configure the scan to network folder and despite your efforts, shared folder information is brings not accepted. Please take a look at the following post, written by @Gemini02 , as well as the steps to configure the feature described and easy to follow: Re: configuration of scan of file.

  If you need assistance, I would like to know the results of your efforts and I will do my best to help. If this solves the problem you are experiencing, please be sure to click on the I accept as Solution button below so that others can see what has worked for you.

  Thank you.

• LaserJet MFP M477fdw Pro: Scanning to network Mac folder

  I tried to configure the network path to a shared folder so that I can scan directly onto my Mac. I followed the instructions:

  -created a shared folder

  -sharing of files for my user name

  -compatible with the SMB and AFP file sharing
  -Full name

  -folder path \\192.168.178.20\Scans (scans of record is in my root)

  -He gave my username and password

  No mather what I try in the path of the folder or the test fails, and I can't scan. What I am doing wrong?

  Edit: when you use the Network Setup Wizard on my other PC scanning, I can even see above on my mac. I just can not connect?

  After 2 hours frustrating to try I finally found it. My Mac has my first and last name as username and contains a space. Rename my full name for 1 Word has solved the problem.

• access to the network drive on XP vm & Mac host

  I'm under vmware 2.0.5 and XP SP3 via bootcamp on OSX 10.5.8. If I map a network drive in a virtual machine XP, I can access is no longer the Mac host.  If I map the drive but share the network as a record disk using vmtools, I can access it from the Mac and XP vm.  Is this a normal behavior?  I would have thought the right way to proceed would be to treat all people as a 'computer' apolitical and connect directly to any external network resource rather than sharing an external resource via the host mac.  I also noticed that my score bootcap 'disappears' from my Mac when vmware is running... It's just for protection?

  Thank you

  Bruce

  Mapped network drives can be mounted to 1 place at one time, then Yes, what you're feeling is normal behavior.

  What type of network you are using?  NFS? SMB? AFP?

  When you use shared folders, we pass everything through a 'passive' network share to work around this problem (among other reasons), allowing you to access the folder of the host and theguest.

  The boot camp partition dismantles the workstation for the same reason... some things can not be mounted at 2 places at the same time.

• Slow connection to SMB/AFP file sharing

  Configuration:

  OSX 10.11.3 (15 D 21)

  Server V5.0.4

  Running services: calendar, file sharing, Manager profiles, Time Machine, VPN, Web, Wiki, DNS, FTP sites, open the directory

  We have a problem which has lasted for several months where clients that attempt to connect to file sharing (AFP or SMB makes no difference) takes too long to authenticate. He constantly takes ~ 40-45 seconds to open a session or even reject a bad password. The really strange part is that it affects all computers on our network with the exception of a Mac Mini. Seems not be customer specific, i.e. all users connect without delay on a Mac Mini and slowly on other computers. I was not able to determine differences in settings of network connection or on different computers, but I don't know there are parameters, I'm not aware of that.

  Did someone met with something like that?

  Thanks in advance.

  The faster connection Mac Mini there the active local folders?  Or using a faster SMB protocol?

• How to backup without identifier (NFS vs SMB/AFP)

  Hello

  you just bought a ReadyNAS 312 but do not yet know about some basic principles.

  I want to use mainly as a backup destination, but also as the main source for backups Crashplan. In detail I will not install Crashplan headlessly on the NAS (totally not supported) but I prefer to install on my computer, which is then connected to the NAS through my line (just check, taken Crashplan supported files attached nas backups).

  What I don't understand is how can automatically make sure Crashplan can see the files at all times... I think that this should be easy with NFS and Linux computers. I just need to configure actions to be mounted automatically at each start-up, right?

  What, Mac computers, is even achievable with SMB/AFP so that I don't connect all the time in the Finder.

  I know that these sounds of questions a bit silly, but it's the first time I have use a SIN 'serious '.

  To be honest: sooner or later we will return only Linux boxes in the House, but at this point we can not yet get rid an Apple computer.

  Thanks a lot for any suggestion

  netghiro wrote:

  My initial confusion is related to how to automatically assemble the network shares on my system (the a CrashPlan possibly running) to make them available to the local backup software (which will take care to copy the files to the NAS)... Sorry for the bad wording or maybe you misunderstand something.

  http://support.code42.com/CrashPlan/latest/backup/Mounting_Networked_Storage_Or_NAS_Devices_For_Back... answers for OSX and links to a similar article for Windows. I suspect that for Linux, you simply create a NFS mount point suitable, but I have not tried. In any event, you don't really need to go with headless on the NAS installation, if it presents the advantage to avoid the need for a separate device.

  netghiro wrote:

  I think that when I'm on Linux and using NFS shares that will be easily magically mount every time you start (I still wonder if the username/password on the NAS must the same on my computer and to be honest, I was wondering the same for the two AFP/SMB!)

  With Windows, the name of user and password may be different. Configure you in the Windows Credential Manager. I'm not a Mac guy, but I think that Keychain Apple does the same for network with OS x resources. I think that with Linux, you need to explicitly use the opening of session and password in the mount command (I don't think it's the equivalent of the Windows or Apple Keychain credentials manager).

  netghiro wrote:
  I have already subscribed to a (computer) personal unlimited plan, I can envision the family upgraded but happy enough to save a little money as well. I'll try to keep a couple of good games of local backup in the first place.

  Which is what I did. I have an unlimited plan for single computer for the NAS. I use Acronis image to back up the disks of PC 'C' on the NAS and also to use the SIN as a consolidated storage. I have 3 copies local of all (the primary account as a NAS) use and maintain CrashPlan as expensive disaster.

  My pro - 6 has 2 GB of ram, which worked well for a few years, but eventually unlimited retention of deleted files caused central CrashPlan CrashPlan to run out of memory. This is what prompted the request for assistance to Crashplan. The solution was to the retention value of the files deleted in 6 months and then consolidate archive. That took a while (Crashplan was not wise to this point). I've also increased the memory in the pro and CrashPlan defined to use the size of the memory possible max (which, on the pro, is about 3.5 GB with a 32-bit JVM).

  It has been working fine since that date (end of June). In any case, it's a good idea to lower the setting for the retention of deleted files. I also put deduplication to "minimal".