Hi all,
I've just got my XDAIIs and am just playing about with it before I start loading all my apps and syncing with outlook.
I've got the Wifi working with my home access point (with encryption).
When I try and use Terminal Service to remote desktop to my pc it trys to dial-up to O2 Active GPRS - why won't it use the wifi connection thats enabled? I can ping the pc via hostname and ip fine though.
By the way, the XDIIs is setup for use on O2 as standard (it's a brand new contract phone).
Any ideas? ANy help would be appreciated.
Many thanks
i think if you change the type of network from internet to work on the xda iis, then it might work.
I had a similar problem with activesync over wifi and had to set network card to work to get it to connect.
I tried that and it was still doing the same.
For atest I deleted all connection settings.
Then Terminal Services told me that I HAD to create a VPN connection setting for the server I'm connecting to. I did this but it kept faling when trying to connect with user/pass error.
I then thought I'd try the IP address of my machine instead of the hostname - This worked straight away!!
So does Terminal Services not like hostnames? I was hoping to connect to my server when I'm away from home using my no-ip address.
Does anyone have a similar setup or can shed any light on this?
Many thanks
DOH!
Just realised I should be using the fully qualified hostname rather than just the pc name.
i.e.
"server.uniquetouch.local" instead of just "server"
"athlon1400.uniquetouch.local" instead of just "athlon1400"
"pentium4.uniquetouch.local" instead of just "pentium4"
"dell.uniquetouch.local" instead of just "dell"
Now that I've got that bit working, I'm going to add the O2 GPRS connection settings back in and see if it still works.
Have you tried pocketVNC yet?? im just about to install it as i run vnc on all our system instead of terminal services
I also recommend VNC viewer.
It acts, amongst others, as a remote control to my windows media player & winamp on my media server.
You can find it all over the place, but here is 1 link:
http://www.cs.utah.edu/~midgley/wince/vnc.html
Is there some tutorial/help on using hte Remote Desktop Mobile to connect to a PC? I haven't been able to connect TP 2 to my PC running Vista. I put in the Computer name, User name, password, and domain and when I clicked "Connect", it returned an error:
Cannot connect. Likely reasons are:
1. specified computer name or ip does not exist.
2. A network error occured while establishing connection.
I tried both domain name and ip. Made no difference.
I also tried both on 3G as well as WiFi but it made no difference.
You'll need to set up two things:
set the vista machine to accept the remote connections
http://howtogeek.com/howto/windows-vista/turn-on-remote-desktop-in-windows-vista/
forward port 3389 on your router if you have one
http://portforward.com/
Then you should be up and running!
'tunes
Thanks, mad-tunes. Got it working now, at least when connected by WiFi. And when the phone and the PC are on the same Wifi network, I can connect simply by putting in the computer ip address. No domain is required and no port configuring required too.
Lord_BlackAdder said:
Thanks, mad-tunes. Got it working now, at least when connected by WiFi. And when the phone and the PC are on the same Wifi network, I can connect simply by putting in the computer ip address. No domain is required and no port configuring required too.
Click to expand...
Click to collapse
Good stuff, glad it helped a bit....
If you can't connect from the outside world (ie, using GPRS), then it's most probably a port forward thing...
If you want to get this bit working: How's the machine you're trying to RDP to connected to the 'net exactly?
(ADSL modem, router etc?)
mad_tunes said:
Good stuff, glad it helped a bit....
If you can't connect from the outside world (ie, using GPRS), then it's most probably a port forward thing...
If you want to get this bit working: How's the machine you're trying to RDP to connected to the 'net exactly?
(ADSL modem, router etc?)
Click to expand...
Click to collapse
Yes, the PC is behind the router. So probably woould need to do port forward as you have suggested. Having tested it yet. Would try this out later this week.
I was wondering, is theres a way to do this if youre on a home edition of windows?
the home edition I dont believe has remote desktop.
Remote desktop mobile using 3G connection
Has anyone gotten remote desktop mobile to work using only a 3G connection? I've got it working perfectly using wifi but can't for the life of me figure out how to do it over 3G. I searched and the closest thing I could find to being helpful was the following:
I had the same problem till I created two VPN connections. One for internal use (WiFi) and one for extenal use (3G).
The internal one uses the internal IP address of the VPN server and the external one uses the external IP address.
You have to sleect which connection you want to use before starting the connection depending on whether u r using WiFi or 3G.
Hope that makes sense. It works 4 me.
Click to expand...
Click to collapse
This makes sense but it's confusing about what to change in the VPN connection settings. Can anyone explain in more detail?
Thank you very much
squirtpunk said:
I was wondering, is theres a way to do this if youre on a home edition of windows?
Click to expand...
Click to collapse
No. You can only use third party solutions like VNC. RDP host is not included in Home Edition.
You have to go into your router and set up a port forward so that 3389 goes to internal IP address of the system you want to remote into. If you have port forwarding/triggering, you can have a different port (eg, 3390) trigger to 3389 internally. If you don't have port forwarding, you can change the listening port from the default 3389 to, eg, 3390 and then you can create a port forward to remote in that way. To access, add :3390 to the end of the remote address (eg, 64.246.222.91:3390). The registry path to the listening port is:
HLKM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp\PortNumber
You must reboot after changing the setting.
If you have a domain, it is incredibly useful to set up DNS for this, then you can simply enter the DNS name in the client. This works internally as well.
Update: So i just went to a Starbucks and tried using the wifi there to connect to my remote desktop and it couldn't connect!? But it can connect when I'm using the same wifi router as my remote computer does this mean I don't have the router properly port forwarded? Or is it some other issue? Any advice would be great.
Thanks
When you use your wifi at home, it ends up in the same IP subnet as the remote computer, so all you need to do is to enter the computer name.
When you're at a hotspot, you need to enter the public IP address for your router and step up port forwarding. Wifi outside of your home is no different from using EVDO as far as IP addressing is concerned. You must enter via public IP.
If you don't know what your public IP address is, open a browser from any computer at home and go to this URL:
http://whatismyip.com
It will tell you what the public IP is.
Cheap Loop-Hole
I got Remote Desktop to work on 3G.
First open Opera (or what ever your default browser is) set a home page to something that takes at least 5-10 second to load (if longer, even better), like an email account or m.myspace.com. Simple sites like m.google.com won't work because they load to quickly.
Close OPERA: I mean make sure its closed not just minimized.
This next part needs to be done rather quickly, so I advise making Remote Desktop a top icon in your Start Menu.
So Launch opera, and quickly launch Remote Desktop and hit connect.
Remote Desktop will piggy back off the Opera browser connection to get out to your computer.
Note: (make sure remote desktop works at home first, either by wifi, blue tooth, or direct usb, and by checking it from a computer outside of your network) once you know it works you should be able to connect to it.
Also note: as some one stated above, make sure that proper ports have been open on the computer and router than you should be good to go.
I'm sure their is a registry fix to get the remote desktop working without doing this, but this is the only way I've been able to do it for now..
Hope this helps...
---
I'm currently using AT&T Tilt 2 Stock Rom and Radio.
Check this out guys, it might be of some help: http://forum.xda-developers.com/showthread.php?t=533664
Thanks a lot guys! It's working just fine now (on both wifi and 3G!) turns out I didn't have the router properly port forwarded.
just started trying to figure this out today. spent about 15 minutes but couldnt get it going.
just installed windows7 on my old pc and im trying to get my htc tp2 (rhodium) to work with the preinstalled Remote Desktop Mobile application. i forwarded port 3389 on both tcp and udp since i didnt know which was necessary.
is a static ip necessary to get this setup by going into the ipv4 settings? also, what is the application looking for with the input for "domain"? - subnet mask? default gateway for my home network?
so far i have tried the following inputs in my tp2 for Remote Desktop Moble:
Computer: public ip
User Name: windows7 login name
password: windows 7 login password
domain: ???
any help is appreciated. going to try this more when i get home from work.
apathyps said:
just started trying to figure this out today. spent about 15 minutes but couldnt get it going.
just installed windows7 on my old pc and im trying to get my htc tp2 (rhodium) to work with the preinstalled Remote Desktop Mobile application. i forwarded port 3389 on both tcp and udp since i didnt know which was necessary.
is a static ip necessary to get this setup by going into the ipv4 settings? also, what is the application looking for with the input for "domain"? - subnet mask? default gateway for my home network?
so far i have tried the following inputs in my tp2 for Remote Desktop Moble:
Computer: public ip
User Name: windows7 login name
password: windows 7 login password
domain: ???
any help is appreciated. going to try this more when i get home from work.
Click to expand...
Click to collapse
network-wise what you need to do depends on how your PC's connected to the 'net...
if it's connected directly via something like a USB ADSL model or Virgin media cable box, then you'll only need to let 3389 through your PCs firewall.
If it's connected via anything like a router, then you'll also have to allow 3389 through your routers firewall, as well as forwarding port 3389 to your machine inside your network.
it's the port forwarding which needs the internal IP of your PC, so a static one's a good idea (otherwise, if your PCs internal IP address changes it'll stop working). you could set your router to always hand the same IP to your PC MAC address, which can be the best of both worlds (and how I do it).
http://www.portforward.coms a good place to start to find how to forward ports for your router if you're using one..
You also have to go to control panel>system>advanced system settings>remote and set things as you need in the 'remote desktop' section.
if you don't have the 'remote desktop' section, then you're running one of the home versions of the OS which doesn't support Remote desktop conenctions (out of the box )
re domains...if its a normal home PC and nothing to do with a business, then you wont have to enter one at all.
Once you're at home, get your TP2 on your internal network (wifi), and then try to rdp to your machine using its INTERNAL ip (192.168.*.*) and see if that works.
if it does, the PC end's fine and it's your router config you need to get right. if it doesnt, then its something at the PC..
post back here if you still have trouble..
ok, so connecting with the tp2 via 192.xxx.x.x works fine from within the network at home on wifi.
however, once i try and connect with the public ip, it doesnt work. did the port forwarding thing.
i setup the static ip, i tried putting the host pc in the dmz, and still nothing. i tried disabling the host pc's firewall, and nothing.
in remote desktop mobile, im putting in the public ip of the host pc, and have tried filling in the username and password fields, and also tried leaving them blank.
any ideas?
apathyps said:
ok, so connecting with the tp2 via 192.xxx.x.x works fine from within the network at home on wifi.
however, once i try and connect with the public ip, it doesnt work. did the port forwarding thing.
i setup the static ip, i tried putting the host pc in the dmz, and still nothing. i tried disabling the host pc's firewall, and nothing.
in remote desktop mobile, im putting in the public ip of the host pc, and have tried filling in the username and password fields, and also tried leaving them blank.
any ideas?
Click to expand...
Click to collapse
if its workin from inside your network, your PCs set just fine...so it must be the firewall or port forward on your router...
double-check that 3389s alowed through its firewall
and
the forwards set to point UPD+TCP on port 3389 to the current internal IP of your PC.
tbh, I cant think of much else but let me know how you get on
ah, got it working. had to forward from ANY -> 3389, not 3389->3389. duh. works now.
thanks guys
Strange, you shouldn't have had to. RDP defaults to 3389 so the client should be using that from the word go (I know mine do!)...it could be a wierd router thing.
Depending on the exact option(s) you had to change to get it going though, it's making your machine a little more open to the outside world. but maybe not in a huge way....
(so, is it now AnyIP:AnyPort>YourIP:3389 or AnyIp:AnyPort>YourIP:AnyPort? I think forwarding all ports to 3389 would wreck eMule!)
It's probably worth changing the port used from the default though tbh.
Your change it in the PCs registry and add ortno to the end of what you enter into the client.
(so it'd be something like 192.168.0.1:3390, for example)
Then change the rules on the router to match, of course.
'tunes
Has anyone got this to work.
I spent the last 8 days trying to figure out what was wrong with this, only to find out that vista cannot (by default) act as a RDP host.
well after i found that out i was RDP'ing to my home computer in as little as 5 minutes. I can connect to my home PC from my laptop or anyother computer using my external IP or my Dyndns name. Works awesome.
Now i am getting a new error on my TP2 when i try to connect.
the error reads
"The connection was ended because of a network error.
Please try connecting to the remote computer again."
Click to expand...
Click to collapse
I installed a "hack" as it were to give my Vista home premium machine the ability to become a RDP Host instead of just a client and i am wondering if maybe that this fix was not designed to allow this kind of connection
the fix turned on terminal services for RDP and set the port 3389 and said it was listening.
so i was wondering if anyone else using Vista Home (premium or basic only not the others) has got this to work on their TP2
Need some help please. i have a question on yahoo answers microsoft answers, ppcgeeks, and 2 other forums. and i am not getting anywhere...
have
I'm using Vista Ultimate so the hack to make remote desktop work was probably different than what you've done, but if you have it working from another location/device there is no reason remote desktop should not work from your TP2. I have mine working just fine. I connect to servername:443 (the port I am redirecting traffic to). There are multiple steps involved in this since you need to forward the traffic from your router to your PC if you are connecting from outside your LAN.
i have gone through a bunch of steps.
i have my ports forwarded and all that..
like you say... if i can connect from my laptop... there is NOOO reason i shouldnt be able to connect from my TP2.
I connect through either my external IP or my DYNDNS from my latop..
(Lan IP works too) But when i type either in my computer name nothing works
i have tried adding :3389 to the end of both and i have tried my user name and password and i have tried it withought. i have tried it with my routers domain name and without. i have tried everything i can think of..
simply there is no reason that this shouldnt work if i can connect from other computers... there is even pictures on PPCGeeks of people having it up and running. so its possible im just missing something.
it worked straight for me. With stuff like this it helps to break it up into it's component steps:
can you get it to work on another PC networked
can you get it to work on another device (PC) remotely and through the firwall?
Then you are left with TP2 issues if it doesn't work when the previous steps do.
This may not be much help as it seems that you know what you're doing
PS it worked for me straight away 'cos I was already using RDP on the PC with other devices
havent used vista home, afterall if your 'hacking' it for remote desktop........
but you have to forward port 3359 i believe it is on your router, to your pc's static ip. You HAVE to set a password if you havent done so already. It works rather well actually once connected.
Have a look here:
http://forum.xda-developers.com/showthread.php?t=533664
It´s almost the same process for Vista
bajunadustin, were you able to fix the problem? Because I am having the same exact problem myself right now.
Hi!
I was able to do Remote Desktop by connecting with my tilt 2 to my local Network so I used my Desktops address (192.168.1.4) as computer name and I was able to connect with the Tilt2.
Now, I am trying to figure out how to do the same but when I am not home thus connected to my network.
I tried using my REAL IP address but it was not able to connect to it.
I am running Windows 7 Ultimate any my tilt 2 has a stock 6.5
Thanks
You'll need to set up port forwarding on your router. Looks like this site has a bunch of guides to do so. You need to set it up to forward port 3389 to your desktop address (looks like 192.168.1.4) and you should be good to go, no specific config necessary on your tp2.
Edit: As a side note for security's sake only allow non-administrator accounts to remotely connect and make sure you use strong passwords!
That worked out great...thanks mate!
Yeah thanks Toleraen! I was just now finally getting around to check out the remote desktop client on both my phones, and was looking for exactly that
Glad I could help
Pretty cool to do this indeed...any other software you consider better than this to remote in to my PC?
shaolin95 said:
Pretty cool to do this indeed...any other software you consider better than this to remote in to my PC?
Click to expand...
Click to collapse
I hear VNC get recommended a lot, but I haven't had a chance to check it out yet (I'll do that once I've tried remote desktop). I've attached the cab for it, but I can't find any threads on it's use, you'll have to dig that up yourself
I must have tried a million different settings over several hours and never was able to connect via 3G or even locally when hooked in through wifi. I used to be able to do this with my Treo 750 with little hassle. I have the port forwarding set up on my Linksys WCG200 router. I have even tried turning all firewalls and encryption off. No joy. Anyone else have a Windows XP setup with a Linksys router that has had success with a Tilt 2 stock ROM? Note: I do not have a static IP. Has anyone successfully done this with a dynamic IP?
I am doing it to Windows 7 with a dynamic IP...I just make sure I got the one for the day(week) before living home if I want to remote in from work.
I use Hamachi to create a VPN connection and then remote into my PC that way, leave hamachi running on my desktop and then just run the mobile version on my phone when I want to remote in, that way there are no open port security issues to worry about and the VPN IP address never changes.
Is it any slower or faster than Remote Desktop?
Zylograth said:
I use Hamachi to create a VPN connection and then remote into my PC that way, leave hamachi running on my desktop and then just run the mobile version on my phone when I want to remote in, that way there are no open port security issues to worry about and the VPN IP address never changes.
Click to expand...
Click to collapse
Sweet! I had no idea hamachi had a mobile client now!!
I'm trying it out as soon as I get home today!
I use "Remote Touch Server" to remotely access my computer. The main reason i use it is because it keeps your computer on while you are accessing it. I use it for a handheld monitor for powerpoint presentations. That way I can see what the computer is doing, and tap the screen to advance to the next slide