If you're like me, you had been hoping Apple's release of Mac OS X 10.5.2 would fix the problems with Back to My Mac. However, this does not appear to be the case. Many people are still having problems with this (potentially) very useful feature.
It looks like Apple needlessly tied the secure remote access features of Back to My Mac to .Mac. While I understand their desire to avoid forcing users to deal with DNS resolution or DHCP-based IP address issues, I think they would have benefited from working with existing solutions and methods. In short, I think they should enable Back to My Mac to function via DynDNS (and other dynamic DNS providers) and from a straight IP address (dynamic or static).
While I can open ports in my firewall for static NAT translations to enable VNC, AFP, and SSH, it seems to me Apple missed an opportunity to provide their trademark elegant UI to solve everyday users' VPN needs. As a Mac owner, I have come to expect elegant solutions to my problems. Rather than relying solely on poorly implemented standards like UPnP and NAT-PMP, Apple should have also allowed for some form of manual configuration
Console Messages
dns-sd
2008-03-02
blog comments powered by Disqus
Subscribe to:
Post Comments (Atom)