Q: file sharing 10.8.2 not working

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.

Same thing - 10.8.2 machine won't connect.

Same here, very fustrating

Same problem but the 10.8.2 can connect to the 10.6.8 and not the other way around.  Come on Apple get it sorted please, a bug this basic should not be occurring.

Yes, same problem for me too.  Can see my 10.7 machine from my 10.8.2, but cannot establish a connection.

Maybe the Apple document Connecting to legacy AFP services might help.

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

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...

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.

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.

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.

I have the opposite problem. I have a mchimne running 10.8.2 that can connect to my other computers but  from any of the others I can't connectto the 10.8.2.

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.