Windows Phone 8 emulator can't connect to the internet

Question

I have Windows 8 installed inside of an emulator, and the new WP8 SDK installed on it. My problem is that the emulator can't connect to the internet. I don't have any proxy, and even disabled the firewall. It still doesn't seem to work though. When I look at the Network Connections sections I can see the new connections the hyper-v manager created for the emulator, and also the automatic bridge created, but even there the network status is "No Internet Connection".

Are there some properties I can manually change in Hyper-V or for the network to make everything work?

Update: I've done everything suggested including create my own switch and delete all others. It still doesn't work however. It doesn't work on cable and not on wifi. Maybe I'm missing something with how to set this up?

Also the WP emulator keeps offering me to connect to the internet every time. It always erases all of the definitions I've set up, replacing it with it's own definitions.

Answer 1

I had the same issue as well. However as someone else pointed out on the official forums it didn't work if you had a static IP for your PC set up in your router. Removing it and let the DHCP assign my PC an IP solved the issue for me.

Source

Answer 2

I think I've finally found the answer, but you're probably not going to like it. It would appear that the phone emulator requires you to have a second network adapter to dedicate to this purpose. Personally, I run Windows 8 in VMWare, and so a second network adapter is free for me.

Anyway, after you get the second network adapter that you can dedicate for the phone emulator(must have internet)

1. Start from scratch. Go to the Hyper-V manager and delete the emulator along with all of the virtual switches
2. Start the emulator from Visual Studio; this will recreate it with all default settings(select yes you want to configure it to connect to the internet)
3. Shut it down
4. Now, go back to the Hyper-V manager
5. Delete the snapshot that was just created for the emulator. This will prevent your changes from disappearing
6. Find the virtual switch for your second network adapter in the Network Adapter settings(under control panel)
7. Disable TCP/IPv4, 6 and all other services. This prevents your host machine from trying to use the connection. While you're there, get the MAC(Physical) address of this adapter
8. Find the virtual-switch for your second network adapter under the Hyper-V settings for the emulator
9. Change the MAC type to static and paste in the MAC address of the adapter
10. Enable MAC spoofing (not sure if required, but just in case)
11. Then, find your virtual switch under "Virtual Switch Manager".
12. Ensure "Allow management operating system to share this network adapter" is unchecked and that all extensions are disabled
13. Click OK and then start the emulator from Visual Studio!

Basically, it appears that for some odd reason it won't properly work unless the phone has the same MAC address as the network adapter. However, we can't just set it to use the same MAC address because address conflicts are very very bad. So, we need a second adapter that we can dedicate to the Phone emulator. The reason we disable TCP/IP on this adapter is so our host machine doesn't use it and cause these conflicts.

Other things to try:

The emulator keeps randomly breaking for me. I'll list a few other things I messed with this last time that got it to work(not sure if related, so only try these if the steps above aren't working

• "Reordering" of network adapters for the emulator so that the external virtual switch is at the top (make sure to copy over the MAC address for the internal adapter)
• Removing unrelated network adapters
• Restarting your machine after recongiguring virtual switches
• Praying to your local Microsoft evangilist

Seriously. Everytime I stop phone work for a while and come back, the emulator is always magically broken without me changing anything. No idea how to get it to work "permanently".

Answer 3

Here's what worked for me:

1. Go into the internal network connection created by hyper-v in network connections on the host computer. Go to TCP/IP V4 and go to advanced. Change the metric from automatic to 10.
2. Go to the external network connection, do the same but set the metric to 1.

Volia, internet in the emulator.

Answer 4

I tried following steps , Not sure if it will work for you

1> Delete All emulators in Hyper-v
2> Remove all virtual switches from virtual switch manager
3> Go to Network connections in control panel and manually disable (right click and click disable) all the connection except the one which provides internet.
4> Start the emulator from Visual studio

Answer 5

Something else that seems to also cause an issue is Fiddler.

I had Fiddler open and running (as I was monitoring other HTTP requests), and it was stopping the emulator from connecting.

As soon as I closed Fiddler, the emulator starting connecting perfectly.

Answer 6

1. Start Hyper-V Manager
2. Open Virtual Switch Manager
3. Remove the Windows Phone Emulator Internal Switch from the list and apply changes

Answer 7

After installing Windows Phone Emulator on my Yoga laptop, I immediately had the following problems:

