Unable to enable AFP file sharing, SMB won't allow connections. Is there a workaround?

After upgrading to Lion from Snow Leopard, I cannot enable file sharing. Checking the checkbox immediately unchecks it. When looking into this more closely, I can enable SMB, but not AFP, and my husband cannot connect to the SMB share when enabled- it just gives him a "Connection Failed" error.
When I try to enable AFP, I get this message in the console:
1/1/12 11:04:06.084 AM com.apple.coreservicesd: launch_msg(): Socket is not connected
1/1/12 11:04:06.000 AM kernel: nstat_lookup_entry failed: 2
When I enable or disable SMB, I get a combination of several of these messages in the console:
1/1/12 11:12:29.970 AM com.apple.smb.preferences: ERROR [launchd_client.cpp:138] failed to send GetJob message to launchd for job com.apple.smbd: Socket is not connected
1/1/12 11:12:30.000 AM kernel: nstat_lookup_entry failed: 2
Is there a way to repair or work around this? I bought Lion less than a month ago but can't find a way to contact Apple support directly.

I have tried numerous workarounds with no success. Everything worked fine on Snow Leopard as regards to connecting to my MBP from my Mac Mini. But with Lion, none of that works. Can we get a refund for Lion? This is atrocious!

Similar Messages

Enable AFP File Sharing via ARD through command line?

Anyone know how to enable AFP file sharing on a remote Leopard client using ARD? I had been sending Unix Commands to do most of my changes, but cannot figure out how to enable AFP file sharing through a unix command. I've tried running /usr/sbin/AppleFileServer but that doesn't seem to do the trick. Any ideas?

Howdy, Space Ranger!
I'd recommend checking out the following documentation to get filesharing going without interrupting a current user.
Apple Remote Desktop Administrator’s Guide
http://images.apple.com/remotedesktop/pdf/ARD3_AdminGuide.pdf
Page 145:
Executing a Single UNIX Command
Using the UNIX Command window, you can send a single command to the selected
client computers. The command is executed using the bash shell.
To execute a single UNIX command:
1 Select a computer list in the Remote Desktop window.
2 Select one or more computers in the selected computer list.
3 Choose Manage > Send UNIX Command.
4 Type or paste the command.
If your command is a multi-line script, enter each command on its own line. If you want
to break up a single-line command for better readability, use a backslash (\) to begin a
new line.
5 Set the permissions used to execute the command.
You can choose the currently logged-in user, or choose the name of another user on
the client computers.
6 Click Send.
For information regarding Terminal commands that can be useful (this is for 10.3 and later, but the relevant command does work in 10.8):
Mac OS X Server Command-Line Administration
http://manuals.info.apple.com/en_US/MacOSXSrvr10.3_CommandLineAdminGuide.pdf
Page 65:
Commands you can use to create share points and manage AFP, NFS, Windows (SMB), and FTP services in Mac OS X Server.
Share Points
You can use the sharing tool to list, create, and modify share points.
Best regards,
Allen

Unable to connect macs with afp file sharing

I am suddenly unable to connect my MacBook Pro to my Mini using afp file sharing. I've done this successfully many times in the past, most recently about three weeks ago.
After using Go -> Connect to Server and picking the previously used Favourite Server entry, I get the Connecting to Server window, then after about a minute I get a pop up that says:
Connection failed
The server may not exist or it is not operational at this time. Check the server name or IP address and your network connection and try again.
Then the Finder icon jumps about and in the Connecting to Server window the message is:
The Finder cannot complete the operation because some data in "afp://aragorn" could not be read or written. (Error code -36)
Both machines are connected by Cat-6 cable to the same router, File Sharing is enabled on both machines, and Airport is switched off. I can ping each machine from the other, and both otherwise work fine. I've also tried connecting using the IP address instead of the machine name, with the same result. I've even tried another router, with the same result.
Anyone seen this before?
thanks in advance,
I.B.

Thanks, j.v., for your reply. It's very strange, this.
I tried your suggestion, but to no avail. The destination machine is visible using ⇧⌘K and under 'Shared' in the sidebar of the Finder window, but selecting it from either place didn't work.
However, after the connection attempts failed, I tried clicking on the 'Connect as' button in the Finder window, and after a bit I got the login credentials window. It allowed me to log in, then connected with the access I was after.
I guess it must be some sort of access permissions issue, but it's quite odd that it only just started happening as I move files between these two machines frequently, and never had any problems before. The 'error code 36' message is completely useless for troubleshooting...

Why did I have to enable Windows File Sharing to share files between two Mavericks iMacs?

