|
|
.Mac Back to Mac?
|
|
|
|
Fresh-Faced Recruit
Join Date: Mar 2005
Status:
Offline
|
|
Has anyone gotten this to work. I can not seem to figure it out. I am able to do the screen sharing when on one mac on a college network connecting to my laptop in my room. But I am unable to take one laptop off campus and connect back to my mac while out of the campus by using back to my mac. I can not even seem to get my laptop in my room to be under shared computers on my office laptop. Anyone have any insight to what Im doing wrong?
Thanks
|
|
|
|
|
|
|
|
|
Professional Poster
Join Date: Jun 2001
Location: Northwest Ohio
Status:
Offline
|
|
Originally Posted by soon2bmac
Has anyone gotten this to work. I can not seem to figure it out. I am able to do the screen sharing when on one mac on a college network connecting to my laptop in my room. But I am unable to take one laptop off campus and connect back to my mac while out of the campus by using back to my mac. I can not even seem to get my laptop in my room to be under shared computers on my office laptop. Anyone have any insight to what Im doing wrong?
Thanks
It may not be you doing anything wrong. It may be your university's network. They might be running a firewall that closes the ports that Back to my Mac relies on.
|
|
|
|
|
|
|
|
|
Professional Poster
Join Date: Jan 2002
Location: London, UK
Status:
Offline
|
|
Also, some routers are not compatible with the feature (such as my Netgear router).
|
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Jan 2003
Location: ~/
Status:
Offline
|
|
Yeah, I can't get it to work either from home to office. The firewall at my workplace however is freaking nuts. They block virtually everything. We have two networks - one internal running on both ethernet and wifi, and a public network for visitors running on wifi (separate SSID). On both networks - even the "public" network - the ONLY ports open to the internet are 80 (http) and 443 (https), and whatever ports are used by the encrypted Citrix server. I can't even check my email from work on my laptop since all POP3/SMTP and IMAP ports are blocked. Web mail only. Its freaking ridiculous.
Internal traffic such as the MS Exchange server, etc., don't get out of the building.
That's one of the few things I don't like about where I work - the IT department is super paranoid about everything. Even visitors (patients, families, students, etc.) can't check their email because the IT department fears that someone will send large volumes of spam from their network.
So no Back To My Mac from work for me. I haven't had a chance to try it from a hotel or a Starbucks or something yet.
|
|
|
|
|
|
|
|
|
Mac Elite
Join Date: Apr 2001
Location: Minneapolis, MN
Status:
Offline
|
|
I got it to work for a few days, nothing since December though. I think it's quite buggy.
|
|
|
|
|
|
|
|
|
Professional Poster
Join Date: Nov 2004
Location: eating kernel
Status:
Offline
|
|
Originally Posted by awaspaas
I got it to work for a few days, nothing since December though. I think it's quite buggy.
Same here, my home machines won't show up on my MacBook sense early December.
|
Signature depreciated.
|
|
|
|
|
|
|
|
Mac Elite
Join Date: Mar 2001
Location: Madison, WI
Status:
Offline
|
|
I've been unable to get this to work, though I only tried this month (i.e., using 10.5.1). I've tried all of Apple's suggestions about logging out and back into .Mac, etc. My router at home is set up to allow uPNP. My home Mac shows up in the Finder sidebar of my work Mac, but when I try to connect, it always times out and fails.
|
|
|
|
|
|
|
|
|
Junior Member
Join Date: Jun 2004
Location: Toronto
Status:
Offline
|
|
I've never been able to get it to work anywhere other than for two computers on the same network. Once I have to connect over the internet, it never works (other computer is never visible). This has been true at every other place I've tried it in (school, work, my mom's house). I have an Airport router so I know it's not the issue, which means that either a whole lot of routers must not work with it, or a whole lot of networks are set up to block those ports. Is it just my bad luck or is Back to My Mac going to end up being a kind of vapourware feature that only a few lucky people will be able to use?
|
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Jan 2003
Location: ~/
Status:
Offline
|
|
Originally Posted by ooninay
...or is Back to My Mac going to end up being a kind of vapourware feature that only a few lucky people will be able to use?
Yep. Because in Steve Jobs' world, everyone runs an open wireless network and no one runs a firewall.
|
|
|
|
|
|
|
|
|
Senior User
Join Date: Mar 2002
Location: between a rock and a casbah...
Status:
Offline
|
|
This works for me "sometimes". And "sometimes" is as random as being able to establish a remote connection in the morning but not after lunch; or vice versa. It's really odd. When it does work, it's very impressive, really useful and a guaranteed crowd-pleaser/sales tool. However, it's so flaky that I've given up using it as "wow factor" when demo-ing Apple kit for sale. It's very embarrassing -- both for me and for Apple -- when it doesn't work as advertised and sadly at the present time I have no way of knowing if/when it will connect successfully or if I will even be able to "see" my home G5 Powermac from my MBP. As a networking pro, I am aware that in certain situations a successful connection is dependent on individual router/firewall configurations but if I can configure Apple Remote Desktop to find my home computer in London (on a static IP) without any difficulty from a hotel room in Hong Kong, then surely it can't be that complicated for Apple to use the .Mac "reflection point" effectively.
|
|
|
|
|
|
|
|
|
Clinically Insane
Join Date: Mar 2001
Location: yes
Status:
Offline
|
|
Originally Posted by Cadaver
Yeah, I can't get it to work either from home to office. The firewall at my workplace however is freaking nuts. They block virtually everything. We have two networks - one internal running on both ethernet and wifi, and a public network for visitors running on wifi (separate SSID). On both networks - even the "public" network - the ONLY ports open to the internet are 80 (http) and 443 (https), and whatever ports are used by the encrypted Citrix server. I can't even check my email from work on my laptop since all POP3/SMTP and IMAP ports are blocked. Web mail only. Its freaking ridiculous.
Internal traffic such as the MS Exchange server, etc., don't get out of the building.
That's one of the few things I don't like about where I work - the IT department is super paranoid about everything. Even visitors (patients, families, students, etc.) can't check their email because the IT department fears that someone will send large volumes of spam from their network.
So no Back To My Mac from work for me. I haven't had a chance to try it from a hotel or a Starbucks or something yet.
Would telling your IT department that somebody could send large amounts of spam on port 80 or 443 help affect anything in your favor?
The best way to combat stuff like that is by being aware of every machine in your network so you can trace stuff like this, but simply trusting that attacks will occur on their proper ports is by no means bulletproof security.
|
|
|
|
|
|
|
|
|
Clinically Insane
Join Date: Mar 2001
Location: yes
Status:
Offline
|
|
My understanding of Back to my Mac is that it is simply a dyndns service that also allows for Kerberos based authentication that doesn't require entering a password for services that require authentication (i.e. file sharing services). Perhaps this is why Kerberos now seems to be a standard open port on Leopard installs...
If you can live with typing your password each time you authenticate to your home Mac for file sharing, you can set this up by creating yourself a dyndns account (which are free), entering your dyndns account info in your router admin settings (assuming your router, like most, support dyndns), setting up port forwarding on your router admin, and connecting to this address. Of course, wherever you are connecting from should support outbound traffic on the port needed by the service you are connecting to.
If you are having a hard time getting an IT person to open up the AFP port (548, I believe), you might see if the SSH port is open. If not, you could probably make a better case for opening this up. With this open, you can make connections to your home Mac via MacFUSE/sshfs. Download MacFusion if you want a GUI for connecting to SSHfs shares.
|
|
|
|
|
|
|
|
|
Forum Regular
Join Date: Dec 2003
Location: Manhattan Beach, CA
Status:
Offline
|
|
Originally Posted by besson3c
If you are having a hard time getting an IT person to open up the AFP port (548, I believe), you might see if the SSH port is open. If not, you could probably make a better case for opening this up. With this open, you can make connections to your home Mac via MacFUSE/sshfs. Download MacFusion if you want a GUI for connecting to SSHfs shares.
Have you tested MacFusion with Leopard and the latest version of MacFuse?
|
MBP 15" 2.4 Ghz 4Gb
MBA 13" 1.6 Ghz 2Gb
|
|
|
|
|
|
|
|
Clinically Insane
Join Date: Mar 2001
Location: yes
Status:
Offline
|
|
I use MacFUSE all the time, but I don't use MacFusion, I have my own connection scripts... MacFUSE itself works just fine under Leopard.
|
|
|
|
|
|
|
|
|
Professional Poster
Join Date: Jun 2001
Location: Northwest Ohio
Status:
Offline
|
|
Originally Posted by besson3c
My understanding of Back to my Mac is that it is simply a dyndns service that also allows for Kerberos based authentication that doesn't require entering a password for services that require authentication (i.e. file sharing services). Perhaps this is why Kerberos now seems to be a standard open port on Leopard installs...
Perhaps to make Back to My Mac more useful Apple should try to implement it over an SSH tunnel or have it try multiple ports that are likely to be open on numerous firewalls?
|
|
|
|
|
|
|
|
|
Clinically Insane
Join Date: Mar 2001
Location: yes
Status:
Offline
|
|
Originally Posted by Person Man
Perhaps to make Back to My Mac more useful Apple should try to implement it over an SSH tunnel or have it try multiple ports that are likely to be open on numerous firewalls?
Well, I think it would be more accurate to say that they should try skipping Kerberos auth, because I think this is where many problems are occurring. Without port 88 open, this doesn't work, yet this is sort of icing.
The only way I can think of getting your SSH tunnel idea to work is converting AFP requests to rsync requests, as rsync supports OS X metadata, and network share browsing with SSHfs. Just thinking out loud.
(
Last edited by besson3c; Jan 13, 2008 at 01:42 PM.
)
|
|
|
|
|
|
|
|
|
Junior Member
Join Date: Jun 2004
Location: Toronto
Status:
Offline
|
|
I don't know much of anything about ports and what protocols use which ports, but FolderShare is a file-syncing app that works over the internet and doesn't have any problems working with Macs. I wonder if any of its techniques could be used in Back to my Mac?
|
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Jan 2003
Location: ~/
Status:
Offline
|
|
Originally Posted by besson3c
If you are having a hard time getting an IT person to open up the AFP port (548, I believe), you might see if the SSH port is open. If not, you could probably make a better case for opening this up. With this open, you can make connections to your home Mac via MacFUSE/sshfs. Download MacFusion if you want a GUI for connecting to SSHfs shares.
With over 10,000 employees, there's a near-zero chance of the IS department capitulating to the firewall requests of a handful of Mac users. Plus, since only authorized devices are allowed on their ethernet network or internal wireless (and I don't know the password), there is absolutely no way they'll open the ports necessary to make it work. There are several internal applications that would benefit hundreds more than a few Mac-specific changes, and we still can't get it approved.
(and yeah, our IT folks - most of them anyway - couldn't care less about making life easy for anyone so long as the network is "secure", and the ones that do care are in no position of power to do anything about it)
|
|
|
|
|
|
|
|
|
Dedicated MacNNer
Join Date: Apr 2002
Location: In your blind spot.
Status:
Offline
|
|
It doesn't matter if I am using B2MM or ARD, I can't copy files to another computer since the 10.5 install. I am able to see the desktop and run functions remotely, but can't access any files or share.
grrrrrrrr Apple!!!!
|
W....liar or idiot? Pick two.
|
|
|
|
|
|
|
|
Dedicated MacNNer
Join Date: Jun 2004
Status:
Offline
|
|
Hey, guys... I recently bought a MacBook, and I'm enjoying using Back to my Mac to access my Mac Pro. Lately, however, my B2mM computers have failed to show up in the Finder sidebar, and three quarters of the time, Leopard shows the wrong icon for the respective computers (i.e. - shows an ACD icon for the MB). Any clue if B2mM will be made more stable with 10.5.2? Also, I haven't read about anyone else experiencing the changing icons. Am I the only one who's seen this? Thanks, guys!
Rob
|
|
|
|
|
|
|
|
|
Addicted to MacNN
Join Date: Jan 2003
Location: ~/
Status:
Offline
|
|
^^ The icon "issue" isn't really an issue. It uses an ACD icon for any/every Mac, and a beige CRT with a BSOD for each PC.
|
|
|
|
|
|
|
|
|
Senior User
Join Date: Mar 2002
Location: between a rock and a casbah...
Status:
Offline
|
|
Originally Posted by Cadaver
^^ The icon "issue" isn't really an issue. It uses an ACD icon for any/every Mac, and a beige CRT with a BSOD for each PC.
Errrr...not quite so. I have a MacPro. On the rare occasions Back to my Mac works for me, the icon displayed is of a MacPro box.
|
|
|
|
|
|
|
|
|
Professional Poster
Join Date: Jan 2002
Location: London, UK
Status:
Offline
|
|
Originally Posted by stoneage
It doesn't matter if I am using B2MM or ARD, I can't copy files to another computer since the 10.5 install. I am able to see the desktop and run functions remotely, but can't access any files or share.
grrrrrrrr Apple!!!!
Have you checked the advanced options to make sure you have the permissions to do this?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Forum Rules
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|