• emulator apps cannot reach the internet
• host computer internet connection is terribly slow and almost unusable

I was discouraged and thought I would have to do some drastic and desperate acts to fix things, but got lucky with the following steps which completely solved my problems (for now). The steps are verbose (intended for the readers' benefit), but are actually very simple in practice.

....0: Unplugged ethernet cable (to remove it from the equation) but stayed connected to WiFi. Problems still remain but at least there is less complexity now.

....1: In Control Panel / Network Connections / Change Adapter Settings, deleted Network Bridge (required for Step 2 to work).

....2: Opened Hyper-V Manager, right-clicked on the emulator VM item and selected Virtual Switch Manager. Selected "Windows Phone Emulator Internal Switch" and changed the radio button from Internal to External (this was only possible after deleting the Network Bridge (Step 1)).

At this point, the emulator can now connect to the internet (and Control Panel shows WPEIS finally 'has internet access'); however deployment of WP build binary from VS to emulator fails - it just hangs when I try to build-and-deploy from Visual Studio (so a new problem has surfaced (temporarily)).

....3: Returned to HyperV Manager, went back to Emulator VM's Virtual Switch Manager and reverted Windows Phone Emulator Internal Switch from External back to Internal.

I can now successfully build-and-deploy WP build from Visual Studio to emulator. And emulator retains its networking ability. Also the host machine's network connection also returned to healthy.

I hope this helps someone. Good luck!

Answer 8

I went through many of the suggested solutions, also with no luck. What finally worked for me was to fix a vmware warning about guest OS trying to set promiscuous mode for ethernet adapter (http://kb.vmware.com/kb/287).

Answer 9

Try this solution, it works for me (no need of DHCP)

Step 1 - using Hyper-V start the server, once started u can see the two new network adapters added in the (network sharing) page.

Step 2 - go to your visual studio IDE where your application runs, using Emulator run your application, once started try to open IE, it will not connect to internet.

Step 3 - now again come back to network sharing page right click on external adapter which was created newly select properties, hit on sharing tab, now check the two options to have tick mark if not tick that two options and click on OK.

Step 4 - internal adapter which was created newly will be changing the domain name from Unidentified network to your shared Domain name, once changed try to access the IE again in emulator which runs already. now i hope the internet connection works.

Thanks,

Baskar

Answer 10

After spending about 3 days on this i finally got it working. (on Windows 8 using WiFi)

1. Start Fresh, Remove HyperV, Restart, Install Hyper V, Restart
2. Open your VS solution and run the emulator.
3. When prompted for letting the emulator access the internet say yes.
4. Let the emulator and your project fully load
5. Shut down the emulator and VS
6. Open Network and Sharing Centre
7. Click change Adapter Settings (on the left hand side)
8. You should have some new adapter created by HyperV, they should be called "vEthernet(...)"
9. The ones you are interested in are the vEthernet( Virtual Switch) and vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch)
10. Open the properties on your vEthernet( Virtual Switch) and navigate to the sharing tab.
11. Choose Allow other Network users to connect and choose the vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch) as the adapter
12. Ok the changes, and then open the properties on vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch)
13. Disable Internet Protocol Version 6 and double click on Internet Protocol Version 4
14. Use the following IP address: 169.254.169.177 Subnet mask:255.255.0.0
15. Click advanced, under the IP settings tab, assign an interface metric: 1
16. Open VS and re run your project under and emulator, wait a few minutes for it to load.
17. Try and open IE within the emulator and confirm you have internet access.

Good luck

Answer 11

After 3 days we have finally solved it. We had to make ip address dynamic. After making it dynamic emulator could reach internet. We didn't have to change anything else.

Answer 12

Good article: http://blogs.msdn.com/b/wsdevsol/archive/2013/10/01/why-can-t-the-windows-phone-emulator-go-online.aspx

I had DHCP reservation on my router, like @robertftw said. I configured a static IP for vEthernet (Internal Ethernet Port Windows Phone Emulator Internal Switch) adapter and everything works.

Answer 13

Disabling the Wifi, and Virtual Wifi inside "Network Connections" worked for me.

Answer 14

My Windows Phone emulator had been assigned an IP address by DHCP on a different Subnet to the one I am using.

Manually assigning an IP address on the same subnet as my PC to the vEthernet port created by Hyper-V resolved this issue.