How to prevent Android Studio / AVD error messages "CANNOT TRANSFER Guest DNS-IP"?

About every 4 seconds after starting the emulator device from my Android Studio project, an error message is displayed in the Run window. This is very annoying because it captures the focus. If I'm in the debug window, it switches to the Run window every 4 seconds due to this error, regardless of what I do.

It started a day ago, but I don’t know what caused it. I have been using the same emulator devices for several months now. Maybe updating some part of the Android SDK? The external SDK Manager is no longer called.

enter image description here




Messages begin to arrive immediately after loading this API 25 wear emulator. One of the workarounds is to make this tab float, then it will not intercept my focus; I transferred it to a second monitor.




I also noticed that I can’t connect the Android Wear app running on my physical device (I use a physical phone with emulated wear) with my emulator.

+77
android-studio avd android-avd
Mar 01 '17 at 8:15
source share
2 answers

Maybe this can help:

  • Please make sure you are connected to the Internet.

Explanation: At startup, the emulator reads the list of DNS servers that are currently used by your system. Then it saves the IP addresses 10.0.2.3 four servers in this list and sets them aliases for the emulated addresses 10.0.2.3 , 10.0.2.4 , 10.0.2.5 and 10.0.2.6 as necessary. Thus, he needs an Internet connection to deal with them.

When starting the emulator at the command line, you can also use -dns-server to manually specify the addresses of the DNS servers used, where serverList is a list of server names or IP addresses separated by commas.

0
Dec 27 '17 at 7:05
source share

This is because you are connected to a network that has automatic redirection, or it is not encrypted (HTTP). Begin with

  1. Disconnecting yourself from the network.
  2. Restart Android Studio

If the problem persists, try posting a more detailed description of the error. If the problem persists, contact your network administrator.

0
Mar 02 '18 at 3:59
source share



All Articles