Incorrect Username/Password Error When Copying Files or Folders

Our business uses a Mac Mini (with OS X Yosemite) and the Server App to share our internal files. We've had this set-up for over year now with everything running smoothly. As of late however, we are no longer able to copy files or folders that reside in all shared folders. Basically, when we try to copy any file or folder that resides within any of our share points, we get the error 'Can't connect to the server because the name or password is incorrect'. This error occurs for every user account, including my own which has been specified as an administrator account. We are able to add files and folders (i.e.: copy from our local computers to the shared folders) as well as rename files and folders that reside within the shared folders. We are also able to create new folders without any error so I'm pretty certain that it is not a permissions issue. In addition, I've tried completely removing all shared folders and re-creating them but still get the same error. I've also tried creating new user accounts (both Local Directory and Local Network Directory accounts) and the problem persists when logged to the server using these new accounts. I simply don't know what else to do as this seems to be a software glitch. Any ideas?


Thank you

Posted on Jul 8, 2016 9:01 AM

Reply
22 replies

Jul 8, 2016 10:09 AM in response to JuiceTinKing

OK, one little update. We have one mac client computer (iMac) that's still running OS X Yosemite. The user on this computer is able to copy files & folders without receiving this error. This same user also has a Macbook which is running El Capitan. Using their same network login credentials to access the server from their Macbook results in the same error message. All other users that receive this error are also running El Capitan on their macs. With this latest development, I'm pretty much able to conclude that this error is a result of El Capitain clients accessing a share folder on a Yosemite server. What's odd however is that I have not always had this error since upgrading to El Capitan. I'm pretty sure this problem only came up within the last month or so leading me to conclude that either and update to El Capitan (on our client computers) or an update to Yosemite or the Server app)on the server computer has created this error. The question is...will upgrading the server computer to El Capitan resolve this issue or am I in for a whole new can or worms??

Aug 3, 2016 2:15 AM in response to JuiceTinKing

Were you ever able to overcome this issue. I have the same issue now with a clients network.

If I sign in with her proper user credentials from her El capitan upgraded Macbook to the Yosemite server, I am unable to copy and paste, receiving the exact same error. However, if I connect as a "Guest user" I receive a different error, "the Finder can't complete the operation because some data in "test.pdf" can't be read or written. (Error code -36)"

However it actually still pastes the item in the location and it is accessible and working 100%.

Obviously that is a security risk and cannot have all folders setup with guest access rights.

Aug 3, 2016 9:20 AM in response to Namtrooper

No, unfortunately I was never able to find a solution to this issue other than manually copying the items on the local client computer desktops and then transferring them over to the server. Not ideal but it gets the copying task done when required. That is certainly strange that it gives you a different error when logged in as a guest but still ends up copying the actual item. For us, we commonly copy a folder that we use as a template for our project files that has several sub-folders that reside within it. When copying this folder, we get the error 'Can't connect to the server because the name or password is incorrect' but the main folder does end up copying. However, it doesn't contain any of the sub-folders that existed within the original. That is what's particularly strange about this bug is that it does actually perform some of the copy/paste function. Hopefully upgrading to El Capitan would resolve this issue but at this point, I'm thinking of simply waiting for Sierra...

Aug 3, 2016 11:56 PM in response to JuiceTinKing

There are unfortunately no guarantees that Apple will resolve this glaring issue in a future release of their OS.

I guess I will have to consider rolling back to a previous version of the Mac OS just to resolve this specific problem.

The actual reason I actually upgraded the OS is to resolve another Microsoft office word corruption issue found on Office 2011 for Mac. Feels like their is just no winning in this scenario.

Isn't there anyone out there with a solution to this problem?

Aug 4, 2016 8:32 AM in response to danmoth

I have yet to try upgrading the mac mini to El Capitan as I'm always concerned about new issues arising from upgrading the OS. As MacOS Sierra will be arriving soon, I'm contemplating simply waiting for that release. However, seeing as how we're starting to discover several users with the same issue, I'm contemplating biting the bullet and upgrading the server to El Capitan this weekend to confirm whether this will in fact resolve the issue.


I do know without a doubt that this particular error did not always exist with our El Capitan clients accessing the Yosemite server drive. I was running like this for almost a year without any problems copy/pasting items. It's either one of the El Capitan client updates or a Yosemite update within the last few of months that has caused this issue to surface. Does anyone know of any significant/specific changes in El Capitan over the last couple of updates that could pinpoint the actual cause of this bug?


I will be sure to post an update if/when I've had the opportunity to upgrade the server over the weekend...

Aug 8, 2016 12:07 AM in response to JuiceTinKing

It has also been brought to my attention by my client actually, that they purchased a Mac that came with El Capitan pre-installed. This machine, has no problems whatsoever on the network. Which makes me wonder if something about the upgrade from the previous older version of Mac OS X is causing the problem.

Just thought I should bring this to everyone's attention as it might be something to think about.

Maybe I should do a clean re-installation of Mac OS X El Capitan instead of the upgrade path I chose?

Any suggestions?

Aug 8, 2016 5:54 AM in response to Namtrooper

Ah that is in contrast to our situation. We purchased 3 new machines, all running El Capitan, and they all seem to have the same issue as the other machines that were upgraded to El Capitan. Just to make things more complicated!


We have planned an upgrade for the mac-mini to El Capitan this weekend, hopefully that will work.. Will let you know if so. Then we need to work out why we get so many permission errors...

Aug 31, 2016 1:52 PM in response to JuiceTinKing

Actually it's not a must to upgrade the server to El Capitan - if there's any other reason not to.


OS X clients experiencing this issue not only run El Capitan - while the server is a pre-El Capitan OS X (like Yosemite), but also > clients are connected via SMB.

If you disconnected the server and connect to it manually by cmd+K and entering the server address:


afp://serveripaddress


...then the connection to the server will be established over AFP.


When connected via AFP, the copy+paste of files and directories is working as expected.


If you connect to the server my clicking on it's name in the sidebar under 'Shared', then Finder will try to connect to the server via SMB, and only in case the server does not offer SMB, then the Finder switches over to AFP.


You can solve it easily by turning off SMB on server side in File Sharing... in case there are no PCs on your network that connect to the server. If you have, then manually connecting is the way to go. Also you can create an alias from the connected server, and next day when you click on the alias, it will connect via AFP - and if you let Finder remember the credentials in keychain, then it will also connect without asking for password.

So aliases also contain the information how the connection was made: SMB or via AFP.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Incorrect Username/Password Error When Copying Files or Folders

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.