Database Users

Setting up VNC or Remote Desktop

I've set up LogMeIn, but it's left me dissatisfied. I don't like the fact that it's website based, and it's a little slow for my tastes.
I've attempted VNC and Remote Desktop but, sadly, it's a little over my head. I'm by no means a noobie, but I've never dabbled in remote desktop type work before.
Is there a simple tutorial for setting up VNC or Remote Desktop clients for the Wizard? I could really use one. I've been trying to search for it for a few days, and I turned up absolute zilch.
Thanks!

both VNC and remote desktop would need to be enabled on your workstation / server / computer and make sure that either the required ports for VNC (port 5900+) and Remote Desktop Connection (port 3389) and open your firewall or the windows firewall is turned off.
if you are trying to use VNC / RDP, using your GPRS/EDGE connection then there's more tweaking which needs to be done ... this would entail you to go to your router/firewall and open ports 5900 (VNC) and 3389 (Terminal Services / Remote Desktop Connection) and point these ports to the right IP Address (which would be the IP address of your workstation).
if you have any questions about remote access just email me back ... i use my XDA Exec, Qtek 8500 and all the other PDA's i have to access my network at the office as well as at my clients all the time ... both through VNC and through Remote Desktop Connection ....

what program do you need on the wizard to do remote desktop?
right now i can remote desktop to my work computer from my laptop at home. is it similar? thank you.

There should be a remote desktop client already installed on your Wizard. Look in the Programs folder for "Terminal Services Client". It works pretty much the same as it does on big Windows.

As dumb as this is, I really need a step by step to help me out on this subject.
I'm unsure what is needed to get the Remote Desktop Client working. I have XP Pro. I have a "Remote" section under my home computers system properties. However, the one tutorial I could find asked me to go into Add/Remove Windows Devices and apply some sort of setting there. Upon doing so, I was asked to insert my Windows XP CD which . . . I don't have.
If I don't need that CD, I am open to doing either Remote Desktop or VNC. Whichever is preferable, I guess. I don't know which is more full-featured, which one is quicker, etc.
So I need help getting started. What do I do?

Hey Dr.Other
Okay here is a step by step to enable remote desktop on your computer ( much better then VNC in my book but I am sure others may disagree..so in the end its personal prefrence...I just like RD (remote desktop) better cause I can stream music if I wanted and its also encrypted (I think I read that some where) any way here it is for remote desktop.
Guessing you are useing Windows XP Pro
Right Click on MY COMPUTER ( on your desktop)
From the menu that opens up Click (Left click) on PROPERTIES
You will see a few tabs in a window called System Properties
Click on the REMOTEtab
Check the Box under the Remote desktop area that say ALL USEERS TO CONNECT REMOTELY TO THIS COMPUTER (its not in caps)
Next click on Select Remote User and click ADD
TYpe in the users name (what ever name you use to login with)
Hit Okay till your back to your desktop
Phone:
Start\Programs\Terminal services Client
under servers type in the IP address of your computer ( Hint try it locally 1st if you have wifi in your house and then click connect) its a bit difficult to naviagate and the colors are not the best ( which leads me toa question ...look at the bottem for the Q ) but it will do...I have hcked email looked at my fav places for a book name I had bookmarked but forgot etc. its really cumbersome but in teh end it may get the job done. Though Fair warning your icons and stuff will be bunched up on your desktop computer once you RD from your Phone
RD to your phone..... What ? can you remote desktop to your phone ?
I think so...if you enable terminal service port on the device you maybe able to connect to it from your computer ...but I am still trying to figure that one out
Question for every one: IS it possible to get better colors when connecting to your home computer via terminal services on your phone ? ...they look like 256 colors (eww)

geekserver said:
Question for every one: IS it possible to get better colors when connecting to your home computer via terminal services on your phone ? ...they look like 256 colors (eww)
Click to expand...
Click to collapse
Even if you could it would slow the process down so much it wouldnt be worth it. I wouldnt even have a background on as it slows to a crawl.

i've looked everywhere, seriously. -remote desktop

any detailed how to guide?, i can do it, i'm fairly tech savvy, so i just need to kneed out a few things. maybe if you caould start from the beginning and i can see where i went wrong.
logmein.com works, but i want something more personal, just bewtween the computer and my phone. somerthing that looks good and scales full screen preferably.
please guys?, point me in the right direction.. all the posts just keep saying to search and there's lots of info, but there's no step by step guide.
thanks guys!

ok i got it going.
first go to the computer you want to connect to and go to control panel / system
click on remote, enable remote users
go to start menu, run. type cmd
in command write "ipconfig /all"
take note of your ip address
on your phone go to remote desktop,
computer = your ip address
username = (go to startmenu, control panel, user accounts) use one of those names.
password = blank unless you have a password.
domain = i left blank.
connect full color unless it doesnt work for you
if you can connect and you get a password error
type the error you get inot google and you should get a fix as your first link.
try that.
blam, remote desktop, it's awesome.

Nice how-to...
this is the most succinct tutorial on how to do this that I've seen. I'm still having trouble, though. I get the "Cannot connect. Likely reason are: 1 the remote comupter is not set up for this. 2. Reached the maximum number of connections. 3. A network error occurred while connecting."
I have set up the XP PC, & taken down all firewalls. I only have one user account and it has a password. I've even tried using Hamachi with one of their VPN ip addresses (awesome and free for pc2pc). I 've combed trhough my router settings too, and tried to clear everything there, too. I can RD from an XP laptop, so ti seems to be something on the unit, to me. I've also setup file sharing w/ Total Commander (it's served my purposes amply).
I really have googled & googled & googled. If anyone has any idea what is going on, I'd be grateful for some ideas.

