Currently Being ModeratedOct 1, 2012 9:06 PM (in response to Ronohki)
I have a similar problem although my 10.6.8 machine can connect to the 10.8.2 machine. Like you though, the 10.8.2 machine cannot connect to the shares on the 10.6.8 machine. I can share the screen though.
Currently Being ModeratedOct 28, 2012 4:27 AM (in response to Ronohki)
I had a similar issue after installing a new macmini running mountain lion to my network. Mt does not connect to less secure service.s like those of snow leopard. I activated the legacy afp on the new mini as per the link posted by satcomer and it woked. Have to admit have only tried accessing from new mini to old one and not the other way.
Hope this helps
Currently Being ModeratedJan 23, 2013 6:28 PM (in response to Ronohki)
Oh yeah!!! Finally found some guys with the same problem than i have!!!! My 10.8.2 MBP see my imac (10.6.8) but that's all! I've been try connecting wireless direct or by firewire network mode between two mac, AND NOTHING! Just ping replys...
Currently Being ModeratedFeb 20, 2013 9:42 AM (in response to Ronohki)
ONE SOLUTION: USE IP ADDRESSES
My Lion machine can see (ping) the Mountain Lion machine, but not other way round. And the Lion box can't connect to the Mountain Lion box as a server when connecting as afp://machinename.local wouldn't work.
However, connecting to afp://IPaddress DID work. Example: afp://10.0.1.6.
You can use the ifconfig command in the terminal to get your IP address. There are probably other ways, but that's how I habitually do it. It may be something like 192.168.x.y or 10.0.x.y.
Worked for me - can't guarantee others. And still can't see the Lion box from Mountain Lion although when I'm on another network, my Finder window fills up with lots of other Macs. Weird.
Currently Being ModeratedFeb 22, 2013 2:38 PM (in response to chestnutcow)
I have the same problem - cannot connect from 10.6.8 to 10.8.2.
Every time I try to connect, netauthagent on 10.6.8 crashes.
Do you see this?
Check your ~/Library/Logs/DiagnosticReports
I have found a weird workaround:
The server's full user name must contain a space (chestnut cow).
On the client side, in the connect dialog enter the name with the space.
Please let us know if this works for you.
Currently Being ModeratedMar 3, 2013 6:49 PM (in response to Ronohki)
Same here – both computers on 10.8.2 – neither connects but both see one another in the sidebar. Really getting annoyed with this one. Same wireless network, both with internet connectivity. Oddly enough, when I send out a broadcast in terminal I get responses from most of my iDevices, but not from the other mac which has the same netmask and same broadcast ip. This is a head scratcher.
Currently Being ModeratedMar 13, 2013 1:44 PM (in response to lestudio)
after a lenthy session with apple care I have my problem fixed. after being told there was no fix , unfortunately filesharing either worked or it didn't, I got to a senior senior adviser. We eventually tried screen sharing and that worked. I was able to connect to my 10.8.2 machine and share it's screen. That drove apple care tech to check the firewall. That was under system prefs Secuity and privacy/firewall then options. applefileserver was blocking connections as was networkbrowseragent. After changing to allow, I am not running correctly again.
I realise that this was not the post for this but it was the closest. I have added this as maybe this may help somebody.
I just remembered we also deleted the keychain password for the 10.8.2 machine on the other machine trying to connect to it, which forced it to ask for the password again.
Currently Being ModeratedMar 13, 2013 2:50 PM (in response to Ronohki)Try setting up another admin user account to see if the same problem continues. If Back-to-My Mac is selected in System Preferences, the Guest account will not work.
If the problem is still there, try booting into the Safe Mode. Shut down the computer and then power it back up. Immediately after hearing the startup chime, hold down the shift key and continue to hold it until the gray Apple icon and a progress bar appear. The boot up is significantly slower than normal.
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points