File Sharing failed between my Mavericks iMacs. The console logs showed that the target iMac saw the ntlmv2 protocol as unknown to the kdc. I fixed it by enabling Windows File Sharing on the target Mavericks iMac. I had tried disabling SMB on both iMacs and leaving AFP on, but then nothing happened when I tried to connect. Why did I have to enable Windows File Sharing to share files between two Mavericks iMacs?

When you enable file sharing you need to have either SMB (Windows) or AFP (historically Apple-native) file sharing checked. The default in Mavericks is SMB, and not AFP.
If you uncheck both, then the system will turn off file sharing. Apple supports the use of both SMB and AFP connections in Mavericks, so with only AFP enabled you should have been able to establish a connection, but there could be a small bug or configuration-specific snafu that you're encountering.
With AFP enabled only, try pressing Command-K in the Finder to open the Connect To Server dialogue, and in here enter the address to the system using afp:// as the protocol, such as the following (the name can be looked up in the Sharing system preferences):
afp://my_imac.local

Lion will not allow AFP file sharing

After upgrading my iMac to Lion, I tried to turn on File Sharing, but it would not allow it - I'd check the box, it would refuse the check. I had to go in to Options and check SMB Sharing to get File Sharing to work. However, I'd like to use AFP file sharing, not SMB. I still cannot turn on AFP sharing - I check the box, it unchecks itself in 1/2 a second.
My Macbook Pro was upgraded a couple months ago, and it does not have this issue. What am I missing?

I had this same problem so I opened the console application and viewed all messages. Then I tried to check the File Sharing checkbox and noticed that two new entries showed up.
3/31/12 9:21:05.415 PM com.apple.coreservicesd: launch_msg(): Socket is not connected
3/31/12 9:21:05.645 PM com.apple.coreservicesd: bind(): Address already in use
Each time I tried to check the checkbox, I received the same messages. I could of done more detective work but Address already in use may be some kind of memory leak issue or something so I simply rebooted my Mac Pro and then I was able to check the box and it stuck this time. Also, I was able to share my file like I intended.

Reseting the Hashed Password after enabling Windows File Sharing

Disclaimer: you'll need a good bit of knowledge about OS X, UNIX, and encryption to understand what I'm talking about.
All right, so normally OS X hashes user passwords using a salted SHA1 encryption. It uses shadowing so that you can't obtain the actual hash value using "% nidump passwd".
BUT, if you enable Windows File Sharing, all that changes. OS X re-hashes your password using the much less secure LANMAN encryption. This allows Windows machines to access your files. (LANMAN is what Windows used to encrypt passwords up through Windows ME. Later versions of Windows use NTLM instead, which is stronger.) This is why, the first time you enable Windows File Sharing, OS X warns you that enabling the feature will require your password to be stored in a less secure manner; it's downgrading the hash from SHA1 to LANMAN.
My question is: I'm done sharing files with idiot Windows users - how do I force OS X to go back to storing my password using SHA1?
Thanks guys.
-Bryan

Thanks biovizier. You're absolutely right, deleting the extra text after ";shadowHash;" and then reseting the password for the user's account does seem to force OS X to rehash the password using SHA1.
Just in case someone else has this question in the future, here's how to verify that your password is hashed in SHA1:
Log in as Root and open the /private/var/db/shadow/hash folder. You'll see files with long, weird names. You'll also see an XML file (with the extension *.state) for each of the files with long, weird names. The XML file contains several tags that tell OS X information about the hashed password - things like when it last logged on, when it was created, how many times login failed, etc.
We're interested in the other files - the ones that don't end in ".state"
To verify that SHA1 is being used, open the long, weird files in textedit. You should see something like this:
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000059G31HJ75BR54210P07Y57BC57094D643H78K8765L98C6X000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000
There should be a few more zeros; I've cut some out here to save space.
What should NOT exist, is the following:
57Y083D243109VGR45Z4B65812R8M087H65HJ8OK95T89L8JHL9000000000
000000000000000000000000000000000000000000000000000000000000
0000000059G31HJ75BR54210P07Y57BC57094D643H78K8765L98C6X00000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000
The second Hashed value does not start with zeros. This hash value is not SHA1. It is the less secure encryption method required for compatability with Windows.
If your hash file opens with zeros, you're using SHA1. Otherwise, follow Biovizier's procedure: Open NetInfo, select the user account whose password needs to be changed back to SHA1, look at the "authentication_authority" value, make sure the value is set to ;ShadowHash; and that no additional text follows that string, then reset the affected account's password. You can then log back in as root and re-check the hash files using textedit and you should find that the hash file opens with solid zeros instead of letters and numbers.
Do NOT manually edit the hash files in textedit. One of those files is the hash for the Root password. If you change that hash file, your root password will no longer work (because when you type MYPASSWORD, OS X will hash that string and find that the hashed value no longer matches the stored hash value in /private/var/db/shadow/hash and OS X will therefore reject your password as incorrect) and you will quickly find yourself locked out of your computer for good.
And finally, just in case you have the computing power of the NSA and are thinking about running the hashes I've listed here: A) They aren't the right length; I've left some characters out and B) I randomly substituted different alphanumerics in for the ones in my real hashes with no rhyme or reason.
Which brings me to another point: NEVER post your hashes online. Yes, it takes a TON of computing power to break them, but still, they're hidden away for a reason!
Anyway, I hope this helps other security buffs out there.
I'm going to make a suggestion to Apple that OS 10.5 be changed so that when you unclick "windows file sharing" the OS immediately rehashes your password in SHA1 again.
-Bryan

