epoch1970;433089 Wrote: > Perhaps this is a matter of UDP vs TCP as the transport, and UDP being > blocked by the router ? > ssh would definitely help in that case. On your router, undo the > current port forwardings and add a new one, for the ssh server on the SC > server host (default: listen on 22/TCP) to respond on, say, 443/TCP. > Then something like: > ssh -p 443 -L 9000:SC_server_lan_ip:9000 -L 3483:SC_server_lan_ip:3483 > -N -C lo...@sc_server_public_ip > > should work. > > I'm not so sure you really need 3483. Discovery is chatty, maybe you > can do without it? > > HTH
I am a little confused. I have ssh working on the SC_server. I have my home router forwarding port 22 to the SC_server computer. Port 22 is open at my work. So on my work computer I can type "ssh myu...@sc_server_public_ip" and I can successfully log on to the SC_server computer. So in the command you gave, I wouldn't need the -p 443 right? That would just be if 22 was blocked at my work and I was having to use 443..right? Also, since SoftSqueeze supports tunneling, do I have to type any SSH command on the work computer at all? Shouldn't I just be able to put in my SSH username and password in SoftSqueeze and everything work? Or do I have to do something special on the SC_server computer to get the tunnel to work? Thanks. -- lemmy999 ------------------------------------------------------------------------ lemmy999's Profile: http://forums.slimdevices.com/member.php?userid=9284 View this thread: http://forums.slimdevices.com/showthread.php?t=64593 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/discuss
