Develop Bugs

[REQ] How To - Remote Desktop Mobile

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

[Q] Tinycam, IP webcam, and portforwarding

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)

[Q] help connecting to FireTV on different LAN subnet?

I have Private Internet Access as a VPN service, and I wanted to use that for my FireTV alone. So I have a second router in my LAN, which basically serves as a VPN filter for my FireTV. Everything else on my network goes through the first router. So it looks like this:
192.168.1.1 = main router
192.168.1.12 = my Macbook
192.168.1.111 = second (VPN) router's address on main network (I can connect to this from my Macbook and administer the VPN router)
10.0.0.1 = LAN address of VPN router
10.0.0.50 = FireTV IP address
So! My question is...how can I ADB connect to my FireTV from my Macbook using adbFire?

You could opt to disable firewall functionality on your VPN router, unless your main router has static routes to your VPN and open for certain ports from the WAN side. That should be the easiest option.
Or you can open specific ports used by ADB on your VPN router to allow inbound traffic to your FTV along with static route to the FTV. In this case, you will connect to FTV using the WAN IP of your VPN router and forward traffic at the designated port(s) to FTV
Or you can run a local hotspot on your FTV using an application like WiFI Tether Router (or even ES File Explorer) and connect your MAC to the router (that is FTV) and work like that. Note, this only works if your FTV is wired and thereby freeing up your wireless so that it can be used for client connections to it. And also, your MAC has to go wireless in this case. But it is a convoluted way to go that way.

Can someone test this for me on the Fire TV 2 (takes a couple of minutes)

FireTV 2 will not allow Custom DNS on WiFi (works on Wired)
Can someone please help verify this for me ... this problem has happened since day 1 when firmware was 5.0.2 ... I am now on 5.0.3.1 and the problem is still there.
Basically once you get to the screen where you enter the passphrase for Wifi - click on Advanced and enter a unique IP / Mask and DNS. Doing this on WIRED works - but not on Wifi. Basically, on wifi it pretends to accept it - but it does not stick.
Amazon says its not possible - which makes no sense since Apple TV / PS3 / Laptop all do that. I would understand if it did not allow it for both Wired and Wireless. But when it works for Wired but not for Wireless (both talking to the same DHCP) ... then its a bug.
You can test it by changing the Custom DNS to 8.8.8.8 and 8.8.4.4 (Official Google DNS) ... and then if it works - revert back to letting DHCP set it. Please let me know if it works for you.

Nobody can test this and help out a fellow FireTV user?

I did the test. It sticks. I used my own specific ip with the dns I set.

guiso98 said:
I did the test. It sticks. I used my own specific ip with the dns I set.
Click to expand...
Click to collapse
Thanks. I narrowed the bug down to it happening only when the DHCP server issues an IPv6 DNS address to the wireless adapter.

SmartDNS service doesn't work anymore after Fire OS 5.0.5 update

I am using a smart DNS service (such as unblock-us / unlocator) on my Amazon Fire TV as well as on a Fire TV Stick, in order to watch shows in my home country language, as I am currently living in Germany.
The DNS setup was done directly on the Fire TV Box, not in my router due to limitations from my internet provider. When I started with the DNS service, everything worked like charme from the start. But yesterday evening my Fire TV got the update by Amazon onto OS version 5.0.5 (before it had an OS version called 51.1.6.3.) From this moment on, the DNS service stopped working on the Fire TV.
Everything is still set up correctly, but I just get the German content, no matter what region I have set in my DNS Service account. No error message though. I tried to restart the device, deleted and re-added the network with the DNS settings and restarted again, restarted the router, but nothing helped. I haven't done anything different than before. So I am quite sure, it has to do with the OS update by Amazon. The Fire TV Stick in the other room still has the former OS version (54.1.2.3.). There, everything still runs smooth as it used to be as well on the Fire TV box.
Is anyone here facing the same issues with the new Fire TV OS 5.0.5? Does anyone know how to solve this or what I can do different, to make it work again?
Thanks in advance for your help.

same !!!
I have same prob since update today.. I was using overp*ay
Any luck getting it sorted thx

One way around is to get your internet provider to bridge their modem (if it is build into router) and buy a good router you can set-up using a custom DNS/VPN

I talked to the u*locator support today (Smart DNS Service I use). They say it's because of IPv6 that seems to break their service. Under settings → system → about → network, the DNS is not in IPv4 but IPv6 format. Apparently Android 5.1 (Fire OS 5.0.5) and my cable provider plus the Fritz!Box Router I am forced to use by them don't go well together in this combination. Former OS version was based on Android 4.2.2. - no problems. I found several reported issues in other contexts (smartphone wifi, smartphone push notifications, etc.) with the keywords IPv6 in combination of Android Lollipop, my ISP and the router I gotta use. So it seems I am unlucky with this combination.
So does anyone have a hint, what workaround options I have?
- downgrade to the former OS? How can that be done?
- would rooting and disable IPv6 on the Fire TV be a possibility?
- (bridging the modem as bula1ca said is unfortunately no option with my ISP)