Personal File Sharing Quites when trying to connect

Everytime I try to connect from another mac to my G5 the personal file sharing unchecks and blocks the connection. Firewall is off.

Okay I did it and then repaired permissions and this is what it changed:
group is 501
Owner and group corrected on ./Library/Preferences/SystemConfiguration/preferences.plist
Permissions corrected on ./Library/Preferences/SystemConfiguration/preferences.plist
User differs on ./Library/Preferences/com.apple.ByteRangeLocking.plist, should be 0, owner is 501
Permissions differ on ./Library/Preferences/com.apple.ByteRangeLocking.plist, should be -rw-rw-r-- , they are -rwxrwxrwx
Owner and group corrected on ./Library/Preferences/com.apple.ByteRangeLocking.plist
Permissions corrected on ./Library/Preferences/com.apple.ByteRangeLocking.plist
The privileges have been verified or repaired on the selected volume
It only did stuff on that file and the -rw-rw stuff is that read write? because i don't want it changing that?

In the file menu it won't allow me to send a sms, why?

When I'm signed into my ichat and I click on the file menu it won't allow me to have the option to send an SMS. I'm not sure why, any ideas?

HI,
You have to be in the United States
The Buddy has to be a Phone number that is also in the United States (On a service that Accepts AIM forwarded SMS)
So...
In the Buddy list the Buddy has to look like +1 234 456789 (but a real Mobile/cell number)
Then the option in the menu should go dark when you highlight this Buddy
10:04 PM Sunday; April 1, 2012
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 iMac 2.5Ghz 5i 2011 (Lion 10.7.3)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

Enabling 'File Sharing' on my Mac allows my Macintosh HD and Boot Camp to be visible and writeable on my home network. How can I turn this off, so that only folders/files I share are visible?

So I've been trying recently to get my MacBook Pro connected to my home network. There are two other desktop computers in the household, and I'd like to be able to connect to their shared folders, as well as allow them to access shared items on my MacBook Pro. I think I've read all the documentation regarding this issue on the Apple Support site. I do have administrator privileges on my Windows 7 computer.
Issues connecting from PC to Mac
A couple of days ago, I enabled SMB File Sharing on my MacBook Pro, and in addition to the already shared Public folder, I added another that resides within Movies. Then I went to my Windows 7 PC, and under Network, my MacBook Pro appeared. I double-clicked on it (I cannot remember if I was asked to enter my Mac user credentials; I think I was), and I saw the two shared folders: Public, and the Movies folder.
However, today I went back to my Windows 7 PC, accessed my MacBook Pro, entered username and password, and in addition to the two shared folders, both my Macintosh HD and Boot Camp HD appeared as shared folders, both fully writable. However, under File Sharing on my MacBook Pro, only the two shared folders (Public and Movies) appear in the Shared Folders list.
How can I prevent my Mac from sharing my entire partitions? How can I configure it so thatonly the folders I select to share are actually broadcasted across my home network? Also, it would be ideal if I can access these shared folders from my Windows 7 PC without having to enter my Mac user credentials.
Issues connecting from Mac to PC
I have a user account on my Windows 7 PC with the same name as my Mac, but with no password. When I try to connect to my PC from my Mac, the enter credentials dialogue pops up and asks me to either log-in as a Guest, or enter my User credentials.
The Guest account is disabled on Windows 7, and I assume that's I'm not able to log in as Guest (if it is possible to connect as a Guest without having to enable the Guest account on Windows 7, please let me know). Leaving the password field blank on the enter credentials dialogue tells me that it's incorrect (even though I don't have a password on my Windows 7 account).
Is it possible to access shared files and folders on my Windows 7 PC from my Mac without having to create a password protected account? If not, is it possible to create a password for the sake of accessing shared files, while not requiring it to log in to the account? I'm sorry, I know this last bit more falls under the category of Windows Help.

