- This topic has 1 reply, 1 voice, and was last updated 16 years ago by
.
-
Posts
-
An OSX 10.3 Server was just replaced with a Mini running 10.6.3 Server. The new server was configured for AFP service and works fine for 10.5 & 10.6 clients on the LAN.
However, remote users who tunnel port 548 through SSH (client side port = 2222) cannot mount the same AFP share. They get the error:
Connection Failure
There was an error connecting to the server “localhost”. Check the server name or IP address, and then try again.NB: other tunneled ports work fine, such as 80, 5900, etc. Also, this used to work with the old 10.3 server. I’m using the same router/firewall and configuration.
I also noticed that after establishing the tunnel, even ‘telnet localhost 2222’ establishes a connection and then immediately closes it. The odd thing is that the server records no access or error entry at all!
Did something change in the way AFP serves in 10.6.3?
Is there another way to tunnel so as to avoid using ‘localhost’ in the Go to Server dialog? (I’m not using VPN for other reasons.)Thanks for any insights.
I think I solved my own problem. (Don’t you love that! 🙂
In my setup, the SSH server is on the same machine as the AFP share. So when creating the tunnel, instead of using:
ssh myname@serverWANaddr -L 2548:192.168.1.10:548
I need to use:
ssh myname@serverWANaddr -L 2548:127.0.0.1:548
Then, in the Finder, using -K allows me to connect to:
afp://localhost:2548
(It does take 15 seconds for the shares to load, but maybe something in the DNS resolution is causing that….)
- You must be logged in to reply to this topic.