Anybody with iMac here. Trying to set up some file sharing. I have everything enabled on iMac (ssh, ftp, smb) and I can connect to it from n800 sitting on the same local network. However I need to set up access from the www to my public IP. Was told to open the appropriate ports (21, 22) on my router (verizon) which I did. The ports test open now when tested from the web (open port check). However ftp or ssh from n800 to my public IP says connection refused. This is sort of confirmed by Port Scan Utility on mac whci shows everything open on my local ip but only 23,80,1111 and 8080 on external IP. Any suggestions?

Can you do normal SSH into your mac and the tablet? Try that first. Also, your router might be in "stealth" mode. It sees if a local computer (iMac) is listening to a port, and only then opens it. I hate stealth mode. For example, my computer has "Intel Active Management", which is a thingy that runs when the computer is turned off or on. It can remotely monitor and switch on your computer. BUT, because it is very passive, the stupid router blocks the ports!!

What's normal what's not? Again I can both ssh and ftp to my mac from the tablet that sits on the same router. But unable to connect to my mac on its external IP. I have stealth mode disabled on my iMac. Router I don't know.

Do you have port forwarding enabled on the router? quite often you have to tell the router who it should send the data to if it gets a call on a port.

EG any calls to port 22 get fowarded to IP 192.168.2.4

Just a thought.

What Rassilon7 said. However I have had problems with my belkin router working with forwarding SSH.

Problem solved, for those interested my problem was I was testing access to my server from my local network using that network's WAN IP, and that for same strange reason is a no go. Local access on local IP always works w/o a hitch as I said in my first posting. And so does access using external IP as long as this is not invoked from any computer sitting on the same network as the server.

Ofcourse that doesn't work. You connect to your WAN IP from an internal LAN interface. This way no port forwarding happening on the external WAN interface gets triggered. It shouldn't pass the external WAN interface because its an internal LAN packet not going to the Internet, and if it does pass the interface, it does so outgoing, not incoming. You can fix this with some additional firewall rules provided its worth the hassle.

Almost every computer supports WOL (Wake On Lan) provided its turned on in the bootable EEPROM, and the LAN card supports this. Which is both the case for computers & LAN cards of past ~10 years. No need to put suspend to RAM or suspend to disk (hibernate) off; there are useful features, good for your bills.