Suddenly can't connect to shared computers or screen share
For some reason I can no longer connect to my shared computers. I can however connect to MY computer from my shared computers, if that makes sense.
From my own computer, when I go to my shared list in the finder, I click on a computer (normally it all automatically connects because I have the password remembered), I click "connect as" and I never get any response, sometimes a "connection failed" I know file sharing is enabled on all computers.
Is there a way to refresh my list? What can I do to reconnect to my shared computers? This seems to have been happenings since I last updated the OS.
Also, I can no longer do a screen share where I was doing this regularly every day.
Thanks
Dan
Message was edited by: Daniel Peck
iMac intel, MacBook Pro, MacBook, Mac Mini,
Mac OS X (10.5.4)
Have you tried connecting directly using apple-k (or Finder->Go->Connect to Server), using something like afp://1.2.3.4/ or smb://1.2.3.4/ or whatever protocol you're using? Does that also not work?
There should be a log file in /Library/Logs/AppleFileService/. Check that to see if there is useful information in there. Also, your system.log might have something -- you can look at that with the Console application.
Is your firewall set to the most open setting (for troubleshooting purposes)? Do the other machines use a firewall?
I tried opening up the firewall and allowed all incoming connections.
no luck
I checked the log file and here's what it had, I don't know what it all means:
7/27/08 6:07:13 PM com.apple.launchd[202] ([0x0-0x5be5be].dotmacsyncclient[12981]) Exited with exit code: 114
7/27/08 8:48:56 PM com.apple.backupd[8961] Found partially deleted backup - trying again to delete: 2008-07-26-184903
7/28/08 7:30:38 AM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[5451]) Exited: Terminated
7/28/08 7:30:38 AM com.apple.launchd[1] (com.apple.ScreenSharing.server[14496]) Exited: Terminated
7/28/08 8:06:28 AM PDFpen[14572] .sdef error: Operation could not be completed. (NSXMLParserErrorDomain error 1549.)
7/28/08 8:06:28 AM PDFpen[14572] line number: 2
7/28/08 8:06:28 AM PDFpen[14572] .sdef error: Operation could not be completed. (NSXMLParserErrorDomain error 1549.)
7/28/08 8:06:28 AM PDFpen[14572] line number: 2
7/28/08 8:06:28 AM PDFpen[14572] _NSMacOSTypeFromString(): string 'color' is not exactly 4 characters long.
7/28/08 8:28:34 AM firefox-bin[14691] Error loading /Library/Internet Plug-Ins/Photo Center Plugin.plugin/Contents/MacOS/Photo Center Plugin: dlopen(/Library/Internet Plug-Ins/Photo Center Plugin.plugin/Contents/MacOS/Photo Center Plugin, 262): Library not loaded: /usr/lib/libcrypto.0.9.dylib
Referenced from: /Library/Internet Plug-Ins/Photo Center Plugin.plugin/Contents/MacOS/Photo Center Plugin
Reason: no suitable image found. Did find:
/usr/lib/libcrypto.0.9.dylib: mach-o, but wrong architecture
/usr/lib/libcrypto.0.9.dylib: mach-o, but wrong architecture
7/28/08 8:28:34 AM firefox-bin[14691] Error loading /Library/Internet Plug-Ins/Photo Center Plugin.plugin/Contents/MacOS/Photo Center Plugin: dlopen(/Library/Internet Plug-Ins/Photo Center Plugin.plugin/Contents/MacOS/Photo Center Plugin, 262): Library not loaded: /usr/lib/libcrypto.0.9.dylib
Referenced from: /Library/Internet Plug-Ins/Photo Center Plugin.plugin/Contents/MacOS/Photo Center Plugin
Reason: no suitable image found. Did find:
/usr/lib/libcrypto.0.9.dylib: mach-o, but wrong architecture
/usr/lib/libcrypto.0.9.dylib: mach-o, but wrong architecture
7/28/08 8:28:32 AM [0x0-0x657657].org.mozilla.firefox ### MRJPlugin: getPluginBundle() here. ###
7/28/08 8:28:33 AM [0x0-0x657657].org.mozilla.firefox ### MRJPlugin: CFBundleGetBundleWithIdentifier() succeeded. ###
7/28/08 8:28:33 AM [0x0-0x657657].org.mozilla.firefox ### MRJPlugin: CFURLGetFSRef() succeeded. ###
7/28/08 8:28:34 AM [0x0-0x657657].org.mozilla.firefox 2008-07-28 08:28:34.745 firefox-bin[14691:10b] Error loading /Library/Internet Plug-Ins/Photo Center Plugin.plugin/Contents/MacOS/Photo Center Plugin: dlopen(/Library/Internet Plug-Ins/Photo Center Plugin.plugin/Contents/MacOS/Photo Center Plugin, 262): Library not loaded: /usr/lib/libcrypto.0.9.dylib
7/28/08 8:28:34 AM [0x0-0x657657].org.mozilla.firefox Referenced from: /Library/Internet Plug-Ins/Photo Center Plugin.plugin/Contents/MacOS/Photo Center Plugin
7/28/08 8:28:34 AM [0x0-0x657657].org.mozilla.firefox Reason: no suitable image found. Did find:
7/28/08 8:28:34 AM [0x0-0x657657].org.mozilla.firefox /usr/lib/libcrypto.0.9.dylib: mach-o, but wrong architecture
7/28/08 8:28:34 AM [0x0-0x657657].org.mozilla.firefox /usr/lib/libcrypto.0.9.dylib: mach-o, but wrong architecture
7/28/08 8:28:34 AM [0x0-0x657657].org.mozilla.firefox 2008-07-28 08:28:34.746 firefox-bin[14691:10b] Error loading /Library/Internet Plug-Ins/Photo Center Plugin.plugin/Contents/MacOS/Photo Center Plugin: dlopen(/Library/Internet Plug-Ins/Photo Center Plugin.plugin/Contents/MacOS/Photo Center Plugin, 262): Library not loaded: /usr/lib/libcrypto.0.9.dylib
7/28/08 8:28:34 AM [0x0-0x657657].org.mozilla.firefox Referenced from: /Library/Internet Plug-Ins/Photo Center Plugin.plugin/Contents/MacOS/Photo Center Plugin
7/28/08 8:28:34 AM [0x0-0x657657].org.mozilla.firefox Reason: no suitable image found. Did find:
7/28/08 8:28:34 AM [0x0-0x657657].org.mozilla.firefox /usr/lib/libcrypto.0.9.dylib: mach-o, but wrong architecture
7/28/08 8:28:34 AM [0x0-0x657657].org.mozilla.firefox /usr/lib/libcrypto.0.9.dylib: mach-o, but wrong architecture
7/28/08 8:38:27 AM com.apple.launchd[202] (0x10c9a0.Locum[14726]) Exited: Terminated
7/28/08 8:38:32 AM Disk Utility[14727]
********
7/28/08 8:38:32 AM Disk Utility[14727] Disk Utility started.
7/28/08 8:38:39 AM Disk Utility[14727] Repairing permissions for “Macintosh HD”
7/28/08 8:38:39 AM Disk Utility[14727] Reading permissions database.
7/28/08 8:38:39 AM Disk Utility[14727] Reading the permissions database can take several minutes.
7/28/08 8:38:58 AM SystemUIServer[222] found device
7/28/08 8:39:38 AM Backup[7930]
* -[NSConditionLock unlockWithCondition:]: lock (<NSConditionLock: 0x1453c380> '(null)') unlocked from thread which did not lock it
7/28/08 8:39:38 AM Backup[7930]
* Break on _NSLockError() to debug.
7/28/08 8:39:38 AM Backup[7930]
* -[NSConditionLock dealloc]: lock (<NSConditionLock: 0x1453c380> '(null)') deallocated while still in use
7/28/08 8:39:38 AM Backup[7930]
* Break on _NSLockError() to debug.
7/28/08 8:40:26 AM com.apple.launchd[202] (0x10e0e0.Locum[14762]) Exited: Terminated
7/28/08 8:40:30 AM com.apple.launchd[202] (0x10e0e0.Locum[14767]) Exited: Terminated
7/28/08 8:41:15 AM com.apple.launchd[202] (0x10de40.Locum[14770]) Exited: Terminated
7/28/08 8:43:35 AM Disk Utility[14727] Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/lanArrow.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
7/28/08 8:43:35 AM Disk Utility[14727] Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/lanCheck.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
7/28/08 8:43:35 AM Disk Utility[14727] Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/lanDisabled.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
7/28/08 8:43:35 AM Disk Utility[14727] Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/wanArrow.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
7/28/08 8:43:35 AM Disk Utility[14727] Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/wanCheck.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
7/28/08 8:43:35 AM Disk Utility[14727] Permissions differ on "Applications/Utilities/AirPort Utility.app/Contents/Resources/wanDisabled.png", should be -rwxrwxr-x , they are -rw-rw-r-- .
7/28/08 8:44:30 AM Disk Utility[14727] Group differs on "private/etc/cups", should be 0, group is 26.
7/28/08 8:44:36 AM Disk Utility[14727]
7/28/08 8:44:36 AM Disk Utility[14727] Permissions repair complete
Ok, it shouldn't be too bad. Open the Terminal application from your Utilities folder. In the terminal window, type the following (you will not be able to cut-and-paste these commands, so read this through):
mkdir /Volumes/test (hit enter here -- do not type this)
mount_afp afp://1.2.3.4/volume /Volumes/test (hit enter here -- do not type this)
Note the following in the above commands:
1.2.3.4 should be the IP address of your remote computer. The "volume" after the IP address should be the name of the volume you are sharing out from your remote computer.
For example, I have a remote Mac with the IP address of 192.168.1.2, and I'm sharing my "Public" folder. So, I would do this from the command line:
Post the output of any failures. Also not that when using the command line, it is not uncommon for a command to return nothing when it completes successfully. So, do not be alarmed if you hit enter after these commands and you get no output -- that is to be expected. If the mount_afp command actually worked, you should be able see files on your shared volume by typing:
Liberty-Bay-Server:~ libertybay$
Liberty-Bay-Server:~ libertybay$ mkdir/Volumes/test
-bash: mkdir/Volumes/test: No such file or directory
Liberty-Bay-Server:~ libertybay$ mkdir/volumes/test
-bash: mkdir/volumes/test: No such file or directory
Liberty-Bay-Server:~ libertybay$ mount_afp afp://10.0.10.248/public/Volumes/testusage: mount_afp [-o option1[,option2...]]
afp://[username:password]@rhost[:port]/volume node
Liberty-Bay-Server:~ libertybay$
I'm not sure what it all means. I figured that my public folder is shared. On my computers I have file sharing enabled and then I have to type in the username and password in order to gain access to all the files, which is usually how I do it, and I have my computer set to remember all the passwords so I don't have to retype each time. I don't know if that would make a difference in what I type in the terminal.
I did not do the test yet, simply because I don't know what I got here.
Thanks again
Oh, and the day is coming to a close so I'll be leaving the office. I won't have access to these computers until tomorrow. To be continued!
Nothing conclusive, it looks like the commands were difficult to read in the forum -- there should have been a spaces in there. For example,
mkdir /Volumes/test
has a space between the "mkdir" (this is a command that makes a directory) and the "/Volumes/test", which is the directory you are trying to make.
Likewise, the mount_afp is:
mount_afp afp://10.0.10.248/Public /Volumes/test
and there is a space after "mount_afp" and a space before "/Volumes/test". Now that you've posted the IP of your remote machine, you can probably just cut-and-paste what I typed above...
i'm having the same issue. i have always been able to connect to both my computes fine, now i can't. i tried the terminal solution but it came back with this,
AFPMountURL returned error -1069, errno is -1069
this is driving me nuts, any help?
-5019 is a "parameter error", which means that something in your mount_afp command isn't correct. For example, you're not really sharing out a "public" folder. Can you verify on the remote machine which folders you are sharing? Be sure to use one of those names in the mount_afp command.
Once you are sure of a shared folder, try the mount_afp command again (you don't need to repeat the mkdir command, which has already succeeded).
Having the same issues here - I checked the System Preferences and under Mobile Me I get this warning:
Back to My Mac: On
Back to My Mac isn't working properly because it requires a router that supports NAT Port Mapping Protocol (NAT-PMP) or Universal Plug and Play (UPnP). Make sure your router supports one of these protocols and that it is enabled.
What gives? I'm using an Apple Extreme Base Station - there are 5 Macs connecting to it - everyone can access the Internet OK and I can see every computer listed in the Finder Window when they're on - I just cannot connect - either via Finder, Screen Sharing or using 'Apple-K'
I am having the same issues. I noticed this yesterday. I use to be able to connect to a shared computer through the finder window but now I can no longer do this. I have another mac and I am able to connect to the computer that has the networking problems just fine.
