Related
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
I had been successfully tethering via Bluetooth with WM6's Internet Sharing function, and was doing so in XP. Well we just took the Vista plunge and I'm having an issue. The Network Connections is showing my BT connection as "Local Only" meaning I can browse other pc's on the network, but I can't get to the internet. My WiFi connection to my router connects to the internet with no problem (The Wireless Connection shows "Local & Internet Access."
So I can not get out to the internet using my Tytn as my connection. I used the "Diagnose Problem" function in Vista, and it tells me that it cannot ping IP address 192.168.0.1. This is the IP address of my router. I don't want it to try to hit that IP address, but I can't find a way to tell it NOT to. All the settings in TCP/IP protocol are set to obtain an IP address automatically. But it seems that even while using BT as the connection, it still wants to get to my router first, even though I'm not using my WiFi at all. I even tried disabling the WiFi connection. Still the same issue.
Does anyone know what I can do to get the pc to stop trying to get my router first?
Thanks!
Tell me about it! It took me an age to find some drivers that worked with my bluetooth, I ended up using the Toshiba stack. After a lot of fiddling I got it working but when it runs it is very hit and miss and I have yet to transfer anything between devices let alone surf the net! Have you tried the bluetooth set up wizard?
stpete111 said:
I had been successfully tethering via Bluetooth with WM6's Internet Sharing function, and was doing so in XP. Well we just took the Vista plunge and I'm having an issue. The Network Connections is showing my BT connection as "Local Only" meaning I can browse other pc's on the network, but I can't get to the internet. My WiFi connection to my router connects to the internet with no problem (The Wireless Connection shows "Local & Internet Access."
So I can not get out to the internet using my Tytn as my connection. I used the "Diagnose Problem" function in Vista, and it tells me that it cannot ping IP address 192.168.0.1. This is the IP address of my router. I don't want it to try to hit that IP address, but I can't find a way to tell it NOT to. All the settings in TCP/IP protocol are set to obtain an IP address automatically. But it seems that even while using BT as the connection, it still wants to get to my router first, even though I'm not using my WiFi at all. I even tried disabling the WiFi connection. Still the same issue.
Does anyone know what I can do to get the pc to stop trying to get my router first?
Thanks!
Click to expand...
Click to collapse
stpete111 said:
I had been successfully tethering via Bluetooth with WM6's Internet Sharing function, and was doing so in XP. Well we just took the Vista plunge and I'm having an issue. The Network Connections is showing my BT connection as "Local Only" meaning I can browse other pc's on the network, but I can't get to the internet. My WiFi connection to my router connects to the internet with no problem (The Wireless Connection shows "Local & Internet Access."
So I can not get out to the internet using my Tytn as my connection. I used the "Diagnose Problem" function in Vista, and it tells me that it cannot ping IP address 192.168.0.1. This is the IP address of my router. I don't want it to try to hit that IP address, but I can't find a way to tell it NOT to. All the settings in TCP/IP protocol are set to obtain an IP address automatically. But it seems that even while using BT as the connection, it still wants to get to my router first, even though I'm not using my WiFi at all. I even tried disabling the WiFi connection. Still the same issue.
Does anyone know what I can do to get the pc to stop trying to get my router first?
Thanks!
Click to expand...
Click to collapse
The internet sharing function on the TyTn used 192.168.0.1
You are saying that your router is also using the same address range.
That is a no-no. Change the router address to 192.168.1.1, and I think you will see better results.
@boz - Actually I have no issues connecting to Vista via Bluetooth, and all profiles work great (I'm using the latest Broadcomm stack). My issue is in my Network Connections, not BT itself.
@Wildbill - the Tytn is not using 192.168.0.1. The PC is trying to ping that IP address because it is the address of my wireless router, and the first time I ever accessed the net with that pc, I did so via WiFi through my wireless router at home. Now, what I am trying to do though is get on the internet in my car, while nowhere near my wireless router. But my pc still seems to want to get to my router as though I'm trying to connect to the net via Wifi, when I'm actually just trying to get to it through my phone. The PC connects to the phone with no problem, and the phone is connected to the internet, But, my problem is that I can't figure out how to tell my pc to NOT look for my wireless router's IP address first.
BT DUN was so much easier with Cingular. I wish one of the cooks could figure out how to get the DUN profile back into WM6's BT stack.
I am really confused here.
When you use Internet Sharing on the TyTn, You are using the Tytn to allow other devices to access the Internet thru the TyTn.
When you do that, the TyTn hands out the address of 192.168.0.100 and it is the gateway, and the Gateway address is 192.168.0.1.
If you have your home router using the same address range, you have the PC that the Tytn is sharing it's internet connection with seeing to addresses within the same range, and two gateways with the same address - The PC LAN card is seing the router at 192.168.0.1 and the Buetooth PAN is seing the phone gateway at the same 0.1 That is what I was trying to say. It won't work like that.
Oh ok I see what you're saying. I was assuming that when it gave me the error, that it was trying to ping my router since I knew that to be my router's address. I did not realize that the Tytn used such a similar gateway.
To correct what I said in my first post: I said that it was trying to ping "IP address"... the exact error message reads "Connot Communicate with DNS Server 192.168.0.1"
It shows a nifty little diagram of the PC connected to the Cingular Bluetooth network connection, then another line connecting to a picture of earth, which they call "internet," but there is a red "X" over that line showing that it can't connect to internet. When you click on Diagnose problem, the above error message is what comes up.
So now, I need to make sure I understand what you are saying Wildbill. I see what you mean from your post... being that I don't connect to my router anymore, ever, at all (since the pc never comes out of the car anymore, and I'm way out of range of my wireless router even in the driveway) what do I need to change? Everything in TCP/IP protocol settings are set to obtain addresses automatically.
Another interesting thing to note is that I did not have this problem when I had XP in my car, and I connected to my wireless router with that pc too. But Internet sharing worked fine with it.
If the only things connected are the TyTn and a PC, then the PC will obtain an IP from the TyTn, and it will be 192.168.1.100. It will tell the pc that the gateway is 192.168.0.1, which is the TyTn. Since the TyTn has Bluetooth 2.0, I would speculate that you could connect additional BT devices to the same BT PAN, and the TytN would likely hand out additional addreses like 0.101, 0.102, etc. I have not tried that nor have I read about it.
See that's what I gathered too. So I don't know why it can't get out to the internet, unless it's that Vista just won't let it for some reason. This bugs me because Internet Sharing worked fine in XP, and BT DUN works fine with Vista with my other phone. Unfortunately I'm getting rid of that phone. If my Tytn had a DUN profile in the BT stack I'd be fine. Weak.
i tehering in wm6 vista using bluetooth ban
I am unable to connect w/ a 3G connection...if I use WiFi I can make a remote desktop connection from my TyTn to my company server, but if I am on 3G I cannot connect. What am I missing?
digitalfx said:
I am unable to connect w/ a 3G connection...if I use WiFi I can make a remote desktop connection from my TyTn to my company server, but if I am on 3G I cannot connect. What am I missing?
Click to expand...
Click to collapse
make sure the connection is active before attempting to connect... so kick up internet explorer or something that initiates the connection...
I have a connection, I can see it go active then I get an error.
I tried as you suggested, the error just comes up immediatly.
ERROR:
Cannot Connect. Likely reasons are:
1. Specific Computer name does not exist
2. A network error occurred while establishing the connection.
Works fine when using WiFi or when connected to PC via USB...wont connect while on 3G
digitalfx said:
I have a connection, I can see it go active then I get an error.
I tried as you suggested, the error just comes up immediatly.
ERROR:
Cannot Connect. Likely reasons are:
1. Specific Computer name does not exist
2. A network error occurred while establishing the connection.
Works fine when using WiFi or when connected to PC via USB...wont connect while on 3G
Click to expand...
Click to collapse
mmm...i think i know your problem...
Click Start > Settings > Connections > Connections > Advanced > Select Networks... now what connection is specified in the 'Programs that automatically connect to a private network should connect using'
that should be your 'GPRS Connection' you are using to connect to your IP WAN
thanks, I had that set wrong...but still cant connect.
my 3G is setup as ISP (Cingular)...I called it "ISP"
The advanced setting had a preset called "My ISP", so I re-setup my connection and called it "My ISP" and selected it in "Programs that automatically connect to a private network should connect using:"
still wont connect.
digitalfx said:
thanks, I had that set wrong...but still cant connect.
my 3G is setup as ISP (Cingular)...I called it "ISP"
The advanced setting had a preset called "My ISP", so I re-setup my connection and called it "My ISP" and selected it in "Programs that automatically connect to a private network should connect using:"
still wont connect.
Click to expand...
Click to collapse
did you use Custel's cabs to install the Cingular Settings??
no, those always caused problems as I am using ISP not MediaNet.
btw- should have mentioned I am now using Black IV Shadow and Radio 1.43.00
Possible reason: your networkprovider has blocked the port used by remote desktop.
We had to change the gprs connection point/address when we wanted to use vpn to connect to our corporate network.
Try to get hold of at telnet application for your device and connect to port 3389 on you remote desktop server.
nadreas
digitalfx said:
no, those always caused problems as I am using ISP not MediaNet.
btw- should have mentioned I am now using Black IV Shadow and Radio 1.43.00
Click to expand...
Click to collapse
ahh well change your signature
ok... umm let me think... i want you to re-create the connections without using the My ISP... create a seperate one for Cingular...
digitalfx said:
I am unable to connect w/ a 3G connection...if I use WiFi I can make a remote desktop connection from my TyTn to my company server, but if I am on 3G I cannot connect. What am I missing?
Click to expand...
Click to collapse
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.
GOT IT!!! Thanks
esseff said:
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
esseff, pardon my noobness but when you speak of "VPN server" is that referring to the desktop I am trying to remote connect to?
I have an ATT 8525 w/Black Satin Normal WM6 on the ATT network using MediaNet as my GPRS.
I can remote in from almost any open network via my laptop. Could it be that ATT blocks 3389? If so can I alter the port RDM uses to setup a connection?
are you able to remote connect PC to PC? (from outside of your current LAN)
if not ... its not your phone its your firewall... try disabling your firewall w/in your pc os and router.
would explain why you can connect using wifi if its part of your router and its set up as a "home network".
I'd bet if you googled this you'd find EVERYTHING you need to know.
Yes, I can connect just fine PC to PC outside the LAN. I have my custom listen port opened as required. The issue is definitely with the 8525 connection settings or the ATT service. I have trolled google pretty extensively, but have been unsuccessful in finding some quality info.
Some time ago I messed with the IP address settings of the various adapters in Wifi - network adapters on my orbit. Now I have an issue where I try to connect to my PC via USB and though the Remote-NDIs Host automatically gets an IP address of 169.254.2.1, shortly after connecting via USB I get a message:
Pocket PC Networking
Cannot obtain a server-assigned IP address. Try again or enter an IP address in Network settings.
Could some kindly soul please take a look through the adapter list and give me the settings of any adapters that don't have a server-assigned address selected?
Pete.
Nobody can look at their orbit on O2 and tell me what adapters have static I.P's as default?
My setups all say 'Use Server assigned IP address' and it all seems to work OK
Cheers anyway
Each time I connect the phone to either my laptop or my PC I get the above message after a minute or so. In desperation today I went through the whole adapter list assigning a loop-back IP to each adapter one after the other then reconnecting the USB lead. Still get the same message
The exact problem here. Any news on how to solve this? It hapenned after I used Internet Sharing on my PDA.
Innovative said:
The exact problem here. Any news on how to solve this? It hapenned after I used Internet Sharing on my PDA.
Click to expand...
Click to collapse
This problem has been raised before and I eventually found a cure - can't remember exactly what is was but seem to remember having to set up a fake email account and then deleting it. Try a search in Google or similar I think that's how I found it. Sorry I can't be more specific at the moment but it is something that can be corrected.
PS - just found this on the Axim Site - not quite how I remember it but give it a try!
"Problem solved
I had this problem and found a fix.
I solved it by going to Settings|Connections|Configure Network adapters. Set
the 'Remote-NDIS Host' settings to use a specific IP address of 169.254.2.1,
subnet 255.255.0.0, default gateway 169.254.2.2
This is what they should be anyway, everything should work now and no
annoying message."
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