afp and ftp
 

HHMM not getting this, theoretically I should be able to login to my mac from another computer using afp. I can access it on my local network using afp by typing in my local address. I'm assuming that in order to access it from outside my local network I need to use my IP address but when I try that it fails with the following message.
the finder cannot complete the operation because some data in
afp:// 90.207.97.28 could not be read or written ( error code -36 )
end message
All 'sharing ' permissions have been set to allow access, file sharing is enabled as is appletalk on both macs so what am I missing?

Is your router set up to port forward?

good of you to reply, I just went in to my router and set up port forwarding for TCP/UDP. It recomended I use the default ip address 192.168 etc. Can't see how that will work though as it's my local network address, everyone's router has that default address is that not so?
Peter

AFP is not a routable protocol. You cannot use that except in an intranet situation. So, this is not a case where port forwarding can be the issue. You need to use TCP/IP to make the connection instead of AFP.

Joe VanZandt

OK now I'm clearly up the wrong tree. Another anomoly is that my IP address as reported by a number of servers is different from the one which my router describes. They both begin 90.209. and then they differ. So assuming I work out which way to remotely login to my mac which address should I be using?
And not forgetting. Can you tell me how I do this using TCP/IP

Apple Remote Desktop will do what you want (or other VNC-type setups). Now, not knowing your exact network topography, it's sort of odd that you'd be getting different routable IPs for your machine, but it is possible if your organization has a block of IPs assigned to it that DHCP is assigning a different one when you start up. This is a bit unusual in the business world; less so in educational institutions. As far as I know, 90.209.xxx.xxx ought to be routable IPs. If you have a network administrator that sets up DHCP for you, he or she can set it so you always receive the same IP (based on the MAC address of your machine) and that would simplify the matter a bit. If that isn't relevant to your situation, then I'm a bit puzzled about why you would be getting a different IP. Maybe someone else can think of a better explanation.

Joe VanZandt

well there's no organization involved. I run a small business with 5 macs in my studio. I have complete control over all permissions, access etc and all macs talk flawlessly over remote desktop, afp etc. I occasionally need to send large files to a colleague in another part of the country and I need to set up a mac so he can access the 'public' folder, nothing more complicated than that. The different ip adresses is curious to me as well, I'm stumped. But I'll try remote access

I thought that AFP was wrapped in IP.

Are the other servers not on your LAN?

Anyway, you can use Cyberduck or some other sftp capable software on the other end if you turn on remote login. I'd limit the account used for this purpose!

already have cyberduck, just tried to access the other mac using it and it fails to connect. The entire online world can access my 'shared'folder using Limewire, Bitorrent etc successfully and yet I cannot not enable what should be a simple ftp connection?

You need to open an sftp connection to the WAN address of the router and the router needs to be set up to port forward to the computer you're trying to reach.

I feel a sore head coming on. I'll plod away at that tomorrow, head's fried now, thanks.
peter

might be getting somewhere, am getting this message upon attempting ssh through terminal
ssh: connect to host 90.206.79.48 port 22: Connection refused
[Process exited - exit code 255]

so something's happening, any ideas?

Yes, this one:

Thanks for responding.
earlier this morning I have set up both routers to accept ALL incoming traffic, ( port forwarding ) I thought that would do it.
Just noticed today that my own router is giving me a different ip address from yesterday, I didn't just mistake a digit or two, it's definitely a whole different address and when I check with external sources they are also giving me a different address from day to day. Assume that's a 'dynamic' address. I didn't set that up, wouldn't know how. It is going to screw with what i'm attempting to do though isn't it?
Peter

re 'port forwarding' just to be clear, the ip address which I want to allow ALL incoming traffic should be -what- 192.168.0.1 ( router address )
or 192.168.0.2 ( mac )

rooney -
I think you need to read some background on port forwarding to make sense of all this.
http://kbserver.netgear.com/kb_web_files/N101145.asp
http://en.wikipedia.org/wiki/Port_forwarding
http://support.apple.com/kb/TS1629

