Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 1 day ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 1 day, 2 hrs ago -
Maemo repository (3)
to Community by torsen - 1 day, 17 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 2 days, 15 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 3 days, 21 hrs ago - more...
 |
|
2010-09-01
, 13:38
|
|
Posts: 220 |
Thanked: 66 times |
Joined on Aug 2010
@ Melbourne, Australia
|
#312
|
Ok, these are things I've not done before. So bear with me!
The local desktop is the one connected to the router wirelessly that I'm trying to access via Rdesktop, and this has a false IP designated by the router? Meaning the router has it's own IP, which differs to the internet connection IP?
I know nothing of ssh tunnel, however I could possibly do the second option. What do I need to do to make this happen?
I apologise for the newb questions.
The local desktop is the one connected to the router wirelessly that I'm trying to access via Rdesktop, and this has a false IP designated by the router? Meaning the router has it's own IP, which differs to the internet connection IP?
I know nothing of ssh tunnel, however I could possibly do the second option. What do I need to do to make this happen?
I apologise for the newb questions.
 |
|
2010-09-02
, 08:59
|
|
Posts: 861 |
Thanked: 936 times |
Joined on Feb 2010
@ Bulgaria
|
#313
|
@5spdvl
Second option requires support from your router. You have to read the manual, it can be called different names(virtual server, port forwarding etc.) Here is how it can be done:
1. You have to know your router real IP(the one that is used to connect to Internet). Lets assume it is aaa.bbb.ccc.ddd
2. You have to check your local desktop IP. Lest assume it is xxx.yyy.www.zzz
3. Rdesktop is using port 3389. If your router supports the needed feature you must configure it to forward connection attempts to its port3389 to the 3389 port of your local desktop. So if there is connection attempt on aaa.bbb.ccc.ddd port 3389, it will be forwarded to local desktop xxx.yyy.www.zzz port 3389, where remote services is listening.
4. To connect from your N900 to the local desktop you must setup Rdesktop to connect to aaa.bbb.ccc.ddd.
Second option requires support from your router. You have to read the manual, it can be called different names(virtual server, port forwarding etc.) Here is how it can be done:
1. You have to know your router real IP(the one that is used to connect to Internet). Lets assume it is aaa.bbb.ccc.ddd
2. You have to check your local desktop IP. Lest assume it is xxx.yyy.www.zzz
3. Rdesktop is using port 3389. If your router supports the needed feature you must configure it to forward connection attempts to its port3389 to the 3389 port of your local desktop. So if there is connection attempt on aaa.bbb.ccc.ddd port 3389, it will be forwarded to local desktop xxx.yyy.www.zzz port 3389, where remote services is listening.
4. To connect from your N900 to the local desktop you must setup Rdesktop to connect to aaa.bbb.ccc.ddd.
| The Following User Says Thank You to zlatko For This Useful Post: | ||
|
|
2010-09-02
, 19:27
|
|
Posts: 2 |
Thanked: 0 times |
Joined on Jul 2010
|
#314
|
Hi
i make music on my computer and since i'm able to control it with my n900 using rdesktop, i was wondering if there is a way to get the sound working. because everytime i try to say start a music program like fruity loops i get a error like couldn't create the Direct sound main object.
can anyone help me please...
i make music on my computer and since i'm able to control it with my n900 using rdesktop, i was wondering if there is a way to get the sound working. because everytime i try to say start a music program like fruity loops i get a error like couldn't create the Direct sound main object.
can anyone help me please...
|
|
2010-09-02
, 19:35
|
|
Posts: 131 |
Thanked: 62 times |
Joined on Feb 2010
|
#315
|
|
|
2010-09-02
, 22:37
|
|
Posts: 220 |
Thanked: 66 times |
Joined on Aug 2010
@ Melbourne, Australia
|
#316
|
Thankyou zlatko and uTMY. I feel I have a good understanding of the concept now. Will try it over the weekend.
|
|
2010-09-03
, 12:43
|
|
Posts: 220 |
Thanked: 66 times |
Joined on Aug 2010
@ Melbourne, Australia
|
#317
|
I have set my IP from dynamic to static, and I have enabled mh router to allow access for Remote Desktop via the Vista network manager. However, I have not been able to set the DMZ on my router to forward port 3389. The prgoram for my router (Linksys WRT120N) is different the one shown in the PDF manual shown in the web. Any thoughts?
Also. in rdesktop. I'm trying to work out what to put:
Server: IP (router or desktop connected to router?) :colon: 3389 (port)
Windows login
Domain: what goes here?
Also. in rdesktop. I'm trying to work out what to put:
Server: IP (router or desktop connected to router?) :colon: 3389 (port)
Windows login
Domain: what goes here?
|
|
2010-09-03
, 21:44
|
|
Posts: 2 |
Thanked: 0 times |
Joined on Jul 2010
|
#318
|
Server: your desktop ip
user name/password: acount wich you want to log on
domain: empty
this is the way i have done it and it works
user name/password: acount wich you want to log on
domain: empty
this is the way i have done it and it works
|
|
2010-09-03
, 21:57
|
|
Posts: 861 |
Thanked: 936 times |
Joined on Feb 2010
@ Bulgaria
|
#319
|
@5spdvl
Server: your router REAL IP
No need for port - rdesktop default port is 3389. But without configuring your router to forward its port 3389 to port 3389 of your local desktop you wont be able to do anything.
Server: your router REAL IP
No need for port - rdesktop default port is 3389. But without configuring your router to forward its port 3389 to port 3389 of your local desktop you wont be able to do anything.
|
|
2010-09-03
, 23:15
|
|
Posts: 220 |
Thanked: 66 times |
Joined on Aug 2010
@ Melbourne, Australia
|
#320
|
Ok, I managed to log into my router to make port forwarding changes (typed in the IP in the address bar, logged in with the wifi access username and password).
I have:
-Single Port Forwarding
-Port Range Forwarding
-Port Range Triggering
-DMZ
I have setup what I believe to be configurations to forward connection attempts via the router IP to port 3389, however rdesktop is still unable to connect. I have disabled firewalls on the desktop I intend to access (desktop connected to wirelessly to router), as well as enabling access via Remo9te Desktop (through Windows Network Manager). The desktop doesn't have a Windows log in, you just push enter on the username without a password and it goes through.
Not sure what more I can do!
I have:
-Single Port Forwarding
-Port Range Forwarding
-Port Range Triggering
-DMZ
I have setup what I believe to be configurations to forward connection attempts via the router IP to port 3389, however rdesktop is still unable to connect. I have disabled firewalls on the desktop I intend to access (desktop connected to wirelessly to router), as well as enabling access via Remo9te Desktop (through Windows Network Manager). The desktop doesn't have a Windows log in, you just push enter on the username without a password and it goes through.
Not sure what more I can do!
Every device that is connected to network has IP. In your case the local desktop is in the LAN and has false IP designated by the router(e.g. 192.168.1.xxx or 10.10.10.yyy). To use remote desktop to it you can either do ssh tunnel with port forwarding to a *nix machine on your LAN, or you can set up the router to map its outside port xxxx to port 3389 of the desktop you are trying to access.