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)
Related
Does anyone know how I can find out the mac address of my xda IIs ? I have a dreytek wireless router at home which uses a mac based access control list. I've tried the addresses that appear in wireless LAN manager ( BSSID and MAC ) but no joy. The only way I can connect is to switch off the access list feature completely
jeff
Hi Jeff,
Switch off the Access control, and let the XDA IIs join the wireless network. Then go into Diagnostic Tools --> View DHCP assigned addresses, and you will get a list of MAC addresses, IP addresses and hosts on the network. Match your phone's name to the MAC address.
Then you can turn access control on again and input the phone's mac address into the "allowed" list.
Thanks for the reply. I've kind of done that as you can see from the DHCP table below
DHCP server: Running
Index IP Address MAC Address Leased Time HOST ID
1 192.168.1.1 00-50-7F-23-97-CC ROUTER IP
2 192.168.1.10 00-00-00-00-00-00 BAD IP
3 192.168.1.11 00-0D-61-4E-A7-F7 0:00:04.600 hubbo
4 192.168.1.12 00-09-2D-0E-49-61 9:24:34.170
(not sure about that BADIP line ! )
I would say my MAC is 00-09-2D-0E-49-61 but it's still not working.... odd.
Is there no way that you can tell the MAC address from the phone without connecting to a network.
Here is a freeware that will allow you to find your MAC with no connection. I used it on my PDA2K.
http://www.freewareppc.com/communication/vxipconfig.shtml
Install on your device. Just turn the wifi on and run the program and it will give you the MAC and additional device info. Don't have the PPC connected to the USB or it will identify that device.
Sorted thanks, whilst in PC World I scanned for a Wireless network, and found three, hehe! Once connected used that utility to get my MAC.
Many thanks!
wifi and drayteck router
hi i see u have a draytech router how did u manage to get streaming video? i have been trying now for hours.I can get the video on my laptop without any problems but my m2000?????
i think the problem lies within the vpn settings as when i try to open http://house:8080 i get the message vpn connection required.
any help would be greatly recived (i have the vigor 2600g)
thanks in advance
delboy
Hi,
I'm experiencing a weird problem and please let me know if it's only my problem or there is some work around for it.
My phone is SX66 upgraded to 1.40 ROM + 1.13 Radio stack
I can connect Wifi fine whenever I have some phone signal (at work). Whenever I go home where the phone signal is weak then the WIFI couldn't get connected (I believe I set up my home network correctly as I've been using it for so long and configure it for several computer/laptop in house). The network could detect the AP with the SSID but I just couldn't connect to it even I'm sitting right next to the AP.
ROM 1.40
Radio: 1.13
MDD
Are you sure it isn't connecting? What has led you to this conclusion?
Is it possible that it is connecting, but that you just can't browse the internet, in which case check your connection proxy settings. If your work uses a proxy server and you've enabled the pass-through setting in ActiveSync, your network connection may be configured with your work proxy server.
If you're sure you're just not connecting however, things to check are;
WEP/WPA Encryption - If you're using it and have other wireless devices on your network, you no doubt know what to do. If not, say so & I can help you.
DHCP - Does your router/AP support Auto-IP Addressing? Is it enabled? If not, you'll have to configure the WiFi card with a static IP within the same subnet as your router. Ask if you need help.
MAC Filtering - Are you blocking unauthorised MAC Addresses (on your router/ap)?
Interference - Wireless A/V Senders and digital cordless phones are common culprits for RFI. 802.11x APs support multiple channels (most default to channel 11), and you can change these in case of interference. Once again, if you have other WiFi gear already connected with good, strong signals, you can probably discount this one.
Sorry if this is all elementary to you - I don't know how technical you are.
Thanks for your reply.
> Are you sure it isn't connecting? What has led you to this conclusion?
Yes, I've check wireless status on the phone. "Connected to the network", and the AP with DHCP on showed the status of an IP has been allocate to the SX66 mac address. However I dont' really believe it then I check the "Adater", it said network available, and the WIFI icon just didnot show any traffic.
> Is it possible that it is connecting, but that you just can't browse the internet, in which case check your connection proxy settings. If your work uses a proxy server and you've enabled the pass-through setting in ActiveSync, your network connection may be configured with your work proxy server.
I've experience once with the internet connection via Active Sync so I disable the passthrough. Both home and work doesn't have proxy server so I selected not to have any on the phone.
> WEP/WPA Encryption - If you're using it and have other wireless devices on your network, you no doubt know what to do. If not, say so & I can help you.
At work, I have 128 WEP and the connection works fine with the key. At home, I open my network but using MAC filtering to protect it. I have problem with the open network one at home. Perhaps, I will try to setup WEP at home and see if it can work.
The only thing I'm not really clear is the difference between setting "WPA" and "WPA-PSK" from the phone.
> DHCP - Does your router/AP support Auto-IP Addressing? Is it enabled? If not, you'll have to configure the WiFi card with a static IP within the same subnet as your router. Ask if you need help.
Yes, DHCP enable as I don't want to change it back and forth when traveling.
> MAC Filtering - Are you blocking unauthorised MAC Addresses (on your router/ap)?
I do it and I already opened the network and then captured the MAC address into the AP memory. (that's why I think it's connected but will check).
> Interference -
Not really, I'm 6' away from the AP and I don't have any cordless device in my computer room.
> Sorry if this is all elementary to you - I don't know how technical you
are.
No problem, I'd like to learn more about this PDA. The concept is about the same with PC, but the tools to debug is not there. I can't use tracert/traceroute, ifconfig or ping broadcast to really know if I'm the network.
Once again, thanks a lot.
Okay, well it sounds like you're on the right track & know what you're doing.
A useful troubleshooting tool, which gives you tracert, ping, whios, ipconfig and a host of other tools is "vxUtil", which is freeware. I'd give you a URL for downloading it, but I'm on my iMate now (sipping coffee by the Yarra in a Melbourne Cafe - oh what a techno-wanker am I!), but search these forums or Google it and you'll find it.
Now, regarding the proxy thing... These PPCs are a little tricky with their internet settings, and I had to create a different 'connect using...' connection profile, if that makes sense. The important setting within the profile, which is under the Proxy tab, from memory, is "This network connects to the internet".
Now for some reason, if you don't enter in a proxy server here, that check-box doesn't stay checked when you ok your way out. So what I've had to do is go into the advanced area & enter anything in the "wap" proxy, then ok out.
Strange, but it seems to work. Although I always leave my "Private network" on "My Work Network", I can now browse the 'Net through the WiFi AP/Router.
Download vxUtil & see if you can ping your AP, then go from there.
I've worked around the problem by using static IP address instead of depending on DHCP. Thanks to Hitchhiker software. I noticed that it was trying to obtain IP address from DHCP but failed. (The very same DHCP work wells for the rest of my network). Anyway, I will use Hitchhiker to switch IP back and forth if necessary.
Thanks a lot!
MDD
Great to hear you found the problem - well done.
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 cannot ping my IP while tethering on my phone. Is there a way to unblock inbound connections on the site, or is it a phone option? There are apps to do this, but they all say you need to be able to ping the phone, and I can't.
I use my phone's tethering as my main internet while at home (unlimited plan) but can't host any games because no one can connect to me.
Still not a thing? I can't ask anywhere else due to the post limitations.
While your computer is tethered to the Internet through your phone, what are the IP numbers of the phone and of the computer?
What IP number are you trying to ping, and whence?
jpradley said:
While your computer is tethered to the Internet through your phone, what are the IP numbers of the phone and of the computer?
What IP number are you trying to ping, and whence?
Click to expand...
Click to collapse
The current IP for all computers connected to my phone is: 70.194.2.149
Using that IP I cannot host any games. Though for some reason I can on PS4, so I have no idea what's going on there.
squat251 said:
The current IP for all computers connected to my phone is: 70.194.2.149
Using that IP I cannot host any games. Though for some reason I can on PS4, so I have no idea what's going on there.
Click to expand...
Click to collapse
Every ethernet port, wired or not, has an IP address. Two devices cannot have the same IP address, each address on a network has to be unique. 70.194.2.149 is the (public WAN) address of a single device, probably that of the incoming port of your router. Your computers each have their own IP numbers (typically in the 192.168.x.y numbering scheme). Your router also has an address in that same number range, for use on its inside (private LAN) ethernet connections.
I don't want to write a dissertation on NAT (network address translation), but that is what the router performs so that your browsers or your Telo "appear" to be coming from 70.194.2.149. Net result,as far as your computers are concerned: they can call out, intitiate a connection to wherever, but nothing can initiate any contact to them from the outside world (short of doing some "port forwarding" in the router). Look up NAT iand port forwarding in a search engine.
BTW, what is "PS4"?
jpradley said:
Every ethernet port, wired or not, has an IP address. Two devices cannot have the same IP address, each address on a network has to be unique. 70.194.2.149 is the (public WAN) address of a single device, probably that of the incoming port of your router. Your computers each have their own IP numbers (typically in the 192.168.x.y numbering scheme). Your router also has an address in that same number range, for use on its inside (private LAN) ethernet connections.
I don't want to write a dissertation on NAT (network address translation), but that is what the router performs so that your browsers or your Telo "appear" to be coming from 70.194.2.149. Net result,as far as your computers are concerned: they can call out, intitiate a connection to wherever, but nothing can initiate any contact to them from the outside world (short of doing some "port forwarding" in the router). Look up NAT iand port forwarding in a search engine.
BTW, what is "PS4"?
Click to expand...
Click to collapse
Playstation 4. All of my PC's connect to the internet through my phone. There is no router, there is no ethernet. They all share the same IP because that is the IP of my phone (my best guess.) That is why all the targeted ads are from the same town. I don't know where in my first post, or any there after you gathered that I am having issues with a router.
squat251 said:
Playstation 4. All of my PC's connect to the internet through my phone. There is no router, there is no ethernet. They all share the same IP because that is the IP of my phone (my best guess.) That is why all the targeted ads are from the same town. I don't know where in my first post, or any there after you gathered that I am having issues with a router.
Click to expand...
Click to collapse
Ah, OK. Then it is your phone which is acting as a router and is doing the NAT procedures. I don't know how to make a phone forward specific IP ports to specific IP addresses.
You need a port forwarding app to allow incoming traffic to reach the right device on the network.
Forward what ever port(s) your game uses from the public wan ip to the game consoles ip provided by the phone.
So lets say forward port 1234 (or all ports) to 192.168.1.10, or what ever the game consoles ip is.
cmlusco said:
You need a port forwarding app to allow incoming traffic to reach the right device on the network.
Forward what ever port(s) your game uses from the public wan ip to the game consoles ip provided by the phone.
So lets say forward port 1234 (or all ports) to 192.168.1.10, or what ever the game consoles ip is.
Click to expand...
Click to collapse
That would work, only all the port forwarding apps require that you be able to ping your public IP. I cannot, all packets are lost no matter what method I use. I would call and ask Verizon, but I have unlimited data, and there is no way I will let them weasel that out of me.
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)
You need your "WAN" (Wide Area Network or Public) address of your router to reach it. But you need a little more than that.
You will usually see this address displayed somewhere on the router (home status page or something it won't be 192.168.x.x).
Get a router that supports dynamic dns (DDNS), most do these days.
ASUS is the easiest to setup. You just pick a sub domain like fredsplace and then you can reach your router through fredsplace.asuscomm.com (no account or anything needed).
fredsplace.asuscomm.com will always have your WAN address which is dynamic and can change.
Then you would use fredsplace.asuscomm.com in your app, not 192.168.x.x.
You'd also have to tell your router to route port 80 (port forwarding) to your cameras IP address in the house.
Typically I use a different port like 8081 (set in your app and the router) and then route 8081 to Port 80 192.168.1.105 (e.g. your camera).
The reason is port 80 might be used by the router itself for it's web interface.
Also 8081 won't get sniffed by bots/malware etc.
On some routers you might have to also tell the firewall in the router to allow port 80 (or 8081) through (I don't think I needed to on an ASUS AC68u it's an implicit firewall rule when you port forward it).