The "ports" we're talking about are the tcp/udp port(s) that a particular "service" on one computer listens and responds to. A service would be something like http server on port 80 or afp server on port 548. So, any request for afp (port 548) to your outside (internet) IP address would be forwarded to the local computer with that service, using its local IP address (Not the router's IP address).

Setting ALL to be forwarded would be like turning off the firewall completely -- so don't.

HTH

Will read and inwardly digest and attempt it again later, thank you all very much for taking the time.
Peter

OK lads all the pennies have dropped, but both macs have the same ISP and they are both getting a different ip address every day! So I was screwed to begin with!
Seems I have to get a static IP for each mac.
Peter

Not necessary:
http://www.dyndns.com/services/dns/dyndns/

Thanks for that, had a quick read, feel another sore head coming on.
Peter

It's simple. Really:
Set up a free account and you can create your own hostnames with your router's current ip address. The even provide software to update the address when it changes.

With that done, all that your client needs to know is the hostname to connect to your router. If you've set up port forwarding correctly, they'll connect to your Mac. Then if they have the correct username & password...

I'm sure you're right but there is a small avalanche of material to read with this and it's yet another day frizziled away creating nothing . Need a big glass or two of the Vin Rouge.
Thanks again
Peter

Read a little, then try it. If it doesn't work, read some more and try again. Either you can connect or you can't, but you're not going to break anything. ;)

Hopefully helpful information
 

I am about to set this up for my brother in law. My network is:

Internet-----Router-----Mac

OK, that's a bit simplified, but the key part is the router. I'm at home, and I have a dynamically assigned address (meaning, it changes). So as was said earlier, I have a service (EasyDNS in my case) that my router speaks to, so that anyone looking for my domain will end up at the correct IP address for my router (my router says to EasyDNS's servers "Hey, my IP changed, here it is" and EasyDNS's servers say to the Internet "Hey, if you want his domain, go to this IP address". Because computers use the IP address, not the name.)

So that takes care of the ever changing IP address on the outside. On the inside I have each computer set up with a "Static DHCP" address, which means the router looks at the MAC (or hardware) address that it sees at a low level, and says "OK, that one gets this IP address", say, 192.168.1.42. That takes care of the ever changing IP address on the inside.

Next, my router is set up that afp connections aren't blocked, but instead are forwarded ("Port forwarding") to my Macintosh. I have many machines inside, but the router sends them all to my Mac. I could allow anyone to come in on the ports, but I don't need the hassle (who knows, maybe malcontents would check, find that guest login was on, and fill up my hard drive with uggy stuff via the drop folder). Instead, I turn it on to a single computer only when I need it, then I block it again at the router.

Hopefully you are with me so far. And a bit of terminology: My router is more than a router, it is a firewall, and a switch, and a DHCP server, and a wireless access point. I think it makes a good single malt, too. I'm running "Tomato", an open source, highly recommended replacement for Buffalo's original firmware.
http://www.polarcloud.com/tomato/

Assuming you pretty much followed me, the only thing left is how to open up the firewall. The idea if you want to connect to an IP address for a certain service you have to contact that IP and say "I want web service" or "I want AFP". "Ports" are what does this. Ports 548 and 427 are what AFP uses (web service (http) uses port 80). So I set up the router such that anyone connecting to it on those ports gets to my (certain) Mac which then happily serves it up.

OK, I glossed over something that may be important to you. You want any Mac to be seen. What you need, then, is for every machine to be reachable from over the Internet, which means it has to have DNS.

Thanks, I've actually got the whole thing and I was getting it earlier but kept getting refused connection because I had a dynamic address and that confused me and I was convinced that i wasn't 'getting it '. My isp won't give me a static address.
Each mac has a manually assigned local ip address and I have been able to see my macs from outside my local network with Remote access but couldn't connect. The DNS service, suggested earlier looks like it would do the trick but I need to study it instead of poking around.
Peter