Related
I do not have Broadband internet. I got the Touch because the Internet Sharing option with Sprint PCS if free on my account. I what to share my Sprint EVDO connection with my Xbox360. Heres my setup...
1:HTC Touch in Internet Sharing mode via USB. IPv4:192.168.0.1 no DG
2:When trying to share connection to Ethernet port Windows wants the IPv4 of the Ethernet port to be 192.168.0.1. Windows give this error...
http://support.microsoft.com/kb/241769
Error 783: Internet Connection Sharing cannot be enabled. The LAN connection selected as the private network is either not present, or is disconnected from the network. Please ensure that the LAN adapter is connected before enabling Internet Connection Sharing.
I looked up this Error. It states that Windows wants the Ethernet port to be 19.168.0.1 and something else is using that IP already. The Touch uses that IP and I don't know how to change it or change the IP that Windows wants to use. Please Help!
Your touch should be using 192.168.2.1 and the virtual adapter on your computer should be 192.168.2.2.
Check to see that there aren't any interfaces that have that port configured statically. In theory this should work although the latency is going to be out the roof and will definitely not be worth playing any games on.
I have the Vogue(6900) as well, and while the download speeds from sprint are pretty quick when connected to a computer, it will be hard to get any good speeds out of it IMO.
Let me know if you figure this out. If I think of anything else, I will let you know.
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
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
I know, I know. I should know this. But for the life of me, I cannot figure it out. I'm trying to use Gmote with my evo, so I can stream music, vid etc. I installed it on my phone, and on my laptop. I have a home network set up, the only access to the net that I have right now is through Cricket Broadband. It is WEEAK. When I open Gmote on my laptop, it just gives me the message saying that Im not connected to a network. How to I get it to see it, or do I need a router or somethin?
BAleR said:
I know, I know. I should know this. But for the life of me, I cannot figure it out. I'm trying to use Gmote with my evo, so I can stream music, vid etc. I installed it on my phone, and on my laptop. I have a home network set up, the only access to the net that I have right now is through Cricket Broadband. It is WEEAK. When I open Gmote on my laptop, it just gives me the message saying that Im not connected to a network. How to I get it to see it, or do I need a router or somethin?
Click to expand...
Click to collapse
I have Gmote set up and all you need is to have your laptop hooked up to your wifi and have your phone also hooked up to the same wifi and make sure you have set the password on your laptop the same as for your phone. SOmetimes you will get a windows firewall notification on your computer so make sure you click on 'allow'.
Well cricket broadband doesnt run through wifi, so I have to make a seprate network. for some reason my phone wont see the network at all.
I am not sure if Windows can set up a domain to create an independent network, this is usually done through a router. Though I don't see why you couldn't set up a VPN and associate the devices within that. There is also the option of setting up a virtual machine on your laptop and running that as a router through the virtual nic's created by it.
Easiest would probably be the VPN. Just Google setting up a VPN in Vista.
Sent from Ye olde Evo
linflas said:
I am not sure if Windows can set up a domain to create an independent network, this is usually done through a router. Though I don't see why you couldn't set up a VPN and associate the devices within that. There is also the option of setting up a virtual machine on your laptop and running that as a router through the virtual nic's created by it.
Easiest would probably be the VPN. Just Google setting up a VPN in Vista.
Sent from Ye olde Evo
Click to expand...
Click to collapse
Seems like I just don't have the stuff to do this. I have to use a Publicvpn account and they charge you by the minute.
The error i get from Gmote on my computer is this:
Unable to join the multicast socket. Is the computer connected to a network? Exiting Gmote.
I can't even get it to start. I am connected to the internet via Cricket broadband USB modem. What am I missing?
Yeah, that is an issue, can you set up a virtual machine to act as your server? Without a router makes all of this very tough.
Sent from Ye Olde Evo
I have a question regarding tethering via wifi on my T989D.
I am using the Juggernaut v5.0 on my Telus T989D. It has wifi-sharing app built in. When I use this application to share my mobile internet with my PC, I get two different ip addresses. For example, use my PC's browser, I find my PC's ip address is 123.123.123.57, however my phone's IP address is 123.123.123.101. So my phone and my pc have different ip addresses.
Strange enough, my Samsung Vibrant (T959 from TMobile), is different. I use wifi tethering for root user app, and I find my PC and my phone (T959) share the same ip address.
Why they are different on my T989D?
The problem I am having right now is, tethering via T989D's built-in function is slow. Sometimes connection drops. However the tethering via my T959 is very reliable and fast.
Is there a way to disable built-in tethering on T989D and use the tethering for root user app on my T989D? I have tried to freeze the tether manager, but tethering for root user still has error in log and I cannot connect to it at all.
Please help, I want to fix my tethering problem with T989D.
thanks
think about it...
when you are WiFi tethering, your phone is acting as the router, and it provides its own IP to you
you don't get the Mobilicity IP on your laptop or whatever it's hooking up to your phone on WiFi
Sorry I don't get it.
Why my T989D and T959 act differently?
Basically there are two ways of tethering your phone to your PC, (to allow the PC to access the internet through your phone's data connection). The first way is connect PC to the phone, and then to configure your PC to see the phone as the network adapter. This is the method used when you configure USB tethering and you connect the PC to the phone with a USB cable. In that case there will only be 1 IP address assigned, because the PC is using the phone as the network adapter. (Imagine the phone is just an ethernet adapter for the PC)
The second way is to connect your phone to your PC and then to configure the PC to access the phone as if it were a Wireless Access Point (WAP). This is the method used when you use Wi-Fi sharing, (called Portable Hotspot). It's called sharing because the phone can share access to its data connection through its Wi-Fi hardware, for up to 8 different PCs simultaneously. In order to do this the phone has to route data requests correctly between the connected computers. It does this by assigning itself 1 IP address, and then assigning each PC that's connected to it, a different IP address. This is similar to setting up a wireless router at home to share a single internet connection between multiple PCs.
Usually USB tethering results in 1 IP address for both phone (network adapter) and PC, and Wi-Fi sharing/tethering results in 1 IP address for the phone and another IP address for each connected PC. However, I suppose it's possible to use different Wi-Fi tethering software that connects the PC to the phone via Wi-Fi, using only 1 IP address for both phone and PC, like the USB tether method. This would mean you couldn't share the connection, but it may work faster, since the phone wouldn't need to do any routing.
If the android-wifi-tether app is what you refer to as "wifi tethering for root user app", it's worth it to see if it works on the T989. (I'd be curious if it works too). However, if you're using Juggernaut 5.0, you should be able to install android-wifi-tether, and it should work. You shouldn't actually have a Tethering manager app in your list of apps, I don't and I'm using 5.0. If you do, and freezing Tethering manager doesn't allow this app to work, then I would try freezing both the Wi-Fi sharing app and the Wi-Fi sharing manager app as well. If it still doesn't work I'd be tempted to reflash the Juggernaut 5.0 ROM, and then install the android-wifi-tether app again, and see if it works.
Good Luck..
Thanks Jasnn, this really helped and I am now clear.
Yes, the application I am referring to was android-wifi-tether. It works flawlessly
on T959D. it is very slow on my T989D with Juggernaut 5.0/Telus modem.
If I reboot the phone and start tethering using android-wifi-tether, the application starts, but there is one error in log:
Setting ad-hoc mode: failed.
IP address are still different. My pc and phone has two different ipaddress.
I'd like to have the same ipaddress, also one thing bugs me is, the internet connection is not stable, the internet goes on and off. Lots of t989/D users have experienced this problem, there is no cure yet.
thanks
jasnn said:
Basically there are two ways of tethering your phone to your PC, (to allow the PC to access the internet through your phone's data connection). The first way is connect PC to the phone, and then to configure your PC to see the phone as the network adapter. This is the method used when you configure USB tethering and you connect the PC to the phone with a USB cable. In that case there will only be 1 IP address assigned, because the PC is using the phone as the network adapter. (Imagine the phone is just an ethernet adapter for the PC)
The second way is to connect your phone to your PC and then to configure the PC to access the phone as if it were a Wireless Access Point (WAP). This is the method used when you use Wi-Fi sharing, (called Portable Hotspot). It's called sharing because the phone can share access to its data connection through its Wi-Fi hardware, for up to 8 different PCs simultaneously. In order to do this the phone has to route data requests correctly between the connected computers. It does this by assigning itself 1 IP address, and then assigning each PC that's connected to it, a different IP address. This is similar to setting up a wireless router at home to share a single internet connection between multiple PCs.
Usually USB tethering results in 1 IP address for both phone (network adapter) and PC, and Wi-Fi sharing/tethering results in 1 IP address for the phone and another IP address for each connected PC. However, I suppose it's possible to use different Wi-Fi tethering software that connects the PC to the phone via Wi-Fi, using only 1 IP address for both phone and PC, like the USB tether method. This would mean you couldn't share the connection, but it may work faster, since the phone wouldn't need to do any routing.
If the android-wifi-tether app is what you refer to as "wifi tethering for root user app", it's worth it to see if it works on the T989. (I'd be curious if it works too). However, if you're using Juggernaut 5.0, you should be able to install android-wifi-tether, and it should work. You shouldn't actually have a Tethering manager app in your list of apps, I don't and I'm using 5.0. If you do, and freezing Tethering manager doesn't allow this app to work, then I would try freezing both the Wi-Fi sharing app and the Wi-Fi sharing manager app as well. If it still doesn't work I'd be tempted to reflash the Juggernaut 5.0 ROM, and then install the android-wifi-tether app again, and see if it works.
Good Luck..
Click to expand...
Click to collapse