I heard wired connections on the firetv box doesnt have this problem but im curious to know the fix because I have a fire tv stick

So I got a solution! Inspired by bula1ca's post, I am additionally using an old TP-Link Router now (TL-WR841ND), which doesn't support IPv6. No rocket science. I just connected the WAN Port of that Router with a free LAN port of my original Fritz!Box, set up a wireless network on that old router and changed DNS to my smart DNS service in DHCP settings. So now I have an additional wireless network that I only use with the Fire TV and my Fire TV Stick. Result: The Fire TV doesn't get a IPv6 DNS anymore, but only Ipv4. Works like a charme.

Whizzkid78 said:
So I got a solution! Inspired by bula1ca's post, I am additionally using an old TP-Link Router now (TL-WR841ND), which doesn't support IPv6. No rocket science. I just connected the WAN Port of that Router with a free LAN port of my original Fritz!Box, set up a wireless network on that old router and changed DNS to my smart DNS service in DHCP settings. So now I have an additional wireless network that I only use with the Fire TV and my Fire TV Stick. Result: The Fire TV doesn't get a IPv6 DNS anymore, but only Ipv4. Works like a charme.
Click to expand...
Click to collapse
Happy that worked for you however some modems need to be "bridged" before you can use your own router.

My router is a Fritzbox and I'm using it in bridge mode. I have simply disabled ipv6 support for the home network:
-DNSv6-Server in Home Network - DNSv6-Server through Router Advertisement (RFC 5006) - off
-DHCPv6-Server in Home network - deactivate
SmartDns is working again even over a Wlan connection. Other router brands might also have this possibility

I'm facing the same problem with IPv6/IPv4.
How do you connect WAN with LAN ports etc., and what else needs to be done how so that the FireTV can eventually work with an IPv4 address?

will2go said:
I'm facing the same problem with IPv6/IPv4.
How do you connect WAN with LAN ports etc., and what else needs to be done how so that the FireTV can eventually work with an IPv4 address?
Click to expand...
Click to collapse
See my answer above. You have to find a way to disable IPV6 DNS in your home network.
-You might be able to do it in your router settings
-if your router doesn't allow switching it off attach another hardware (router) to your WAN cable modem's port where it is possible to do so/or the router is an old pre-ipv6 model where it is off anyway.
Just connecting the firetv to a lan port won't help unless you have a special router setup

uzi74 said:
See my answer above. You have to find a way to disable IPV6 DNS in your home network.
-You might be able to do it in your router settings
-if your router doesn't allow switching it off attach another hardware (router) to your WAN cable modem's port where it is possible to do so/or the router is an old pre-ipv6 model where it is off anyway.
Just connecting the firetv to a lan port won't help unless you have a special router setup
Click to expand...
Click to collapse
I can't disable IPv6 since my ISP is just providing IPv6 addresses. If I disable that within my router, there's no internet connection.
How do I setup another router via WAN? That may actually work. Do you happen to have a step-by-step guide how to do that?
Thanks.

will2go said:
I can't disable IPv6 since my ISP is just providing IPv6 addresses. If I disable that within my router, there's no internet connection.
How do I setup another router via WAN? That may actually work. Do you happen to have a step-by-step guide how to do that?
Thanks.
Click to expand...
Click to collapse
You don't have to disable IPV6 completely, just for your home network (if your router supports it). - in case you get a dual stack IPV6 (you get an IPV4 and IPV6 address assigned the same time)
How to do it exactly, how to use a different router and what is possible for you, you would better ask in forums of your internet provider. (I had to request my internet provider to switch the router/cable moden they gave me to bridge modus, than I was able to hook up a different router on the LAN1 port of my cable modem - I needed it before for different purposes)
Your options are very much dependent on your internet provider and hardware you own, but basicly your goal is the have IPV4-only DNS on your home network

Not an option, sorry.

My router won't allow full disabling of IPV6 unfortunately.
I have just heard from unblockr.net a SmartDNS provider, and they suggest that it would potentially help to disable this.
My traffic is definitely being routed via their servers as I can connect to the DNS servers fine, but it won't unblock geoblocked content for a certain country I'm aiming for which is a shame.

johnsmithtetley said:
My router won't allow full disabling of IPV6 unfortunately.
I have just heard from unblockr.net a SmartDNS provider, and they suggest that it would potentially help to disable this.
My traffic is definitely being routed via their servers as I can connect to the DNS servers fine, but it won't unblock geoblocked content for a certain country I'm aiming for which is a shame.
Click to expand...
Click to collapse
What kind of router do you have that can't handle this simple setting?