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
Has anyone got this to work.
I spent the last 8 days trying to figure out what was wrong with this, only to find out that vista cannot (by default) act as a RDP host.
well after i found that out i was RDP'ing to my home computer in as little as 5 minutes. I can connect to my home PC from my laptop or anyother computer using my external IP or my Dyndns name. Works awesome.
Now i am getting a new error on my TP2 when i try to connect.
the error reads
"The connection was ended because of a network error.
Please try connecting to the remote computer again."
Click to expand...
Click to collapse
I installed a "hack" as it were to give my Vista home premium machine the ability to become a RDP Host instead of just a client and i am wondering if maybe that this fix was not designed to allow this kind of connection
the fix turned on terminal services for RDP and set the port 3389 and said it was listening.
so i was wondering if anyone else using Vista Home (premium or basic only not the others) has got this to work on their TP2
Need some help please. i have a question on yahoo answers microsoft answers, ppcgeeks, and 2 other forums. and i am not getting anywhere...
have
I'm using Vista Ultimate so the hack to make remote desktop work was probably different than what you've done, but if you have it working from another location/device there is no reason remote desktop should not work from your TP2. I have mine working just fine. I connect to servername:443 (the port I am redirecting traffic to). There are multiple steps involved in this since you need to forward the traffic from your router to your PC if you are connecting from outside your LAN.
i have gone through a bunch of steps.
i have my ports forwarded and all that..
like you say... if i can connect from my laptop... there is NOOO reason i shouldnt be able to connect from my TP2.
I connect through either my external IP or my DYNDNS from my latop..
(Lan IP works too) But when i type either in my computer name nothing works
i have tried adding :3389 to the end of both and i have tried my user name and password and i have tried it withought. i have tried it with my routers domain name and without. i have tried everything i can think of..
simply there is no reason that this shouldnt work if i can connect from other computers... there is even pictures on PPCGeeks of people having it up and running. so its possible im just missing something.
it worked straight for me. With stuff like this it helps to break it up into it's component steps:
can you get it to work on another PC networked
can you get it to work on another device (PC) remotely and through the firwall?
Then you are left with TP2 issues if it doesn't work when the previous steps do.
This may not be much help as it seems that you know what you're doing
PS it worked for me straight away 'cos I was already using RDP on the PC with other devices
havent used vista home, afterall if your 'hacking' it for remote desktop........
but you have to forward port 3359 i believe it is on your router, to your pc's static ip. You HAVE to set a password if you havent done so already. It works rather well actually once connected.
Have a look here:
http://forum.xda-developers.com/showthread.php?t=533664
It´s almost the same process for Vista
bajunadustin, were you able to fix the problem? Because I am having the same exact problem myself right now.
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
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)
Hello all!
Recently I've purchased the Swann DVR8-1425 security system.
I've been able to connect it to my home network successfully. I can remote view the cameras through my T999L (no root, completely stock) on WiFi through the SwannView app, but as soon as I put it into mobile data, it shows me a message of not being able to contact the server. I'm assuming if I were at someone elses house on their WiFi, it would be the same result. Same issue on my Dad's S2, rooted, running Infamous 3.0 in the T989 forums.
I've messed with most, if not all the settings I can possibly use with trial and error. When it comes down to it, obviously there's only the one setting that works with my WiFi (the given IP address from the DVR and a server port given: 9000) and it won't connect with mobile data whatsoever (2g, 4g, or LTE). I've tried using HTTP port 85 instead of the 9000, a preferred DNS server in place of the IP address, turning on and off UpNp (not really sure what that does). Absolutely nothing. Server connection fail each time when using mobile data.
I've disabled the firewall in hopes of it working, but I've had no luck. Haven't reset the router, assuming I just unplug and replug but other than that, I'm out of ideas. Not sure what else I can work on besides the firewall, if that even does anything.
The Swann software installed on my Mac does work, but haven't had a chance to test it somewhere other than my home network. It could work, but I wouldn't know at this point. Just more concentrated on the mobile data issue.
My knowledge is small when it comes to this networking stuff. Connecting to a WiFi hotspot is about as easy as it gets for me lol. I just got lucky with trial and error for setting it up with the home network. Just wondering if anyone has experience with this or ideas that may come to mind. At the worst, I won't be able to remote view anywhere other than using my wifi, but it will still record at least.
Thanks in advance!
MyanRagahis said:
The Swann software installed on my Mac does work, but haven't had a chance to test it somewhere other than my home network. It could work, but I wouldn't know at this point. Just more concentrated on the mobile data issue.
Click to expand...
Click to collapse
^^^^^
Seems to me you should test the remote connection elsewhere before you start troubleshooting a problem thst may not even exist. If its not configured correctly to do what you want, its not going to work across the internet which would include the mobile data.
Make sure you can access what you want remotely, then test over mobile data. Unless I read that wrong it doesn't sound to me like you've done this. You can test the mobile data connection all you want, but if its not working remotely by any other means you will be wasting your time. (Unless you got lucky and configured it correctly, but as you said, youre not very experienced with this).
Until you verify it does work remotely, there's no reason to assume its your phone or T-Mobile that is the problem.
Tbh, I'd assume first it was a router config on your side. (Unplugging it doesn't reset its settings, and even if it did it may not be configured as needed by default.)
You'd probably find better support by going to the equipment website and router website.
Sorry I don't have the answer your looking for, but hopefully ill get you in the right direction.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
^^^^^
Seems to me you should test the remote connection elsewhere before you start troubleshooting a problem thst may not even exist. If its not configured correctly to do what you want, its not going to work across the internet which would include the mobile data.
Make sure you can access what you want remotely, then test over mobile data. Unless I read that wrong it doesn't sound to me like you've done this. You can test the mobile data connection all you want, but if its not working remotely by any other means you will be wasting your time. (Unless you got lucky and configured it correctly, but as you said, youre not very experienced with this).
Until you verify it does work remotely, there's no reason to assume its your phone or T-Mobile that is the problem.
Tbh, I'd assume first it was a router config on your side. (Unplugging it doesn't reset its settings, and even if it did it may not be configured as needed by default.)
You'd probably find better support by going to the equipment website and router website.
Sorry I don't have the answer your looking for, but hopefully ill get you in the right direction.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
After read this earlier, I facepalmed myself and went to go test this out. Drove over to Starbucks a few minutes ago, connected to their wifi through my phone and it didn't connect Hmm...definitely a router setting then. The dvr itself is connected to the router by an ethernet cable. Just a matter of figuring out how to configuring the router settings. Thanks!
Try bluestacks
Hey. I came across this page looking for a solution to a similar problem. My new swann system connects fine with my phone on Orange but wouldn't connect to my partners identical phone on Vodafone via mobile Internet. Both worked on wifi. I solved by asking Google for my ip address, then going onto the swannview link app, under my device is a button to edit, on the edit page where it has p2p if you tap the line it gives you another option to connect with ip, then enter your ip where it says host. Save details with icon in top right and log in. This solved my issue, hope it helps anyone with the same issue.
MyanRagahis said:
Hello all!
Recently I've purchased the Swann DVR8-1425 security system.
I've been able to connect it to my home network successfully. I can remote view the cameras through my T999L (no root, completely stock) on WiFi through the SwannView app, but as soon as I put it into mobile data, it shows me a message of not being able to contact the server. I'm assuming if I were at someone elses house on their WiFi, it would be the same result. Same issue on my Dad's S2, rooted, running Infamous 3.0 in the T989 forums.
I've messed with most, if not all the settings I can possibly use with trial and error. When it comes down to it, obviously there's only the one setting that works with my WiFi (the given IP address from the DVR and a server port given: 9000) and it won't connect with mobile data whatsoever (2g, 4g, or LTE). I've tried using HTTP port 85 instead of the 9000, a preferred DNS server in place of the IP address, turning on and off UpNp (not really sure what that does). Absolutely nothing. Server connection fail each time when using mobile data.
I've disabled the firewall in hopes of it working, but I've had no luck. Haven't reset the router, assuming I just unplug and replug but other than that, I'm out of ideas. Not sure what else I can work on besides the firewall, if that even does anything.
The Swann software installed on my Mac does work, but haven't had a chance to test it somewhere other than my home network. It could work, but I wouldn't know at this point. Just more concentrated on the mobile data issue.
My knowledge is small when it comes to this networking stuff. Connecting to a WiFi hotspot is about as easy as it gets for me lol. I just got lucky with trial and error for setting it up with the home network. Just wondering if anyone has experience with this or ideas that may come to mind. At the worst, I won't be able to remote view anywhere other than using my wifi, but it will still record at least.
Thanks in advance!
Click to expand...
Click to collapse
Fix
Hello..
I am also using Lorex wireless security camera for my home but till now I am not facing any issue because all configuration is performed by experts. But I have two fixes for your issue.
Either contact with Lorex Support Team for help or follow steps:
Check with your mobile data service provider to confirm if they allow streaming of constant information over their network.
Configure a lower substream video resolution in your DVR / NVR settings to reduce mobile data usage and increase your connection speed.
If you cannot connect to your cameras using an LTE or IPv6 connection, switch to a 3G connection.
If you are using a device ID through your mobile plan, set up a Dynamic Domain Name System (DDNS) to eliminate the need to pass through the Stratus / FLIR Cloud servers.
Hope it helps!