Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 1 day, 1 hr ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 1 day, 3 hrs ago -
Maemo repository (3)
to Community by torsen - 1 day, 18 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 2 days, 16 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 3 days, 22 hrs ago - more...
|
2012-01-04
, 00:02
|
|
Posts: 136 |
Thanked: 14 times |
Joined on Feb 2011
|
#2
|
I can ping to router's External ip address just fine, no RTO,
so the problem must be on the port forward
Last edited by shuraizo; 2012-01-04 at 00:17.
so the problem must be on the port forward
Last edited by shuraizo; 2012-01-04 at 00:17.
 |
|
2012-01-04
, 01:06
|
|
Posts: 106 |
Thanked: 81 times |
Joined on Dec 2011
@ /
|
#3
|
Is it working when you connect local on the home pc?
With "telnet ip-adress 5800" you can test if portforwarding of port 5800 to vncserver works from outside.
edit:
Just saw you have a wrt54g, a very nice router. But not with the original Firmware.
I would suggest to flash it to dd-wrt when you have some spare time, to unleash the power.
Last edited by eight; 2012-01-04 at 01:16.
With "telnet ip-adress 5800" you can test if portforwarding of port 5800 to vncserver works from outside.
edit:
Just saw you have a wrt54g, a very nice router. But not with the original Firmware.
I would suggest to flash it to dd-wrt when you have some spare time, to unleash the power.
Last edited by eight; 2012-01-04 at 01:16.
|
|
2012-01-04
, 01:15
|
|
Posts: 136 |
Thanked: 14 times |
Joined on Feb 2011
|
#4
|
Originally Posted by eight
Yep it's working,
Is it working when you connect local on the home pc?
With "telnet ip-adress 5800" you can test if portforwarding of port 5800 to vncserver works from outside.
edit:
Just saw you have a wrt54g, a very nice router. But not with the original Firmware.
I would suggest to flash it to dd-wrt when you have some spare time to unleash the power.
I can remote just fine when i connect it to my local wifi (same connection)
hmm thanks for the info i'll try that once i'm done with this
 |
|
2012-01-04
, 01:35
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#5
|
Slightly off topic.
But have you also installed the mirage driver for tightvnc?
It makes a much improved difference than without it.
But have you also installed the mirage driver for tightvnc?
It makes a much improved difference than without it.
|
|
2012-01-04
, 01:44
|
|
Posts: 136 |
Thanked: 14 times |
Joined on Feb 2011
|
#6
|
Originally Posted by Addison
Thanks for the tips, i'll check the difference once i get this working..
Slightly off topic.
But have you also installed the mirage driver for tightvnc?
It makes a much improved difference than without it.
Hmm after reading somewhere else it says that it's recommended to use ssh, is it absolutely necessary?
But i don't think that's gonna solve this problem right?
|
|
2012-01-04
, 02:13
|
|
Posts: 106 |
Thanked: 81 times |
Joined on Dec 2011
@ /
|
#7
|
It is necessary if you want to keep your desktop stream privat, tunneling over ssh encrypts all vnc data.
And it could solve your problem, as you first connect to a ssh-server on the desktop, and then to a tunneled port of vnc. So for this you have to get portforwarding to ssh (22) working, and over this every port can be tunneled.
It is even possible to install a ssh-server on the wrt54g.
Last edited by eight; 2012-01-04 at 02:24.
And it could solve your problem, as you first connect to a ssh-server on the desktop, and then to a tunneled port of vnc. So for this you have to get portforwarding to ssh (22) working, and over this every port can be tunneled.
It is even possible to install a ssh-server on the wrt54g.
Last edited by eight; 2012-01-04 at 02:24.
|
|
2012-01-04
, 09:27
|
|
Posts: 136 |
Thanked: 14 times |
Joined on Feb 2011
|
#8
|
Managed to get it work with the help of a friend
It's nice but I'm getting black screens occassionally, is there any fix for this?
It's nice but I'm getting black screens occassionally, is there any fix for this?
|
|
2012-01-04
, 09:33
|
|
Posts: 244 |
Thanked: 354 times |
Joined on Jul 2010
@ Scotland
|
#9
|
Originally Posted by shuraizo
Re the black screen ; vnc can clash with terminal services. Try changing to 5801 and 5901 (whicb would be hostname:1 in vnc connection terms)
Managed to get it work with the help of a friend
It's nice but I'm getting black screens occassionally, is there any fix for this?
| The Following User Says Thank You to gregoranderson For This Useful Post: | ||
|
|
2012-01-04
, 09:44
|
|
Posts: 136 |
Thanked: 14 times |
Joined on Feb 2011
|
#10
|
Originally Posted by gregoranderson
Sorry where do i have to change this ?
Re the black screen ; vnc can clash with terminal services. Try changing to 5801 and 5901 (whicb would be hostname:1 in vnc connection terms)
On the router or on the server?
My home desktop and n900 have different network, because i want to be able to monitor it while i'm away
So I followed this port forwarding guide precisely
http://portforward.com/english/route.../Tight_VNC.htm
I've set up my static ip address, put it on the router port forward setting just like the guide says.
Tight vnc is already on the firewall exceptions,
But it still won't connect over the internet on my N900,
Am i missing something here?
Oh and i'm connecting it from n900 using external IP address of the router
Last edited by shuraizo; 2012-01-03 at 23:27.