Have you enabled the RDP on the host computer?
Right click my computer
Properties
Remote
Then enable allow user to connect remotely.

Will only work on XP Pro, or Vista if you choose to allow older clients which they scaremonger you against by saying it's less secure.

Danke!
I've been scared away from Vista for the usual "new" OS reasons, but perhaps it's getting to be time for me to haul my old conservative back-end into the modern world.
Thanks so much for taking the time!
(and to Biohead: yes, I followed the instructions I lauded so vehemently.... ???)

you're running vista?
and you haven't been able to connect still, right?
sorry i could walk you through xp, but man vista sucks, i wouldn't touch it with a 10 foot pole.

i'm setting up remote desktop on my iphone
hahaha totally referred to this guide

and it sucks, so i'm sticking with vnc
man, i miss my exec/universal

dutchschultz said:
any detailed how to guide?, i can do it, i'm fairly tech savvy, so i just need to kneed out a few things. maybe if you caould start from the beginning and i can see where i went wrong.
logmein.com works, but i want something more personal, just bewtween the computer and my phone. somerthing that looks good and scales full screen preferably.
please guys?, point me in the right direction.. all the posts just keep saying to search and there's lots of info, but there's no step by step guide.
thanks guys!
Click to expand...
Click to collapse
Hope this helps
http://forum.xda-developers.com/showthread.php?t=366312
http://forum.xda-developers.com/showthread.php?t=294524

orb3000 said:
Hope this helps
http://forum.xda-developers.com/showthread.php?t=366312
http://forum.xda-developers.com/showthread.php?t=294524
Click to expand...
Click to collapse
you, my friend, are awesome

A possible solution for those of us on T-Mobile's standard web n walk
Sorry to resurrect this thread, but I thought I'd post my experiences here in case anyone else (like me) searches for a solution to enabling RDP on T-Mobile (UK at least).
I was having the same problem with remote desktop, it saying that the server was not available. I phoned up T-Mobile's helpdesk as recommended here and after getting past first line support (who didn't know what remote desktop was, and tried sending new connection settings to my phone to resolve the issue) I got through to someone who knew what they were talking about. Turns out that I'm on T-Mobile's "basic" or "handset-only" web-n-walk package, and it's not possible to use RDP on this. I assume they block the relevant ports. They told me that I could pay an extra fiver a month to upgrade to a version of web-n-walk which can handle RDP.
Well I told them I would think about it, but instead tried to find a way around it as the one or two times I need to use RDP are certainly not worth a fiver a month. My solution is probably only suitable for the more techy of us, but without much work and with no prior experience I managed to set up a SSH tunnel using FreeSSHd as a server running on my windows server (although a normal windows box should work fine - http://www.freesshd.com/) and zaTunnel as a client on my phone (http://www.zatelnet.com/zatunnel/main.php). Both programs are free.
Basically my phone takes all RDP connections and tunnels them over SSH to my windows server, which then turns them back into RDP connections. T-Mobile have no idea I'm using RDP, and if they block the SSH port in the future I can always change FreeSSHd to run on port 80 (for web). This will also work for other protocols T-Mobile might be blocking (FTP springs to mind).
Just thought I'd post this in case anyone was in my situation of needing RDP on their standard web'n'walk.
Edit Sorry posted this in the wrong thread! Will leave this post up however just in case someone finds it useful

echolock
Many thanks for the above have been searching everywhere for a fix to this. I am the same as you T Mobile (UK) and can't connect.
Could you give some additional advice as how you got the RDP to work.
For the record I can connect by Wi-Fi and by using a PAYG sim from a different carrier. However, I am on a contract with T Mobile and don't want to carry a different sim just to use the RDP.
I have installed both apps. I can make a connection from zaTunnel on Port SSH:24 to the freeSSHD server (SSH - listening on port 24). Other than adding a User and changing the default port to 24 there are no other changes I have made in freeSSHD.
Under the connections tab in zaTunnel I have left Network: Automatic with the other settings relevant to make a connection.
Under the ports tab of zaTunnel I have
LP> 3389,
IP/URL . IP of the desktop I want to connect to of 192.168.1.10
>RP 3389
When I the start the Remote Desktop app under my Windows Mobile 6.1 it indicates connecting the fails as before.
Also forgot to mention freeSSHD is running on the desktop I want to connect to.

Sure thing.
When you run Remote Desktop under Windows Mobile, make sure you connect to "localhost" NOT to the IP of the desktop you want to connect to.
Your other settings seem correct to me.
To attempt to explain a little, basically what happens is as follows. For simplicity's sake I will have three machines, your phone, your SSH server and your RDP server (although the latter two can be the same).
On your phone:
1) Remote Desktop connects to localhost on port 3389.
2) zaTunnel is listening on localhost on port 3389. It echos all commands sent to this port out on port 22 over your cellular connection to your SSH server, also providing details of your RDP server and port.
On your SSH server:
3) FreeSSHd receives the commands sent over port 22 and is told by zaTunnel to convert them to commands sent to your RDP server using port 3389.
On your RDP server:
4) Remote Desktop receives a normal RDP request over the normal port from your SSH server.
5) Responses are sent to your SSH server.
On your SSH server:
6) FreeSSHd receives the RDP responses, and sends them back to your phone over port 22.
On your phone:
7) zaTunnel converts the commands sent over port 22 back into RDP commands sent over port 3389.
8) Remote desktop receives a response from zaTunnel and thinks it's connected directly to an RDP server on localhost. In actuality it's connected to your RDP server using an SSH tunnel provided by zaTunnel and FreeSSHd.
Hope this makes sense, I'm not very good at explaining this!

