Okay, I've tried following the discussion

http://talk.maemo.org/showthread.php...light=sidekick

And a couple other places but I'm missing something somewhere. I have my N900 on the T-mobile sidekick plan and I know that it is working because I can connect to m.yahoo.com while connected with it.

I have a SSH server setup on another remote machine and I have tried running it on a bunch of different ports from the lists that I have found and I can't seem to get any to connect. I'm not even to the point of trying to forward traffic over it I just wanted to make sure it would connect first.

I know the server is listening on the correct port because I verify that it works by connecting to it with my wifi connection. I then switch to T-mobile connection and try to ssh to that server on the same port (my last test was 143) and I'm getting no go.

ssh -p 143 ip.add.#.#

Is there something I'm missing or am I just in an unfortunate place where everything is blocked?

Thanks

Try adding -vv (one or more v's for more verbose output) and see if there are any clues on the output.

Have you set up port-forwarding on your router, or is your server in a DMZ?

/home/user # ssh 1.1.1.1 -p143 -vv
OpenSSH_5.1p1 Debian-6.maemo5, OpenSSL 0.9.8g 19 Oct 2007
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug2: ssh_connect: needpriv 0
debug1: Connecting to 1.1.1.1 [1.1.1.1] port 143.
debug1: Connection established.
debug1: permanently_set_uid: 0/0
debug1: identity file /root/.ssh/identity type -1
debug1: identity file /root/.ssh/id_rsa type -1
debug1: identity file /root/.ssh/id_dsa type -1

And thats where it dies. Also, I turned off the sshd on remote server and tried connecting while on T-mobile and got same spot so seems ot be saying it connected no matter what. Again goes through fine once I connect to my wifi connection.

Codemonkey - outside server and no prob on wifi so not issue there only when on t-mobile

Thanks