I'm unable to ssh into my machine remotely. If i try internally (192.168.0.105) it works just fine. If I unplug the cable from my linksys box and put it directly into the box, it works just fine. So it looks like linksys is not forwarding port 22 to the box, but I did set up a forwarding rule so it should work (windows port forwards like VNC work just fine). Any thoughts?

Are you sure you are forwarding TCP 22? It could also be possible that your ISP may not allow TCP 22 traffic to traverse its network.

It is forwarded TCP 22. If I disconnect my Comcast connection from the linksys router and plug it directly into the ubuntu box everything works perfectly. That's a great temp fix while i'm working on that one box remotely, but I'm going to need to add more things onto the network at some point.

Does the linksys have a firewall rule for exactly ssh already that could be selected as allow instead of the port forward external to internal? To prove for sure it is the linksys I guess you could also dmz it for a short test just in case of some other oddity. Not sure you'd need to but recheck the port forwarding. I read it wrong and answer it wrong too. So get off my case you goober.

I've done this on my firewall which isn't a linksys but all SOHO type "routers" basically work the same. You have to setup your forward to send the ssh port 22 to the internal IP of the PC you wish to connect to. I have several Linux boxes and two UNIX boxes at home. My OpenBSD box is my router/firewall which resides behind the SOHO one provided by my ISP (Combo modem/router/wireless AP unit). The SOHO router connects directly to the OpenBSD router/firewall which then in turn connects to my Cisco switch and the rest of the LAN. The forward I setup on the SOHO unit is for port 22. It points to my OpenBSD box via it's IP address (ie: forward port 22 tcp/udp to IP address xxx.xxx.xxx.xxx). Once I've connected and logged in, I can then ssh to any other Linux/UNIX PC in my home office. I suggest you double check your forward. If nothing appears to be wrong with it, delete it and try redoing it over. You may have made a simple mistake setting it up.