Ah found another problem. The IP of your desktop you say is 192.168.1.10 - this is a local IP address so will only work on your local network.
Go to a website like http://whatismyipaddress.com/ from the machine you run SSHd on to find out what your current "external" IP address is. Bear in mind that most home broadband connections have a "dynamic" address which is allocated to you and might change from time to time - you can always use something like http://www.dyndns.com/services/dns/dyndns/ to set yourself up with a static hostname, and run a program on your machine which updates your hostname with the correct IP address every time it changes. Some routers have this functionality built in.

Thanks for the quick response and explanation.
Between posting and reading your reply I had worked out the RDP app needs the localhost or the IP 127.0.0.1.
I had come back here to post, so others would know in future.
Your other point you raised about the desktop IP. I have used this only in the ports tab on zaTunnel. The connection tab has a proper mydomainname.com address. (Provides email and a webmail interface).
Anyway, can connect now and thank you again in solving this for me. (If your in Leeds I will buy you a beer).

Ah yeah the 192.* address would work on the ports tab, fair enough. Might be worth pointing out if others read this that this is only the case if the machine you're trying to RDP to is on the same local network (or the same machine) as the machine you have FreeSSHd running on.
But good to hear you got it working Now hopefully T-Mobile won't cotton-on and decide to block port 22 too...

Mount Windows share over SSH? (cifs?)

Has anyone done this? At home on wifi, I can mount my windows shares directly to the nook, browsing my comics collection / files on the device.
It'd be great to be able to do this from outside my network, securely..but I'm having trouble setting up a ssh server and connectbot.
Anyone done exactly this?
Or done connectbot with remote desktop? I could just change the port to 445 for similar instructions yes?

It is possible to set up an SSH server on Windows but it's not generally a good idea. If you have an always on Linux box then you could use that to tunnel into your network (this works very well). It looks like Connectbot does support port forwarding so in theory this should be possible but I've not personally tried it.
All that said, I have tried smb/cifs over ssh in the past and it did not work very well.
I think the "proper" solution to what you are trying to do would be VPN.

A Remote RDP Tutorial?

I honestly don't know what I'm doing. All I know is that all the things I've tried so far didnt work.
Can someone guide me on how to set this up on my NookColor?
My PC and NookColor share the same wifi connection via an Airport Exteme router. I know that there are two IP Address: one form y router, which I can see on www.whatismyip.com and the other is my computer's which I can see via cmd > ipconfig. So, my question is-- how do I set this thing up? Any step by step procedure?

