Notices


Reply
Thread Tools
Posts: 42 | Thanked: 1 time | Joined on Dec 2009 @ Finland
#101
Originally Posted by Rob1n View Post
Interesting - it works fine here with that enabled. Which version of Windows are you running?
Windows 7 Professional 64bit. Could it be that I have some weird version of freeSSHd installed?
 
Posts: 42 | Thanked: 1 time | Joined on Dec 2009 @ Finland
#102
Well how about it, I got VNC working and it only took 4 hours


Thanks a lot for your help, I'd still be figuring this out next week if you hadn't helped.
 
Posts: 553 | Thanked: 1,704 times | Joined on Jan 2010 @ NYC
#103
Hey Rob1n,

Just want to thank you for you hard work helping ppl with there ssh/vnc troubles! Though you didn't help me directly, some of your post were helpful along with my searches around the web.

I currently have my n900 ssh into a home machine with passphrase key use with no local login required expect vnc of course. Now I still trying to make it faster through compress or any other means. Of it would probably help to move vnc server to a faster machine and clean up the desktop of too many files.

But if you have any nice little secrets to speed up ssh/vnc over dsl, please chime in.

x
 

The Following User Says Thank You to xman For This Useful Post:
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#104
Originally Posted by xman View Post
But if you have any nice little secrets to speed up ssh/vnc over dsl, please chime in.
You could try enabling ssh compression (use the -C option on the command line, or add "Compression yes" to the config file), though VNC should be compressing the data anyway. If your server is on a Windows PC then you could also try using a VNC server which supports a mirror driver (TightVNC, Ultr@VNC, Real VNC Personal/Enterprise), if you're not already using one.
 

The Following 2 Users Say Thank You to Rob1n For This Useful Post:
Posts: 553 | Thanked: 1,704 times | Joined on Jan 2010 @ NYC
#105
Yeah, been using the -C. I guess I was hoping for a more substantial difference ... .

Right now I'm using an older os x machine, that need optimizing and more testing. But isn't tightvnc cross-platform? I could put on a linux install. Anyway, thanks for trying.

x
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#106
Originally Posted by xman View Post
Yeah, been using the -C. I guess I was hoping for a more substantial difference ... .

Right now I'm using an older os x machine, that need optimizing and more testing. But isn't tightvnc cross-platform? I could put on a linux install. Anyway, thanks for trying.
OS X won't need a mirror driver anyway - those are only for Windows. There were some compatibility issues with the VNC server built into OS X though, so you may want to try the Vine server instead (I've never used OS X myself, but this is what I've heard).
 
Posts: 10 | Thanked: 0 times | Joined on Feb 2010 @ Dublin, Ireland
#107
After many hours of reading through these posts I finally got the SSH working but the VNC Viewer is not


The tunnel should now be configured. You can start the tunnel from X Terminal by running "ssh pc.dyndns.org".

Working


You should be prompted for the pass phrase, then presented with the C:\ prompt.

Working I can see the C Drive on my PC


You can now run the VNC client, connecting to "127.0.0.1:0".

Not Working.
Error message says "Cannot Connect to Server". Checked the config file and it is correct.

Could be 2 problems
Port Forwarding Settings - Are these correct?
Service Name *VNC
Protocol TCP
Global Port Range 522 - 522
Base Host Port 21
and / or

FreeSSHd (SSH Server is not running) no longer allows me to connect to Port 522 "The specified address is no longer in use" - but I downloaded TCPView and no other resources are using 522.

Grr...I feel that I'm really close to getting this to finally work

Last edited by pacmanster; 2010-02-25 at 16:52.
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#108
Originally Posted by pacmanster View Post
Could be 2 problems
Port Forwarding Settings - Are these correct?
Service Name *VNC
Protocol TCP
Global Port Range 522 - 522
Base Host Port 21
The port forwarding must be okay - we're only using that for SSH. The VNC connection is made "inside" the SSH connection.

Originally Posted by pacmanster View Post
FreeSSHd (SSH Server is not running) no longer allows me to connect to Port 522 "The specified address is no longer in use" - but I downloaded TCPView and no other resources are using 522.

Grr...I feel that I'm really close to getting this to finally work
No idea why you're getting that now - it was obviously working okay earlier. If you're using TCPView, make sure you enable viewing listening ports (I think it defaults to showing only connected ports).

If you're using RealVNC Enterprise/Personal editions, then make sure that encryption is set to "prefer on". Also check whether the VNC server has a separate option to enable loopback connections (the TightVNC installed here does).
 
Posts: 553 | Thanked: 1,704 times | Joined on Jan 2010 @ NYC
#109
Originally Posted by Rob1n View Post
OS X won't need a mirror driver anyway - those are only for Windows. There were some compatibility issues with the VNC server built into OS X though, so you may want to try the Vine server instead (I've never used OS X myself, but this is what I've heard).
You are correct. I've experimented with built 10.4 vnc, Real vnc server (PE) and Vine Server (OSXvnc) and so far I think the vine works the best and the built in was very slow updating the images or just problematic. Funtimes


And just a fyi pacmanster, I didn't need to use 127.0.0.1:0 for the viewer just 127.0.0.1. I'm no expert, but it was the last piece to my puzzle.

cheers

x
 
Posts: 10 | Thanked: 0 times | Joined on Feb 2010 @ Dublin, Ireland
#110
Previously I was using via my wifi to get onto my C: Drive on laptop.

Decided to start from scratch uninstalled and reinstalled everything - bad mistake.Generated new keys, copied and pasted output from .pub file into freeSHd. The SSH now doesn't like my password

debug1: PEM_read_PrivateKey failed
debug1: read PEM private key done: type <unknown>
Enter passphrase for key '/home/user/.ssh/id_rsa':
debug1: read PEM private key done: type RSA
debug1: Authentications that can continue: publickey
debug1: Trying private key: /home/user/.ssh/id_dsa
debug2: we did not send a packet, disable method
debug1: No more authentication methods to try.
Permission denied (publickey).

The dsa doesn't look right I thought that it should read rsa??
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 04:16.