What Port Do I Use For Screens App Mac OS X But

I just went with it and decided to find out if and when the IP changed.

But to control your computer over an internet connection is easy, too.

Be sure to use a local port other than 5900 -- otherwise the screen sharing app will complain about controlling the local screen is not possible.

If the tunnel is established and you click the generated link, the screen sharing app will start and show your remote computer.

I have this situation -- I can only get through port 22 to my machine at the office, not port 5900.

The tunnel allows me to do remote screen sharing with this machine (which, if anyone is concerned, is just fine with my workplaces IT people).

Getting around firewalls in a secure manner is just as (and probably more) important.

I have port 22 forwarded to the host that I would like to tunnel to, the command does not work, also shouldent the s be:s.

In order to create an SSH tunnel, youd use a command similar to the following: ssh -L 1202:localhost:5900 remote-host This would listen locally on port 1202, tunnel to remote-host and then have remote-host redirect that traffic to localhost on port 5900.

You can also replace localhost with a different box that remote-host has access to, perhaps if you wanted to tunnel through that box to another box on its network.

In any case the original proposed method (not using localhost) create a secure tunnel: From man ssh: -L bindaddress:port:host:hostport Specifies that the given port on the local (client) host is to be forwarded to the given host and port on the remote side.

This works by allocat- ing a socket to listen to port on the local side, optionally bound to the specified bindaddress.

Whenever a connection is made to this port, the connection is forwarded over the secure channel, and a connection is made to host port hostport from the remote machine.

However, the:host: (i.e.

What Port Do I Use For Screens App Mac OS X But

I think iChat is one of the weakest components of Mac OS X but I digress.

It takes all packets destined for port 1202 on the server machine and forwards them to port 5900.

With this setup, though, you wont be sending any packets to port 1202 on the server side -- theyre going to port 1202 on the client side, and the first ssh command takes care of the necessary forwarding.

The key is that the sleep 10 will cause the shell channel of the ssh connection to drop after 10 seconds, giving the local side 10 seconds to open the vnc connection.

The SSH connection will automatically drop when you close the VNC connection.

Mac 2 is on a home network behind a Westell router, and Mac 1 is on the internet.

I am using DynDNS to get the routers ip address, and I have enabled screen sharing on both Macs.

I understand that I need to forward port 5900 from the router to Mac 2 -- but the router apparently needs to know the ip address of Mac 2.

Is there a way to forward the port without assigning Mac 2 a static ip address I believe that assigning Mac 2 a static ip address will cause it to not work if it moves to a different network that uses different ip ranges, right Thanks.

My old router kept track of NAT by MAC address, which make much more sense.