can anyone else use IP Webcam without problems on the shift? When I try to connect to my IP it doesn't work. and i get a ping timeout on my command prompt. do i need to set something up or is sprint blocking access?
Related
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
When I connect to my computer via remote desktop via Terminal Services Client over my LAN, it takes about a minute to connect - almost as if it waits for something to timeout before connecting. However, much to my amazement, I connected to my computer via the internet from a remote location via remote desktop via Terminal Services Client and it worked instantly - with no wait at all.
I think this means either my network is configured incorrectly (but I doubt this, all are on the same subnet using 192.168.1.x) or that wm2005 / terminal services client has a problem connecting to local computers.
First thing to check is whether there is some problem with your name service when connecting over the lan. There could be some default domain being set which is causing your 'timeout' style response.
Sorry, not got a universal so cannot tell you explicitly how to check this, but this is where I would start if it were a laptop showing the issues you describe
Gareth
Is there a delay if you use IP? This should have no delay as no DNS lookup is required.
Actually Tron, you bring up a good point, can your terminal server do a reverse DNS lookup on your IP address if you are on the LAN? Most ISPs provide a reverse DNS, but many companies don't bother internally. From your terminal server, you could try:
Start->Run: cmd
(If you are allowed)
then
nslookup <ip of laptop/universal>
If it comes back not found, then this could be the answer, and you should talk to the network admin
I am in desperate need of Help!! Can someone walk me through all the correct router (Linksys WRT54G)/phone settings (Cingular 8125) for accessing Terminal Services over GPRS. I can connect through terminal services while at home on my wireless network by using my network IP address. I would like to have this feature when away from home. The PC I want to connect to has XP Pro and I have enabled remote access.
OmegaDog said:
I am in desperate need of Help!! Can someone walk me through all the correct router (Linksys WRT54G)/phone settings (Cingular 8125) for accessing Terminal Services over GPRS. I can connect through terminal services while at home on my wireless network by using my network IP address. I would like to have this feature when away from home. The PC I want to connect to has XP Pro and I have enabled remote access.
Click to expand...
Click to collapse
Well, for you to access it from outside of your home, you have to know the IP address your internet provider assigns you. And you most likely will have to enable port forwarding on your router.
To resolve my home network from the office, I use no-ip.org for a DNS forwarder. Bassically, myplace.bounceme.com always points to what IP my cable modem has. N0-ip.org is a free service, with a utility that keeps the DNS tables updated.
I have enabled port forwarding and I know the ip address provided by my dsl provider by accessing www.whatismyip.com.
OmegaDog said:
I have enabled port forwarding and I know the ip address provided by my dsl provider by accessing www.whatismyip.com.
Click to expand...
Click to collapse
So what is the problem then ?
times out when trying to connect through cingular gprs
Just wondering if anyone can shed some light on this... I've setup port forwarding on my phone to an internal server, however I don't know how to access the external interface of my phone from the web.
When i run IPConfig on the phone, my WAN interface is a different IP to when I connect to a server on the internet and ask it to tell me what IP i'm originating from.
How do you even do something basic like ping these phones ? (on their 3g interface from someone else out on the web).
Any suggestions ? do they have any sort of firewall built in ?
Cheers
***************EDIT**************************
PROBLEM SOLVED. ISP has us sitting behind a NAT. I had to ring up and have them give me access to a special APN for a proper public IP.
My main goal is to use adb over my wifi lan. The first step would be network connectivity... which is mostly there. I can browse the web over wifi, and even ping my desktop from the terminal emulator. trying to ping my device from the desktop machine does not work, 100% packet loss.
Is this a security measure built into the rom? (NexusHD2-Froyo_V1.9b_NAND)
Is there a way to initiate the adb connection from the device side, rather than the desktop?
I know i am using the right local ip addresses.
sbtm said:
My main goal is to use adb over my wifi lan. The first step would be network connectivity... which is mostly there. I can browse the web over wifi, and even ping my desktop from the terminal emulator. trying to ping my device from the desktop machine does not work, 100% packet loss.
Is this a security measure built into the rom? (NexusHD2-Froyo_V1.9b_NAND)
Is there a way to initiate the adb connection from the device side, rather than the desktop?
I know i am using the right local ip addresses.
Click to expand...
Click to collapse
the same problem.
seems i can't ping from DESKTOP PC (win7) but can ping from notebook (also win7)
Look here: http://forum.xda-developers.com/showthread.php?t=939523&page=3 - there is same problem.