Notices


Reply
Thread Tools
Posts: 145 | Thanked: 304 times | Joined on Jan 2010 @ Milton Keynes, UK
#21
the logs just show connection attempt. success and disconnect. tryed it through a different router (although same brand) and a different broadband connection. same result =(
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#22
Can you try (on the desktop) running (at a command prompt) "telnet 127.0.0.1 5900" to check that you can actually connect to the VNC server. You should get a "RFB 003.008" (or something like that.
 
Posts: 254 | Thanked: 17 times | Joined on Dec 2009
#23
Originally Posted by Rob1n View Post
Okay, here's the instructions for setting up SSH tunnelling - let me know if anything's unclear.

SSH configuration for VNC

Data used (substitute your own values for these where used):
Dynamic DNS name for PC: pc.dyndns.org
SSH user login: fred
SSH port: 522
On the router:
Ensure port 522 is allowed, and is forwarded to the PC.
On the N900:
From X Terminal, run "ssh-keygen -b 2048 -t rsa" to generate a public/private key pair. Choose a pass phrase - this will be required every time you connect (you can leave it blank, but I'd advise against this).
On the PC:
Download and install freeSSHd (http://www.freesshd.com/), setting it to run as a system service.
Double-click on the icon in the system tray.
Edit the settings:
Telnet: Disable starting server at startup.
SSH: Enable starting server at startup. Change the port to 522 to reduce random attacks (any other non-standard port will do).
Authentication: Set password authentication to disabled and public key authentication to required.
Tunneling: Allow local port forwarding, only to localhost. Disable remote port forwarding.
Users: Add a new user fred (any name will do), set authorization to Public key, and enable Shell and Tunneling.
Click OK to close the freeSSHd settings window.
Copy and rename the public key from the N900 (/home/user/.ssh/id_rsa.pub) to C:\Program Files\freeSSHd\fred on the PC (the same name as you used for the user you created earlier, with no file extension).
On the N900:
Create a configuration file /home/user/.ssh/config (to simplify the connection strings):
Host pc.dyndns.org
IdentitiesOnly yes
PasswordAuthentication no
User fred
Port 522
LocalForward localhost:5900 127.0.0.1:5900
The tunnel should now be configured. You can start the tunnel from X Terminal by running "ssh pc.dyndns.org". You should be prompted for the pass phrase, then presented with the C:\ prompt. You can now run the VNC client, connecting to "127.0.0.1:0". To shut down the tunnel, simply type "exit" at the C:\ prompt.
couple of questions:

--Frm whre to get to ssh config for VNC?
--thn when on n900 i run ssh-keygen....it says...ssh-keygen not found?

clear these questions please so that i can proceed further....
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#24
Originally Posted by somekeystrokes View Post
couple of questions:

--Frm whre to get to ssh config for VNC?
--thn when on n900 i run ssh-keygen....it says...ssh-keygen not found?

clear these questions please so that i can proceed further....
You need to install the openssh-client package to get ssh-keygen. Not sure what you mean by "ssh config for VNC" though - there's nothing special needed, just the openssh-client and the VNC viewer on the N900, and freeSSHd and a VNC server on the PC.
 
Posts: 145 | Thanked: 304 times | Joined on Jan 2010 @ Milton Keynes, UK
#25
Originally Posted by Rob1n View Post
Can you try (on the desktop) running (at a command prompt) "telnet 127.0.0.1 5900" to check that you can actually connect to the VNC server. You should get a "RFB 003.008" (or something like that.
Hi Rob1n,

Tested that this morning, I get that exact message. I also tried to connect to the VNC server using another PC on the network and that worked too, so I can control it via local network just not through the tunnel.

VNC also works fine on the N900 as I use to remote control a different PC (local network, no tunnel)

I'm guessing this is gonna be some kind of bug or glitch, I've tried all the workarounds I found on google, (which basically consisted of rm the known_hosts file.) I just had a quick look and it may be afault with my router... the netgear DG834G seems to have problems with ssh, and streaming videos...time for a different brand router I think.
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#26
Originally Posted by jamiefuller View Post
I'm guessing this is gonna be some kind of bug or glitch, I've tried all the workarounds I found on google, (which basically consisted of rm the known_hosts file.) I just had a quick look and it may be afault with my router... the netgear DG834G seems to have problems with ssh, and streaming videos...time for a different brand router I think.
Could well be. Can you try using the N900 to connect to it via ssh on the local network? You'll need to edit the ssh config file on the N900 to create a duplicate section for the new host name (using the internal name/IP address). The rest of the process should be the same though.
 
Posts: 145 | Thanked: 304 times | Joined on Jan 2010 @ Milton Keynes, UK
#27
I cannot access the local network with my N900 as it is a purely wired network. no Wifi is allowed. Only entry point is the network firewall attached to a leased-line, and to access that i'm going out through a seperate ADSL connection though the netgear router.

I have tried upgrading, downgrading and even installing custom firmware for my ADSL router but no luck still.
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#28
Originally Posted by jamiefuller View Post
I cannot access the local network with my N900 as it is a purely wired network. no Wifi is allowed. Only entry point is the network firewall attached to a leased-line, and to access that i'm going out through a seperate ADSL connection though the netgear router.

I have tried upgrading, downgrading and even installing custom firmware for my ADSL router but no luck still.
The only other thing I can suggest then is installing the openssh client (http://sshwindows.sourceforge.net/) on another PC on the network, with the same private key (/home/user/.ssh/id_rsa) and config as you have on the N900 and seeing whether that works over the local LAN. That'll at least rule out the server from the equation.
 
Posts: 254 | Thanked: 17 times | Joined on Dec 2009
#29
Originally Posted by Rob1n View Post
Okay, here's the instructions for setting up SSH tunnelling - let me know if anything's unclear.

SSH configuration for VNC

Applications required on N900:
vncviewer
OpenSSH Client
Data used (substitute your own values for these where used):
Dynamic DNS name for PC: pc.dyndns.org
SSH user login: fred
SSH port: 522
whre are these settings to be set....i dnt see any applocation in my menu even after installing openssh client on my phone??
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#30
Originally Posted by somekeystrokes View Post
whre are these settings to be set....i dnt see any applocation in my menu even after installing openssh client on my phone??
Those aren't set anywhere as such - those are just the values I've used in the instructions. Where you read those values, you can instead substitute your own. The "Dynamic DNS name for PC" is the DNS name you choose when registering at www.dyndns.com to set up your PC for dynamic DNS services. The "SSH user login" is the login you create in freeSSHd (documented later on), and the "SSH port" is the port you choose to set freeSSHd to listen on (and your router to forward to your PC).
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 14:14.