Hello everyone,
I am looking into the idea of being able to run an SSH or VNC server on the Windows Mobile, specifically our Rhodium, platform over cellular (3G). I know for a fact Tmobile can assign a 'route-able' IP address to a phone here in the USA (this has been tested). I can ping this IP address from any computer on the internet (albeit with some substantial latency). Perhaps there is a way to use the Tmobile allowed "pinging your device" to tunnel SSH or VNC traffic.
I would like to figure out a way to reach an SSH or VNC server on my phone using this method. We would need to somehow "open" an inbound port to the phone (this would function like basic port forwarding).
All of this works perfectly over WiFi, of course, but the goal is to get this working over cellular 3G (in particular, Tmobile). I see this as a technical challenge we can overcome as a group.
Does anyone have any ideas on this?
Folks, someone must have some ideas on this!
Here's a few links I came across:
http://kar1107.blogspot.com/2006/03/running-servers-on-cell-phones.html
http://digg.com/software/Run_a_web_server_from_your_phone
it isnt possible they close all ports except if you use port 80 on your phone for the server then you can run vnc server mobile
Antonius123,
So you're saying I can run a vnc server on port 80 on Tmobile? I have tried to run a web server on port 80 with no success.
Which mobile VNC server allows you to set the listening port?
its a program that is in alpha mode.
you can get your ip adress from your mobile phone trough php it is sending the real ip and not the fake.
But you must be aware that ip changes every time you get tro a difrent tower (gsm tower).
create a php page on a webserver with this code
PHP:
<?php
echo $_SERVER['REMOTE_ADDR'];
?>
Thanks for your reply, but I have additional questions.
I am able to get my real IP address from the phone by using VxUtil. This application tells me my IP address. Remember, I am able to have Tmobile assign me a 'route-able' IP address.
What is this program you speak of, which is in "alpha mode"?
The PHP code you provided, as I understand it, will simply give me my IP address, which VxUtil is able to do.
Were you able to somehow successfully access your device using the cellular connection? Which VNC software did you use, or did you use a different protocol?
It's interesting to note that when I check connectivity to my phone by doing "telnet IP_ADDRESS_HERE 80" I do not get a failure, the screen does hang as expected (Telnet can be used to see if ports are open without having a Telnet service running on my phone).
Can anyone please provide input?
Related
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
I just bought a program called Remote Desktop Client (by Xtralogic) and installed it.
However, when I tried to connect to my work, I get a notification 'Socket Is Not Connected'. I called the helpdesk of my work and they say it is not possible to have the server running on my mobile device......
The address I m trying to connect to is 172.20.20.20 with domain 'flexinet.local'. I used the correct username and password.
Maybe you guys can help me on my way?
First...I wouldn't go sticking those IP details up for the world to see. I'm sure it's safe enough but still. Next, have you checked not only the IP but the ports are correct? Then you should ensure that those ports are forwarded from the external domain you're connecting to.
Another thing you may want to check is if this app needs the prefix, i.e. http://YourDomain.com etc.
Lastly...are you attempting to connect from outside the network? Are you connected to the network via WiFi or are you attempting to connect via 3G from a remote location?
172.20.20.20 is a private address... 10.x.x.x, 192.x.x.x and 172.16.x.x to 172.30.x.x are private ranges and not valid on the internet - you'd need the external ip address or the fully qualified domain name (FQDN)... RDP uses port 3389 (if it's not been changed on the server) so your firewall will also need to be open and the transport you use to connect will also need to allow 3389 (WIFI / 3G)...
That is assuming you're trying to get to your server from outside your local network...
Did you try connecting to your work vpn (if you have one) so you can get inside your work network, then use the rdp client to connect to your machine?
Sent from my HTC Desire using XDA App
Does anyone know of a VNC app that - or any kind of "control my android phone from my PC" that:
1. is NOT Android Screencast
2. WORKS on the CDMA Galaxy Nexus
All the apps I've tried on the market thus far (e.g. droid vnc server) don't work - I think Verizon does something to prevent the IP address from being available to the app, so it reports the IP v6 MAC address and I can't connect to the phone.
Any solution (wired or wireless) would be fine, just one that works well (and is preferably free).
Hey, I'm in the same boat as you, i want to VNC onto my phone from my work PC as it makes my office life so much easier (did this on my iPhone for a couple of years)
I've managed to connect to my Galaxy Nexus GSM via LAN IP fine (IPV6 shows but used IPV4 IP instead from wireless settings) evem though i connected, the screen is blank and i can click but not type so looks like it needs some TLC on the developing side before it'll work :-(
Now for a remote IP you could try whatismyip.com or some simular site but i'm pretty sure most phon operators keep you on an internal network and route you out to the internegt, therefore meaning that you dont have any ports coming into your phone from the internet and therefore can't run any internet services, it has to be connection from your phone to a server not from PC/server on internet to your phone on internet.
I know however that back about 8 years ago i did get a windows mobile http server working, but think it's all changed since then..
Only exception to this would be if your phone was on wifi as you could setup a port forward from the router.
Maybe if TeamViewer made a version which allowed control of the phone, then you'd be able to do what you need.
Regards
Liam
Our VNC Server, VMLite VNC Server, works just find on Galaxy Nexus.
You can use USB connection, or reverse connection to connect if your phone's ip is blocked. i.e., you run tight vnc viwer in listening mode, you run the vnc server on the phone in reverse mode, so the vnc server will connect to the viewer.
Our app actually works w/o rooting.
https://play.google.com/store/apps/details?id=com.vmlite.vncserver&hl=en
The new teamviewer client will be your answer... just wait till its ported correctly to your rom
Are you sure? I thought team viewer is to view PC from android phones, instead of viewing phones from PC, i.e., different direction.
TerryNova said:
The new teamviewer client will be your answer... just wait till its ported correctly to your rom
Click to expand...
Click to collapse
Guys I am in over my head here, I've watched way too many YouTube videos and guides and I still cant get this.
I have 2 galaxy nexus phones and I am trying to leave one at home running the app IP webcam and taking video. That phone will be connected to my WiFi network at home. Then I am trying to use my other nexus phone running Tinycam Monitor and connected to Verizon's 4g network, to connect to that phone and stream me live video from home.
Now basically I am looking for someone who has set this up correctly or who could help talk me through this.
I have set up a static ip address
I went to my linksys routers web address and tried to port-forward ports 8080 and 80 which are the ones I need
Its not working though and it keeps saying failed connection on the phone. I think I am just typing in something wrong or missing a step.
Can anyone try and help me through this?
Use your IP address and 100 instead of 80
Sent from my Galaxy Nexus using Tapatalk 2
vhgomez36 said:
Use your IP address and 100 instead of 80
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Where are you talking about? You mean when I am forwarding the port on the linksys web interface? It asks me for the internal and external port (which I am typing in 8080) and then it asks for the "to ip address"
I am really unsure of what to put in the "To IP address" field. It shows my ip address but leaves blank the last few digits. Am I supposed to get that information from the phone from which I will be viewing the video?
bhawks23 said:
Where are you talking about? You mean when I am forwarding the port on the linksys web interface? It asks me for the internal and external port (which I am typing in 8080) and then it asks for the "to ip address"
Click to expand...
Click to collapse
Example.
vhgomez36 said:
Example.
Click to expand...
Click to collapse
Thanks for the reply, but I am still a little confused on what you are trying to say.
When I start up IP webcam it begins the video and it gives me an ip address and port number to connect to it. (this phone is on home wifi)
When I type those detail in tinycam monitor on my other phone (connected to verizon network), I add a new camera, set it to IP webcam for android, type the the previous ip hostname and port but it always fails to connect
I understand I need to portforward the port I am using to allow it to connect but I dont think I am doing that correctly
Make sure you port forward on your router to allow the connection.
Sent from my PG86100 using xda app-developers app
bhawks23 said:
Thanks for the reply, but I am still a little confused on what you are trying to say.
When I start up IP webcam it begins the video and it gives my an ip address and port number to connect to it. (this phone is on home wifi)
When I type those detail in tinycam monitor on my other phone (connected to verizon network), I add a new camera, set it to IP webcam for android, type the the previous ip hostname and port but it always fails to connect
I understand I need to portforward the port I am using to allow it to connect but I dont think I am doing that correctly
Click to expand...
Click to collapse
What happens if you turn on Wifi on your phone? Does it work then? You need the public domain IP address where your DVR is connected. I have the info. at home. I'll grab it tomorrow in case you still need the info.
handle223 said:
Make sure you port forward on your router to allow the connection.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Yeah handle223 that is the step where I believe that I am messing up at. I followed a guide that said I need to port forward 8080 and 80 ports so I tried to do that. I'm just not sure what to enter into the "to ip address" field on linksys website. Am I supposed to put my computers ip or something from either of the phones?
vhgomez36 said:
What happens if you turn on Wifi on your phone? Does it work then? You need the public domain IP address where your DVR is connected. I have the info. at home. I'll grab it tomorrow in case you still need the info.
Click to expand...
Click to collapse
Yes it works fine when the phone is connected to wifi so I'm trying to get it to work while away from home on a mobile network. Yeah if you could help me out tomorrow that would be great. Thanks for the help already
bhawks23 said:
Yes it works fine when the phone is connected to wifi so I'm trying to get it to work while away from home on a mobile network. Yeah if you could help me out tomorrow that would be great. Thanks for the help already
Click to expand...
Click to collapse
There your problem...wrong IP address. I can help you more tomorrow when I get home.
vhgomez36 said:
There your problem...wrong IP address. I can help you more tomorrow when I get home.
Click to expand...
Click to collapse
Sounds good man thanks
Essentially, what you need to do is:
1. Set your home phone up with a static IP address. You can normally do this by connecting your phone to wifi, and then going to the control interface for your router and fixing the IP address to that device (look under DHCP settings).
2. Forward an external port (e.g. 8080) of your static home IP address to the http port (80) on the IP address you just assigned permanently to your home phone. This will be under port forwarding in your router interface. The internal port is the one the home phone tells you when you start the webcam program.
3. Contact your ISP and ensure that a) you have a static IP (if not, you can register a dynamic one at e.g. dyn.com, and get software which will update it periodically); and b) that port 8080 is not blocked at their end. You can check your home external IP address on your router page, or if you cbf, go to ip4.me in a web browser and it will tell you.
4. With your external phone, with the wifi off, set your viewer up so that it looks for your router's external IP address and port 8080.
NOTE:
This is not a particularly sophisticated way of setting this up. Please consider the possibility that a technologically competent thief could use this as a way of casing your joint so they can rob you while you're out. Please at least a) ensure you have a strong password on your camera; and b) consider using a non-standard port rather than 8080 as your external port.
The more sophisticated way of doing this involves being able to ssh into your home network using e.g. PuTTY, and using this connection to do tunneling. I run an SSH server on my nexus sometimes (though I don't use it for this purpose), so it is definitely possible for this to be your phone. You can then remote into your home network and then use the camera client as if you were connected via wifi at home. Sing out if you'd like a hand setting up SSH, as it's actually not as hard as it sounds.
m.is.for.michael said:
Essentially, what you need to do is:
1. Set your home phone up with a static IP address. You can normally do this by connecting your phone to wifi, and then going to the control interface for your router and fixing the IP address to that device (look under DHCP settings).
2. Forward an external port (e.g. 8080) of your static home IP address to the http port (80) on the IP address you just assigned permanently to your home phone. This will be under port forwarding in your router interface. The internal port is the one the home phone tells you when you start the webcam program.
3. Contact your ISP and ensure that a) you have a static IP (if not, you can register a dynamic one at e.g. dyn.com, and get software which will update it periodically); and b) that port 8080 is not blocked at their end. You can check your home external IP address on your router page, or if you cbf, go to ip4.me in a web browser and it will tell you.
4. With your external phone, with the wifi off, set your viewer up so that it looks for your router's external IP address and port 8080.
NOTE:
This is not a particularly sophisticated way of setting this up. Please consider the possibility that a technologically competent thief could use this as a way of casing your joint so they can rob you while you're out. Please at least a) ensure you have a strong password on your camera; and b) consider using a non-standard port rather than 8080 as your external port.
The more sophisticated way of doing this involves being able to ssh into your home network using e.g. PuTTY, and using this connection to do tunneling. I run an SSH server on my nexus sometimes (though I don't use it for this purpose), so it is definitely possible for this to be your phone. You can then remote into your home network and then use the camera client as if you were connected via wifi at home. Sing out if you'd like a hand setting up SSH, as it's actually not as hard as it sounds.
Click to expand...
Click to collapse
To the OP, This is what you have to do. Everything is set up correctly on the phone is what it seems like but without a static IP from your internet service provider you're going to run into issues again the minute it changes it's IP address.
You'll have to connect to your router from the outside world (The internet) via the address that shows up in your router page under status. from there you connect to the port you specified with port forwarding and it'll connect to your phone from anywhere you're located outside of your home wifi.
m.is.for.michael said:
Essentially, what you need to do is:
1. Set your home phone up with a static IP address. You can normally do this by connecting your phone to wifi, and then going to the control interface for your router and fixing the IP address to that device (look under DHCP settings).
2. Forward an external port (e.g. 8080) of your static home IP address to the http port (80) on the IP address you just assigned permanently to your home phone. This will be under port forwarding in your router interface. The internal port is the one the home phone tells you when you start the webcam program.
3. Contact your ISP and ensure that a) you have a static IP (if not, you can register a dynamic one at e.g. dyn.com, and get software which will update it periodically); and b) that port 8080 is not blocked at their end. You can check your home external IP address on your router page, or if you cbf, go to ip4.me in a web browser and it will tell you.
4. With your external phone, with the wifi off, set your viewer up so that it looks for your router's external IP address and port 8080.
NOTE:
This is not a particularly sophisticated way of setting this up. Please consider the possibility that a technologically competent thief could use this as a way of casing your joint so they can rob you while you're out. Please at least a) ensure you have a strong password on your camera; and b) consider using a non-standard port rather than 8080 as your external port.
The more sophisticated way of doing this involves being able to ssh into your home network using e.g. PuTTY, and using this connection to do tunneling. I run an SSH server on my nexus sometimes (though I don't use it for this purpose), so it is definitely possible for this to be your phone. You can then remote into your home network and then use the camera client as if you were connected via wifi at home. Sing out if you'd like a hand setting up SSH, as it's actually not as hard as it sounds.
Click to expand...
Click to collapse
Yes! That was extremely helpful and thanks for describing it in detail.
It took me about 20 minutes but now it is working perfectly and I am able to stream live video from wherever I wish. (It is working better than I thought on 4g also)
I had to create a static id for my home mobile phone and that was under DHCP settings like you said. That allowed me to properly open up the ports
Thanks for the help everyone and I'm glad I didn't give up because this is pretty sweet, and also I do understand the risks.
On a side note, what kind of strain would this put on my extra nexus if I was running IP webcam 24/7? (while plugged in of course) Guess I will find out
Deleted
Sent from my GT-I9000
mobile
m.is.for.michael said:
Essentially, what you need to do is:
1. Set your home phone up with a static IP address. You can normally do this by connecting your phone to wifi, and then going to the control interface for your router and fixing the IP address to that device (look under DHCP settings).
2. Forward an external port (e.g. 8080) of your static home IP address to the http port (80) on the IP address you just assigned permanently to your home phone. This will be under port forwarding in your router interface. The internal port is the one the home phone tells you when you start the webcam program.
3. Contact your ISP and ensure that a) you have a static IP (if not, you can register a dynamic one at e.g. dyn.com, and get software which will update it periodically); and b) that port 8080 is not blocked at their end. You can check your home external IP address on your router page, or if you cbf, go to ip4.me in a web browser and it will tell you.
4. With your external phone, with the wifi off, set your viewer up so that it looks for your router's external IP address and port 8080.
NOTE:
This is not a particularly sophisticated way of setting this up. Please consider the possibility that a technologically competent thief could use this as a way of casing your joint so they can rob you while you're out. Please at least a) ensure you have a strong password on your camera; and b) consider using a non-standard port rather than 8080 as your external port.
The more sophisticated way of doing this involves being able to ssh into your home network using e.g. PuTTY, and using this connection to do tunneling. I run an SSH server on my nexus sometimes (though I don't use it for this purpose), so it is definitely possible for this to be your phone. You can then remote into your home network and then use the camera client as if you were connected via wifi at home. Sing out if you'd like a hand setting up SSH, as it's actually not as hard as it sounds.
Click to expand...
Click to collapse
Hi..
is it possible to do this with two mobile phones and without a static ip using mobile network only? somehow sending video signal to some free host using mobile internet?
like one phone stays at home connected to mobile internet as ip camera.. and with second I can watch the video from anywhere???
because when i create a local network with one and connect to it with other then all this works great...
OLD post i know but i figured id post in here just in case you guys are still around.
I have a S4 ( i don't think this matters)
But just like the OP. I have these 2 apps . The stream works fine in house (both on my wifi) but i cannot figure out how to get it connected off of wifi. the monitoring phone i am trying to use i turned the wifi off to use the 4glte but it just wont connect. I do have ports 8080 and 80 forwarded.
But what IP and port do i use the the connecting phones settings? the 192..... one is internal and works in the wifi but i tried that one and the external ip.... any ideas?
(the external IP i am using is the one from googling "whats my ip" inside the cams phone web browser so its the ip from the phone not pc)
Dear All,
Anyone managed to use "Port Forwarder Ultimate" app from Playstore? https://play.google.com/store/apps/details?id=com.icecoldapps.portforwarderultimatepro&hl=en
I'm not a technical person but this method has other potentials to explore. Maybe someone has patient to teach non-IT person.
I know that I should be satisfied with "USB tethering" in android. But users experience improves with new things.
As prerequisite, we should be able to ping our phone's public IP. but how to ping mobile Public IP?
A detailed guide with screenshot or video will help.
Thanks,
AB
This app does not provide such a feature, it would work if it was installed on your carrier router.
You have an class c address witch is not routable.
The app provide means for running a server app on your phone that is using a port below 1024 , ex: ftp, web etc. If you are connected on your wifi network and make proper port forwarding on your router than you will be able to access your phone from the Internet. But it does not make any sense in doing so.
To access your phone's external ip address regularly you need to run the DynDNS client that forwards your ip to dyndns. When you setup an account with DynDNS you select a url to use and DYDNS will forward any requests to that URL to your phone's current ip address. Naturally you will need a service running on your phone like a web server, ftp or vnc depending on what you want to do.
mdalacu said:
This app does not provide such a feature, it would work if it was installed on your carrier router.
You have an class c address witch is not routable.
The app provide means for running a server app on your phone that is using a port below 1024 , ex: ftp, web etc. If you are connected on your wifi network and make proper port forwarding on your router than you will be able to access your phone from the Internet. But it does not make any sense in doing so.
Click to expand...
Click to collapse
I purchased the below item from ebay. I'm thinking of pushing my phone's internet to standard router. Then I will have wired and wireless connection. USB tethering works but I want a bigger network. Maybe you guys can suggest an easy procedures?
http://www.ebay.com/itm/190466358913?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649
If there is still help needed with Port Forwarder Ultimate, I'm one of the developers
Themuzz said:
If there is still help needed with Port Forwarder Ultimate, I'm one of the developers
Click to expand...
Click to collapse
Hi developer,
This what I want to set-up (he ethernet jack will come soon). Internet from phone to Buffalo router! Can you please share the solution?