I'm trying to connect to my server at work through the Jasjar's Terminal Services Client over a VPN and it's not working. The VPN connects and I can open up a web site on the server using an internal address, but the Terminal Services Client just times out. I can connect with the Terminal Services Client to other servers without using the VPN and I can connect through the VPN with a PC, so I don't know what's wrong. Any thoughts?
Thanks,
Brett
are you using internal dns name or internal ip, if dns the ip should work and its cos your not internally resolving, i have this prob with when i vpn in to my server, dns does eventually resolve but ip is instant
Is the vpn terminal services restricted by IP address? Are you using gprs or wifi? If gprs maybe the ip range is not set up on the vpn??? If using gprs are you using the apn internet3.voicestream.com?
Sorry, I know, not much help. Mine seems to work
I'm trying to connect by IP address over wifi. The Jasjar does recognize that it should go over the VPN because it will automatically make the VPN connection when I try to start the TSC connection.
I'm glad to hear that it's working for you guys, though, so at least I know it's possible.
Thanks,
Brett
TSC/RDP
I am also having difficulty in this area and havent been able to resolve when using WIFI from my AP at home over ADSL to the Public IP address, then a TSC/RDP connection to the internal network IP address of our TS box.
I can easily get to the TS box via the WIFI AP at work directly, just not from the home AP. I can easily use the home AP for my home laptops to connect to work, so I know the systems at both end are up and operational.
In summary, I just dont know why the JJ doesnt VPN via the home AP over the ADSL to public IP to use the TSC to the internal IP of the TS box.
I just wanted to follow up on this. For some reason both of the servers I was trying to RDP into behind the firewall were in some wierd state and they weren't accepting any connections from anything but my desktop PC. I rebooted them today and that solved the problem I was having.
Thanks,
Brett
Hi everyone,
I would like to connect to my laptop next room from local network. I can connect perfectly when I type in my IP address into the first textbox (Computer), but I can't connect when I type in my Computer Name (full computer name) instead. I tried MyPCName as Computer, \\MyPCName as Computer, forwarding port 3389 to my IP, leaving domain name empty, putting in my workgroup name as a domain, putting in my computer name as a domain, putting in myPCName\MyUserName as Username, \\MyPCName as Computer, still the same. It won't connect unless I put in the IP address. I would like to do this since my workplace assigns a different IP to my laptop then I assign at home, but naturally I have the same computer name at both places, so I would like to have a permanent setting for both places.
I'm running Windows 7 64 bit on my laptop and 1.66.405.2 ROM on my HTC HD2.
Many thanks in advance.
can you connect to it ok using another computer? might be a dns issue at a guess...
I can connect from other computers fine. Also on my HD2 I can see the host names of PC's under Resco Explorer and map them. However, remote desktop mobile refuses to work with the Computer Name. I can ping my Laptop's IP and also Computer name from pingbox2. Only in Remote Desktop Mobile there is a problem.
windows 7 by default blocks remote desktop connections from different versions of remote desktop. if you right click computer and select properties, then choose remote settings on the right hand side and select the middle option (accept connections from all verions of remote desktop). havent tried this my self but it solves most issues when using different versions of windows
OK, I sort of figured it but would still appreciate some help. Here is how I got it to work:
I had OpenDNS IP under DNS settings for wireless adapter. I deleted them. If I don't do this, pinging my computer name from HD2 always brings 67.215.65.132, which is opendns and not my true local IP, i.e. 192.168.x.x. I also had to disable the data connection (3G) and only have wireless. If I don't disable 3G, I can only connect with IP and not computer name. Only after doing these 2, when I pinged my computer name, I got the true local IP and I was able to connect with Remote Desktop Mobile using computer name. Now my question is:
1- I don't want to quit using opendns, is it possible?
2- I don't want to disable 3G connection every time, is it possible?
thanks in advance.
For me it works with MyPCName in computer and empty domain, both for XP and 7.
Something seems strange with your phone's networking configuration. At a guess (and this is a long shot), I would check your VPN settings on your phone to make sure you're not connecting to a different domain over 3G as this might explain why it works when you turn off the data connection on the phone and why it works by IP address.
As I said though, it's a long shot and is the only thing I could think of that fits your particular symptoms...
ozkaya said:
OK, I sort of figured it but would still appreciate some help. Here is how I got it to work:
I had OpenDNS IP under DNS settings for wireless adapter. I deleted them. If I don't do this, pinging my computer name from HD2 always brings 67.215.65.132, which is opendns and not my true local IP, i.e. 192.168.x.x. I also had to disable the data connection (3G) and only have wireless. Only after doing these 2, when I pinged my computer name, I got the true local IP and I was able to connect with Remote Desktop Mobile using computer name. Now my question is:
1- I don't want to quit using opendns, is it possible?
2- I don't want to disable 3G connection every time, is it possible?
thanks in advance.
Click to expand...
Click to collapse
about the open dns issues, I suspect that can be solved by making sure your router lets the incoming connection into your home network (you say it resolves to 66.whatever when open dns is used, shouldn't be a problem do long as you don't forget that will be your home ip address so that connection will neef to be allowed through the router and then forwarded by your routers virtual server (our whatever your router software calls out) to your laptops internal ip address.
as for the 3g it should use wifi over 3g by default..... mine certainly does, no need for me to disable it.
tomallen35 said:
Something seems strange with your phone's networking configuration. At a guess (and this is a long shot), I would check your VPN settings on your phone to make sure you're not connecting to a different domain over 3G as this might explain why it works when you turn off the data connection on the phone and why it works by IP address.
As I said though, it's a long shot and is the only thing I could think of that fits your particular symptoms...
Click to expand...
Click to collapse
I think you're right, when the 3G is on (and also Wifi on), Resco shows computers from all around the country when I click computers near me and not my local network. When only wifi is on I can see my local computers. 3G probably has precedence over Wifi? How can I correct this?
samsamuel said:
about the open dns issues, I suspect that can be solved by making sure your router lets the incoming connection into your home network (you say it resolves to 66.whatever when open dns is used, shouldn't be a problem do long as you don't forget that will be your home ip address so that connection will neef to be allowed through the router and then forwarded by your routers virtual server (our whatever your router software calls out) to your laptops internal ip address.
as for the 3g it should use wifi over 3g by default..... mine certainly does, no need for me to disable it.
Click to expand...
Click to collapse
But the 66.whatever address is generic openDNS lookup IP and same for everyone. Are you suggesting me to route this IP to my local IP, i.e. 192.168.x.x? Oh, one more thing, I can also connect when 3g and wifi are both on, but only through computer's IP and not computer name. Can you connect with computer name while both are on and connected?
when your phone does a dns lookup on the name it resolves to the open dns assigned address (not the same for everyone, otherwise the open fns system wouldn't work) so to connect to your computer the phone sends its request to open dns who forward that request to your current actual address.at home that address is your home ip address BUT it isn't your laptops address it is your routers address.(stop reading here if you don't have a router).
so the router needs to be told "if you get a connection request in port (whatever the remote desktop port is) please forward it to (laptop ip address)
its called port forwarding in some routers, virtual server in others.
samsamuel said:
so the router needs to be told "if you get a connection request in port (whatever the remote desktop port is) please forward it to (laptop ip address)
its called port forwarding in some routers, virtual server in others.
Click to expand...
Click to collapse
You're mixing up things a bit - he's not using dns but the computer netbios name. The point is that he has wifi on and connected as well as 3G, thus with an "intranet" ip address on Wifi... so the program/phone should be looking up the name on that connection, where it would find it, instead of looking up over the 3G connection. As the netbios protocol is not routable, it has no chance of finding the computer name over 3G/internet and back home, even with port mappings.
kilrah said:
You're mixing up things a bit - he's not using dns but the computer netbios name. The point is that he has wifi on and connected as well as 3G, thus with an "intranet" ip address on Wifi... so the program/phone should be looking up the name on that connection, where it would find it, instead of looking up over the 3G connection. As the netbios protocol is not routable, it has no chance of finding the computer name over 3G/internet and back home, even with port mappings.
Click to expand...
Click to collapse
you're totally right, I have a router and its port is forwarded to my laptop IP, but this is only good (and works well too) when I want to connect from Internet to my local network. I tried OpenDNS exceptions for VPN and defined an exception named as MyComputerName but it didn't work. Then I tried a dyndns solution, but it only works for external connections and not local network, i.e. it can't map local IP's. What I need is a dynamic client which can update my local IP.
I also tried to edit hosts entry in the registry with MyComputerName. It works for a single IP, but I'm not sure if I can write multiple IP adresses (my work and home local IP) into that. If I could maybe everything would be OK.
I've just tried a couple of things and it really works fine for me. If I connect Wifi only, I can remote desktop with the computer name. If I then connect data connection, it still works. Disabling wifi and obviously it doesn't work anymore. Re enabling wifi, it doesn't work at first, but does again after ~30 seconds once the netbios protocol has done its host lookup procedures.
There simply shouldn't be anything special to do.
kilrah said:
I've just tried a couple of things and it really works fine for me. If I connect Wifi only, I can remote desktop with the computer name. If I then connect data connection, it still works. Disabling wifi and obviously it doesn't work anymore. Re enabling wifi, it doesn't work at first, but does again after ~30 seconds once the netbios protocol has done its host lookup procedures.
There simply shouldn't be anything special to do.
Click to expand...
Click to collapse
thank you very much for your time, I appreciate it. You're right in that waiting a bit resolves the issue (it's a bit more than 30 secs for me that's why I thought it wasn't working when 3G is enabled) but only when OpenDNS is not used. I assume you don't use OpenDNS, right? Once I put that one into equation, it takes over NetBIOS protocol and returns its IP instead of the local IP(192.168.x.x). As far as I understand, DNS lookup has precedence over NETBIOS and if the name is not found in DNS it consults NETBIOS protocol. However OpenDNS has this nice "feature" where it finds the name with its own IP. There are several posts about this on its webpage and they say to either disable the typo correction or put exceptions for Netbios names, but sadly none of them works for me right now.
Nope, no OpenDNS, never actually heard of it.
How does it work? Do you enter their DNS server address in the network settings of your pc/phone, or is it an app you run?
you click Start/Settings/All Settings/Connections/Wifi/First Button/Switch to Network Adapters tab/Select Broadcom 802.11 DHD Network Adapter/Switch to Name Servers Tab/Type in 208.67.222.222 for primary DNS and 208.67.220.220 for secondary DNS, click OK. that's all. Could you try if it's not so much trouble? Thanks.
OK, remote desktop doesn't work either with the OpenDNS servers in.
I'm pretty sure it must be a limitation of the remote desktop app itself, as resco explorer can still navigate and/or discover the network shares of my other PCs with no problem. NBTStatCE also finds everybody.
Wouldn't even surprise me, as that Remote desktop mobile has always been troublesome. I don't remember exactly, but in the WM5 days it was pretty much impossible to use on a local network due to a weird handling of names... if I remember well all "local" (NetBIOS) addresses without a '.' entered in the remote desktop app would be redirected to the "Work" connection, while "remote" ones with a period would be directed on the "Internet" connection. As a network card can only be defined as one of them, if you wanted it to work in both cases through Wifi you had to switch the card from Work to Internet and back all the time. And of course when it's on Work it breaks some other things that use the default system handling like mail.
Where I work we use a software program that we connect to using our smartphones (some android, some windows mobile). To access the site we type the external (static) IP address and port into the phone's browser. However we do not get a very good cell signal in our building, so indoors we will use the wifi usually. This means instead of connecting to the external IP address, I have to use the internal IP to connect. Does anyone know of a way that I can connect using the external IP even when connected to the local wifi network so I don't need to change the IP I'm connecting to every time i go in and out of the building?
Have you tried using the external IP while on WiFi at work. It's simply a public IP and NAT should redirect it to the private IP address. Essentially data will travel out to the Internet and back to the Intranet.
Do you have the FQDN of the server? Ask your IT department, I'm sure they'd tell you the FQDN. You should be able to use that internally & externally. If you are connected to WiFi then internal DNS servers should resolve it to the local address and if you are external then public DNS records should help you find your way to the public IP.
+1 on what michaelkahl said. You will need to have your network dept to add DNS records if they don't already exist. Externally the FQDN (i.e. server.yourcompany.com) would resolve to the external public IP while internal DNS servers would resolve to the internal private IP.
We do this at my company for users connecting to a terminal server. No matter if they are at home or in the office they can use ts.ourcompany.com to connect to the server.