Sharing files from a Mac to a PC is a different animal. I've never done it myself so you may want to repost a separate question on this topic.
From what I understand, in order to access files from a Mac on a PC, you must log in using your Mac username and password (no anonymous file sharing). Since this is not very desirable from a security standpoint, Apple recommends creating a separate user account on the Mac that is dedicated to file sharing. Give that account access only to the files/folders you want to share. You can then give that user account name and password to your Windows users.

Mac OS 9 AFP file sharing volume not visible under Mac OS 10.5

An old blue-white PowerMac G3 running Mac OS 9.2.2 with file sharing on is not visible on the network for a MacBook Pro running Mac OS X 10.5.5. – However, a PowerBook G4 with Mac OS X 10.4.11 perfectly shows the G3.
Connecting to the G3 works on the new MacBook Pro with OS X 10.5 if I use the server's IP-address (afp://xxx.xxx.xxx.xxx) but does not work if I use the server's name (afp://<servername>).
All other shares on the network are visible for both the MacBook Pro running OS X 10.5 and the PowerBook G4 running OS X 10.4.
Why does the MacBook Pro with Mac OS X 10.5.5 not show the G3?
Why can't I connect to the G3 using its AFP name?

I think this is because there is no AppleTalk on Leopard.
Ah, I stand corrected........
Go to SystemPreferences > Network
Select your connection in the left column. Advanced > AppleTalk
Enable AppleTalk for your connection.
sp
Message was edited by: brainslice

File sharing reports too many users connected

SPECS: Mac Mini Core 2 Duo 2 GHz, 2G RAM, Mac OS X 10.6.4. Other users in office also running similar hardware and Mac OS X 10.6.4.
CLARIFICATION: This Mini is used as a file server in a small law office (4 other workstations). It is running Mac OS X Client, not Server. I refer to the machine as "the server" but wanted to be clear the operating system is the same on all stations.
HISTORY & CONFIG: This system was setup in November 2009. It provides simple file sharing storage for a 4-user law office and runs Retrospect (version 8.1.626) to do some local and network backup operations. At the time it was setup, it was also running Now Up-to-Date Server but that program is no longer supported, and it has been removed from the computer (May 31, 2010). In late March 2010, I installed Daylite Server as a replacement for Now Up-to-Date. All stations are running Mac OS X 10.6.4, and have always been at the most recent Mac OS X 10.6.x revision within a few days of the release of a major update.
PROBLEM: Occasionally, clients cannot connect to the server (and I don't have the exact error message -- next time it happens, someone is supposed to get a screenshot). When this happens, if you go to the server and open the file sharing control panel, then click "options", you will see an impossible number of people are connected. The first time this happened was on April 28, 2010, when it reported 41 users were connected. Mac OS X Client has an upper limit of 10 simultaneous user connections, so you can see this number is not possible. Additionally, these are "phantom" logins because you can execute this command in Terminal to see the IP addresses of any connected users:
netstat -n | grep '.548'
And when I do this, unless there was someone who had logged in prior to the "phantom explosion", it never shows any connections. On two occasions, I've actually been in the office late one night to do maintenance, checked the server before I left and found 0 connected users, then got a call in the morning that the first person who attempted to connect was blocked and the server showed 10 or more users connected.
I do not believe this is some kind of security breach. The server is not Internet-accessible, and as is shown by the netstat command, there really isn't anyone logged in anyway. I consulted with Marketcircle (makers of Daylite) because it seemed very coincidental that I installed their software just prior to the beginning of this problem, but they claim Daylite does not make any use of the Mac file sharing system. But, again, since these aren't real users, I suppose it's possible a bug in their software is somehow upping the Mac's connected user count erroneously?
Restarting the server always fixes the problem -- until it happens again. This Mac Mini is a pretty simple station -- just runs Daylite Server and Retrospect Single Server, plus the basic file sharing. Anyone have any ideas why this keeps happening?

I would say odds are likely this is correct. On at least two occasions I can think of where I verified everything was okay and later discovered a "phantom explosion", a Retrospect backup would have run. Our backups typically run at 3 AM. Is this a known issue with Retrospect? If so... not sure why it doesn't happen all the time. And in my own office I have a pretty similar setup on an entirely different computer that multiple people connect to, and it never does this. Color me confused.

Bluetooth file sharing between computers will not connect with my iPad 2. Any help will be nice

I have been trying to send files through bluetooth and cannot get the ipad to receive. Does anyone know how to fix this? Can it be fixed?

That depends.
If you have Pages on your iPad and Pages on your computer they should both support iCloud. Setting up iCloud and turning it on for Pages will allow Pages documents to be sync to both devices simultaneously.
I do this all the time. Changes I make on my iPad are automatically synced to my iPhone and computer.

How DELETE song file...won't allow me!?

Imported songs from my husband's iPod into my pc. Cannot delete songs! Info is greyed out (cannot edit, etc). Says it might be write-protected. Used Windows Explorer and directly deleted file, but now there's an exclamation point next to file in iTunes. How do I COMPLETELY delete these song files!?

There was a recent iTunes bug that prevented deleting. For now, just leave it in your library with the exclamation point. Next time you restart Windows, try again to delete it and it just may work. It did for me.

Time Capsule will only allow Apple products to connect to internet, PC ad PS3 shows excellent signal from TC but won't allow connection.

I have a Mac, iPad, iPhone and several iPod touch devices that can connect to the internet through Time Capsule without a problem. There are times when my work PC and PS3 won't connect to the internet through TC. There doesn't seem to be any reason why this happens and it just started happening in the last month. The PC indicates an excellent wireless connection. If you have any suggestions please put it in very easy to understand terms (I'm not a very technical person).

Ok.. that is very helpful. What OS is your Mac running?
Please now take a few screenshots of your airport utility so I can see the setup of the TC.
But it looks like it is bridged.
Open the utility and click on manual setup.
Take a screenshot of the summary page.
Take a screenshot of the internet tab.
And the other two tabs there.. TCP/IP
And DHCP
Yours will look different to mine.. but there is nothing in them that is needing to be hidden.. it is useless info to another person. I post mine to show it is useless in case it worries you.
I do need some more info.
What is the modem you have? Is it also a wifi router. In the list of wireless you took the snapshots of, you have several wireless names.. I want to know which of those are yours??
The WEP security device is a problem. It is old and near useless.. if you don't own it that is fine.. but if it is yours get rid of it.
Can your PC and PS3 connect to the internet via some other wireless?
It looks like you might be able to simply bypass the TC to connect the PC.
Sometimes it is easier to solve this problem by using different hardware.. and a secondary wireless AP can easily be plugged into a modem router if that is what you have to provide wireless just for your PC devices.
What model is your TC.. ?
Please look at the bottom rubber mat.. there is a number in the top line of the rubber molding.. It will say A1254 or A1302 or A1355 .. those are the numbers for Gen1 , 2 and 3. Gen4 it is on the paper label.. where it always should have been A1409. Please tell me that number.

Adobe Browserlab - Tells me network connection settings won't allow connection

I can use the Dreamweaver --> File --> Preview In Browser menu to test from so maybe it's no big deal but was just wondering if I was missing something by not having Browser Lab and if I am how do I modify my Mac Network connection settings to get Browserlab to work?
me again -- Dave V.

In this one http://kb2.adobe.com/cps/846/cpsid_84665.html
On Mac OS X
Do the following:
Quit all CS5 applications.
Open the Apple Property List Editor (supplied with the Apple SKD) or other property list editor application..
Open the file [Startup Disk]/Library/Preferences/com.adobe.AdobeOnlineHelp.plist.
Select Root to see the subentries.
Locate the string object AdobeOnlineDefault. if the key does not exist, you'll need to create it.
Double-click this string value and set it's Value Data to "0" to disable CS Live access.
Save the com.adobe.AdobeOnlineHelp.plist file.
Quit the plist editor.
I put that value to 1 instead of 0 and it made everything work. The CS Live button in the Tool bar in all Adobe applications is for access to various online Adobe services, BrowserLab among them. I don't have Property List Editor but used Prefsetter and it worked. I've for a long time had my Adobe applications saying that they are not connected to the internet. But doing this setting today solved it for me. CS Live is not only for groups. I am a one-person operation but the CS Live button is the easiest way to reach those services you want. Provided the application don't says that it is not connected to the internet... The Adobe technote describes how top turn it off, not how to turn it on. And it is only the AdobeOnline Default that needs changing. Nothing else.

Unable to enable AFP file sharing, SMB won't allow connections. Is there a workaround?

Similar Messages

Maybe you are looking for