What have you already tried? Also what version of OS are you using, some versions of windows have RDP kneecapped. Also, where are you trying to view it from?
If you already have RDP going, you can use Wyse PocketCloud to manage the connections through your google account, it's pretty straight-forward.
Personally, I use TightVNC as the desktop client and AndroidVNC Viewer and ConnectBot on the nook. I only use my home computer when at home, so the setup is fairly simple, have AndroidVNC talk to myipaddress using port 5900. Be sure to use the connecting password when you set up TightVNC - also check the character count as you enter it, sometimes it doesn't take all the characters, ie; the password "bob-ismyuncle" is stored as "bob-ismy".
For connections remotely (not on the same network) I first SSH into the machine with ConnectBot, then set up a port forward to localhost:5901 which AndroidVNC then connects to.
Also, has anyone tried NX?

I'll assume you're a windows user?
Make sure RDP is enabled on your PC (google it, really easy to enable)
If BOTH machines are connected to your network... get the PC's IP address (via cmd ipconfig) and connect to it using the RDP port (3128 on Windows)... ex: "192.168.100.199:3128"
If you want to use RDP away from home, you need to configure your router to forward any external connections on the RDP port directly to your PC. Then you'll want to connect using your external (router's) IP address. Ex: 111.222.333.444:3128 => 192.168.100.199:3128 .... then connect to "111.222.333.444:3128"

I like LogMeIn free and logMeIn Ignition great little app. also teamviewer has a free version and free app for android

[How To] Use ConnectBot to pass WebTop FF traffic without a tethering plan

I, like many here, have received a notice about tethering usage. I was working on a non-related project for someone who is heading to China so that they could bypass TGFoC when I had the following idea. If I can pass a computer in China through my SSH server to get internet access, why can't I do the same within the WebTop environment?
I know that in the WebTop environment, the phone window still has a valid connection to my carrier (AT&T, as the case may be), although the Webtop environment does not unless you pay for the double-dipping fee for tether usage. Here's what I did to get internet access on my phone (in Firefox) and it appears to work for me (YMMV):
===Things you'll need:===
Phone with WebTop
ConnectBot installed on the phone
Valid credentials to a box you can SSH to as well as create port forwards on
===Procedure===
1 On the phone, setup the ConnectBot ahead of time for the connection to the server.
2 Create a port forward
2a Name it anything you want (I called my WebProxy)
2b Type should be dynamic (SOCKS)
2c Source port is set to 8080. Any unused port should be fine, but this is the one I used
2d Destination is unchanged
3 Open up Webtop. Although untested, I see no reason why Webtop via HDMI shouldn't work.
4 Within the Mobile view window, connect to your server and ensure that the port forward is enabled (a disabled one has a line through it)
5 Open the Preferences of the WebTop's Firefox
6 Click on Advanced->Network->Settings
7 Change the proxy to be SOCKS and use 127.0.0.1 as the IP and the same port number as you selected in step 2c
8 If you want the DNS requests to work, you may wish to change that within about:config (look for "network.proxy.socks_remote_dns" and set it to true)
Your FF should now pass all its traffic through ConnectBot's SSH connection.
===Caveats===
1 All your network traffic from Firefox will be slower due to your SSH server acting as proxy.
2 You obviously need a desktop/ server machine that is reachable all the time. This may not be cost effective if this is its only use.
3 I do not claim that this is undetectable, only that it works. If another person more knowledgeable in this could comment, I'd appreciate it.
Thoughts?

I'm having occasional issues with ConnectBot not creating the port forward while on mobile data, and I'm thinking it may be timing related. Could anyone assist?

wingmanjd said:
I'm having occasional issues with ConnectBot not creating the port forward while on mobile data, and I'm thinking it may be timing related. Could anyone assist?
Click to expand...
Click to collapse
Solved my own problem. I had a dying Atrix phone previously. My tutorial above works perfectly on my new phone.

This really helped me!
Thanks a lot, it worked (although I can't find a "thanks" button).
But I don't get one little thing. Why we have to set the proxy to "source port"? In my (obviously mistaken) mind, it should be the destination port.
On a computer ssh command we would use something like:
ssh -ND [port-passed-to-proxy] [email protected]
I'm a bit confused by the name "source" to the port being passed to the proxy as I see it the other way around.

perr0.br said:
Thanks a lot, it worked (although I can't find a "thanks" button).
But I don't get one little thing. Why we have to set the proxy to "source port"? In my (obviously mistaken) mind, it should be the destination port.
On a computer ssh command we would use something like:
ssh -ND [port-passed-to-proxy] [email protected]
I'm a bit confused by the name "source" to the port being passed to the proxy as I see it the other way around.
Click to expand...
Click to collapse
Well, I think the confusion lies in possibly the way you're looking at it. From connectBot's viewpoint, it's going to be passing all data that hits the source port via its connection. Firefox's proxy port, and what I'd consider to be a destination port from its point of view, would be the connectBot's source port.
I'm not a developer, but I play one on TV.