Connecting with IPv6 in Windows 8

With World IPv6 Launch upon us, we thought it would be good to provide a look at the work in the Windows 8 Release Preview supporting IPv6. Christopher Palmer on the core networking program management team authored this post.

IPv4 is the Internet Protocol that has been used for Internet connectivity for decades. However, IPv4 was never designed for such load and scale, and it is beginning to show signs of strain as the Internet grows—even though the incredible foresight of the original designers continues to power the Internet at a massive scale. Internet service providers are finding IPv4 increasingly costly to maintain; it will require an overhaul to sustain the upcoming onslaught of connected PCs and devices.

For several years, the industry, including Microsoft, has been working to roll out a completely new version of the Internet Protocol – IPv6 – across various devices, services, and network infrastructure. Windows releases since Windows XP SP3 have supported IPv6, making the IPv6 transition possible. We have engineered Windows 8 to keep you (and your apps) reliably connected as this dramatic transition takes place.

The limitations of IPv4

First, let’s cover some basics. Every time you browse to a website like, that friendly name gets turned into an IP address, something like An IP address is conceptually similar to a telephone number. Just as all your contacts have telephone numbers, everything that connects to the Internet has one or more IP addresses. The “telephone directory” for the Internet is the Domain Name System (DNS). Given a name, DNS resolves the name to a set of IP addresses.

IPv4 only provided around 4 billion IP addresses. That seemed like a lot in the 1970s. But by 2015, an estimated 15 billion devices will be connected (PCs, phones, household appliances, cars, even furniture!). IPv4 simply does not have the addresses necessary to connect this many devices to the Internet.

As demand for IPv4 addresses has grown in recent years, the Internet community has found ways to “share” those vital resources. The most common way to share an IPv4 address is to use network address translation (NAT). This functionality is in most home routers, enabling computers and other devices in a household to share a single public IPv4 address.

Conventionally, ISPs provide a single IP address to each home. However, that is becoming increasingly difficult. Because of IP address depletion, unique IPv4 addresses simply aren’t available for each home. Soon, whole cities or countries may be behind large-scale network address translation. Internet service providers have to develop costly and complex infrastructure to continue to support IPv4. For end users, IP address exhaustion means that location-based services, such as Bing, will not work properly, and peer-to-peer applications will face degraded performance.

IPv6 is the future

Microsoft, along with other technology companies, has been working on the deployment of IPv6 to ensure that end-users continue to have high-quality Internet access, despite the performance and connectivity limitations brought about by IPv4 address exhaustion.

The most immediate benefit of IPv6 is that it provides more than 3×1038 IP addresses, enough for every person to have billions of addresses all to themselves, or enough to give every star in the universe a unique address. This will allow the Internet to grow and evolve. IPv6 also provides for many security and performance improvements, like built-in support for IPsec. (What happened to IPv5, you ask? Bing can help you find out why it’s being “skipped.”)

Upgrading the entire Internet to IPv6 isn’t something that can be done instantly. It has taken many years to get to where we are today, and we still have many years of work to do. Currently, around 1% of devices can connect to the Internet using only IPv6.

During the transition period, most networks will fall into three categories:

  • IPv4-only networks. This is probably what you have today, as most Internet Service Providers have only just started rolling out IPv6 support. Many devices that connect to the Internet might only support IPv4 as well.
  • IPv4 and IPv6 networks (dual-stack). This means your Internet Service Provider is configuring your PC with both IPv4 and IPv6 addresses. This model is common in cable and dial-up networks that are transitioning.
  • IPv6-only networks. This means your Internet Service Provider is configuring your device with only IPv6 addresses. Because many websites are still only on the IPv4 Internet, ISPs must use a translation device to allow access from your IPv6 network to the IPv4 Internet. This device is called a NAT64. This mode is becoming popular in the mobile environment, because having only one kind of Internet Protocol between the mobile device and the operator’s infrastructure is simpler to deploy and cheaper than a dual-stack configuration. Also, mobile operators are feeling the IPv4 address exhaustion pinch most severely. Here is a basic diagram of this configuration:

The router for IPv6-only devices connect to IPv4 Internet via NAT64

You might be wondering what kind of connection you have right now. We have a widget at the bottom of this post that can show you.

Windows 8 is designed to ensure connectivity across all types of network configurations. In Windows 8, you can launch DNS look-ups using the Resolve-DNSname cmdlets in Windows PowerShell. Open up PowerShell and run the below command, and you will see both IPv6 and IPv4 records returned. Only websites that support IPv6 will have IPv6 records.

IPv6 and IPv4 records

Windows 8 on IPv4-only networks

On an IPv4-only network, devices are configured with IPv4 addresses only. This model continues to work in Windows 8 as it has in the past. In addition, Windows hosts also provide IPv6 connectivity by tunneling that traffic inside various transition technologies – an example of which is Teredo, where IPv6 packets are encapsulated in IPv4 UDP packets. Now that we are starting to see the emergence of IPv6-only servers and services, Windows 8 automatically attempts IPv6 connectivity when the server does not offer an IPv4 address. Note that Teredo is enabled by default only on non-domain networks, and Teredo may not be available if your network blocks UDP.

Windows 8 on dual-stack networks

During the transition period, dual-stack networks will be the common deployment model. On a dual-stack network, devices will be configured with both IPv4 and IPv6 addresses.

Our primary focus during this transition has always been to minimize the impact of the transition for everyday users. It shouldn’t matter whether your connection is over IPv4 or IPv6. You should have an Internet experience that is fast and reliable, with little evidence of the IPv6 transition, so you can just enjoy the content.

At the same time, it’s also a priority for us to help the IPv6 transition move ahead. To this end, Windows prefers native IPv6 connectivity over IPv4 connectivity, if both connection modes are available.

In summary we have the dual goals of ensuring a reliable user experience, and enabling the IPv6 transition. As you might imagine, this can sometimes involve subtle tradeoffs, which have been the subject of much debate in the Internet community.

In an effort to sort out those sometimes competing goals, major websites around the world--including,, and–organized an event called World IPv6 Day last year. During this one-day test of the IPv6 Internet, participating websites turned on IPv6 in addition to IPv4.

The good news is that most things worked. All that goes into the Internet’s correct functioning—servers, end-user devices, and content delivery networks—were able to work at scale without issue.

However, we also observed that a small subset of the population (0.01% of the world) was misconfigured with IPv6, seemingly because of a router or ISP issue. That’s not too surprising, as IPv6 is a fairly new technology, and mistakes happen. But for those unlucky users, it could cause a significant impact on everyday experiences with the Internet.

Engineering resiliency into our connectivity algorithms for dual-stack networks

In order for a device to truly support dual-stack networks, apps must not only be able to send traffic with IPv4 and IPv6, but the OS must be smart enough to know which protocol is appropriate for the task at hand. Even more specifically, because your device might have multiple IPv4 and IPv6 addresses, and because the destination you’re trying to reach might also have multiple IPv4 and IPv6 addresses, the stack must be smart enough to know which specific source and destination addresses should be used for connectivity. This functionality is called address sorting, and is an area that we have enhanced in Windows 8. The idea behind address sorting is to determine which address pair is likely to produce the best connection, so the application does not need to wait.

When Windows tries to connect to a dual-stack website, Windows sorts through its own and the website’s IP addresses to decide which pair it should use to make the connection. (For standards buffs, address sorting is standardized in RFC 3484.)

Below is a diagram showing how Windows uses address sorting.

1 - App requests connectivity to 2 - Windows sends out DNS queries to resolve into IP addresses. 3 - Windows sorts the responses of the DNS server using an algorithm defined in RFC 3484. 4 - Windows connects to the web server, using the first address in the sorted list.


Traditionally, address sorting relies on Windows being correctly configured by your router. Windows analyzes the routing information provided by the router and uses that information in conjunction with address sorting to ensure fast connectivity to named resources. The RFC 3484 standard specifies that IPv6 should be preferred if IPv6 is configured by your router.

World IPv6 Day showed that some clients were configured with IPv6 routing information, but they did not actually have IPv6 connectivity to the Internet. This appears to be the result of a misconfiguration by some Internet Service Providers or buggy home routers. Windows attempts to connect to websites using IPv6, expecting it to work, but it won’t! Eventually, Windows detects that the connection attempt failed and falls back to IPv4 connectivity. However, for users, connectivity to dual-stack websites can be delayed by 10-15 seconds. This obviously causes a problem for web browsers, but any network-connected app faces this issue.

As we looked into engineering a solution to this problem, we had to consider a couple of important issues. First, many enterprises deploy complex routing topologies. We had to make sure that our change did not break connectivity in these environments. Second, we needed a solution that worked not only for Internet Explorer but also all the other apps that are relying on Windows to help them connect to network resources. Those apps rely on us to remain intelligently connected throughout the IPv6 transition. Our solution needed to address the needs of existing desktop apps as well as new Metro-style apps.

Windows 8 tests IPv6 connectivity when you connect to a new network that advertises IPv6 routabilty, and it will only use IPv6 if IPv6 connectivity is actually functioning. This approach is a modification of our implementation of RFC 3484. Instead of sorting addresses as a result of policy, we use the actual state of the network as input to our algorithm. On a misconfigured network, this approach improves the experience not only for browsers but also for apps that connect to dual-stack destinations using standard Windows APIs.

Windows 8 performs the network connectivity test when you first connect to a new network; it caches this information and repeats the test every 30 days. The actual test for connectivity is a simple HTTP GET to an IPv6-only server that is hosted by Microsoft. (For standards buffs, this is implemented between rules 5 and 6 of destination address sorting in our implementation of RFC 3484.) Windows performs a similar network connectivity test for IPv4 connectivity. If both IPv4 and IPv6 are functioning, IPv6 will be preferred.

To make sure that Windows 8 does not cause problems on enterprise networks, the functionality has two safeguards:

  • If the enterprise has provided specific routing information to a particular destination, then Windows 8 will honor that preference, regardless of the connectivity determined by Windows. In enterprise environments, Windows assumes that network administrators who configure such routes specifically thought it was a good idea to use those routes.
  • This change isn’t implemented on networks with web proxies. In these networks, the proxy provides connectivity to the Internet; so end-to-end testing of IPv6 connectivity is not useful. Instead, Windows 8 simply opens connections to the proxy in the most efficient manner possible.

In this way, we’ve ensured that apps and experiences on Windows 8 can remain reliably and speedily connected to the Internet throughout the IPv6 transition, even if your local network is misconfigured.

Ready for the future of IPv6-only networks

On an IPv6-only network, the best way to improve a user’s experience is to increase the number of services and experiences that are available over IPv6. On such a network, access to the IPv4 Internet is through a NAT64. These devices can be a fragile point of failure for connectivity, and can have severe performance limitations that lead to dropped packets. They also break IPv4 peer-to-peer connectivity, needed for some multiplayer games.

Across Microsoft, we have done a lot of work to enable the growth of IPv6 deployments, both in enterprise and Internet settings. One of our most important efforts is to ensure that our server products support IPv6. IPv6 support is part of our Common Engineering Criteria (CEC). This is part of a broad company-wide commitment to customers that our business products, such as Exchange Server and SharePoint, support IPv6 in either dual-stack or IPv6-only configurations. Most Microsoft products built since 2007 have supported IPv6, but you can find out about IPv6 support in other Microsoft products on Technet. Through this effort, developers and solution providers can support IPv6 in their own products.

World IPv6 Launch Logo

Microsoft is also working on IPv6 support for our own services. Earlier this year, the Internet Society announced the World IPv6 Launch, a major milestone in the process of upgrading the Internet to IPv6. In June, Bing and other websites will start serving traffic over IPv6 on a permanent basis. Hardware vendors are working on IPv6 support in home routing devices, and many ISPs will start large-scale deployments of IPv6. CDNs (content delivery networks) have also started enabling support for IPv6 within their networks.

With the release of Windows 8, some of our infrastructure services will deploy IPv6 support.

Windows Update is a critical service providing ongoing support and updates to millions of users every day. More and more PCs are going to be connected to mobile broadband networks, where IPv6-only is a popular configuration. We have to make sure that downloads are reliably available to you on those networks.

For this reason the Windows Update service now supports both IPv6 and IPv4. Windows Update utilizes CDNs for worldwide distribution of updates and we are partnering with them to enable IPv6 support. Windows 8 will use IPv6, if available, to download Windows Updates so that users always get the best possible connectivity when downloading updates.

We are working with CDNs to extend IPv6 support beyond Windows 8. Once that work is complete, even Windows 7 and Windows Vista will automatically use IPv6, where it is available, for connecting to Windows Update.

Leading the way

Windows 8 is connected and ready to use, and our support of IPv6 is a key part of ensuring that connectivity for years to come. Because IPv4 wasn’t designed to handle the scale of connectivity today, the Internet is undergoing a radical change in its foundation. Every connection to every website, every multiplayer game, and every video call will gradually move to IPv6.

As part of that transition, Microsoft is leading the way by ensuring that Windows 8 provides the most resilient connectivity to the Internet while providing IPv6-ready products and services.

- Chris

Note: Several sections of this blog post were missing from the original publication. The missing sections were added several hours later. Apologies for the error.

Comments (117)
  1. NoCustomerAnymore says:

    Metro sucks on Desktop!

  2. Untitled says:

    I <3 IPv6 in Windows 8.  I tossed Customer Preview on an old Dell 910 mini yesterday, runs great!

  3. 600p says:

    Metro sucks on Desktop! +1

    Everybody who agree … to post the same comment.

  4. 8r13n says:

    Will we get static IP addresses on the cheap now?

  5. Metro Fan says:

    Metro rocks on the desktop. Metro is the greatest UI innovation of all time. It's beautiful, productive, modern, fast and fluid. Classic desktop sucks.

  6. steve says:

    this is great information.  Can it be explained why direct access was working in the consumer preview and does not work now with the release preview?

  7. Darren says:

    Metro sucks on Desktop! +1

  8. 600p says:

    Metro rocks on te Deskstop !

    sorry for my last Post…


  9. Oguz says:

    Metro rock on desktop. I am very excited with Windows 8 a new breeze, a new way of doing things. I really like it all.

  10. Darren says:

    Metro rocks on te Deskstop !

    sorry for my last Post…

  11. nazgul says:

    it's not about this post but i would know if the magic trackpad and other multitouch trackpad will work with multitouch gestures in windows 8

  12. I can't wait for the release of Windows 8 :) says:

    Windows 8 is so beautiful and powerful!

  13. theipv6guy says:

    Keep up the great work on deploying IPv6, this is the future of the internet and innovation

  14. Trolls…

    By the way, great post as usual!

  15. kudo says:

    One question. Why Windows have the IP Helper service ? I used to disable it all the time because IPv6 is still not used a lot.

    It is not something that you can have without a service ?

  16. jeroen says:

    The funny thing is that the trolls showcase their complete misunderstanding of the relation between metro and the desktop.

  17. offtopic says:

    The help section is missing in Windows Taskmanager, bring it back please…/taskmanger.jpg

  18. Darren says:

    @jeroen: Not as funny as Microsofts sad attempts to praise this sh*tty Windows 8 os.

  19. Max says:

    Metro sucks on Desktop! +1  It's horrible and people with epilepsy probably will die when using Windows 8

  20. Myrddin Emrys says:

    Slight error in your post; the Earth alone contains about 10^50 atoms.…/mathatom_05.html

    Also, I suspect the writer does not read XKCD regularly. 🙂

  21. Max says:

    Metro rocks on the Deskstop !

    sorry for my last Post…

  22. @Darren

    Is "Deskstop" referring to the removal of the start button? Actually, that's quite fitting.

  23. @Myrddin Emrys

    That's funny. I guess we will have to wait to index every atom in the universe.


  24. TMG says:

    Forefront Threat Management Gateway (TMG) and Unified Access Gateway (UAG) do not support IPv6.  Will they ever?  Are these dead products now?  Rather strange for your perimeter products not to support IPv6…

    (Btw, replacing the normal Start button with a hidden-in-the-corner Start button is a big mistake.  This is a different issue than Start Menu vs. Start Screen.)

  25. raymond says:

    zune is a better name xbox music is kinda blah sounding. But it would be even better to put all their stuff under one store/marketplace and such. Where we can download apps, music, video, xbox games. Basically they should rebrand the zune software and add those categories. xbox music is a horrible name choice though. Zune was nice and simple.

  26. raymond says:

    also should make some under the hood changes for zune software so it's not sluggish.

  27. w8 manco li kani.iettalo intu cess.... says:

    It's a disgrace.It's a disgrace.

    Metro sucks on Desktop! +10000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

  28. Mark says:

    Really good information – thanks!

  29. Entegy says:

    So we have an interesting article about engineering the Internet and what, like 2 of them actually refer to the topic at hand as of my posting?

  30. DavidRa says:

    I'm with TMG. Where's the support for IPv6 in the perimeter gateways? Is there some unannounced TMG/UAG 2013 product line or a new service pack to finally enable IPv6? I feel it was a travesty not having it on release a couple of years ago; claiming that most current products are IPv6 ready and not acknowledging this gaping hole is just ridiculous.

  31. Darren says:

    @jeroen: And while you keep laughing your *ss off, you probably did not realise that you cannot escape Metro even on desktop. Just to name the annoying charms. This is the problem of W8: You cannot get the desktop without Metro. Maybe you understand now.

  32. @Steve

    DirectAccess is one of a number of features that requires Windows 8 Enterprise.…/introducing-windows-8-enterprise-and-enhanced-software-assurance-for-today-s-modern-workforce.aspx


    In Windows 7, The IP helper service configures the in-box IPv6 transition technologies, like Teredo and ISATAP. In Windows 8, the service operates some of the power-saving networking features for metro-style apps. So even if you don’t use transition technologies, it’s really not something that should be disabled.

    @ Myrrddin Emrys

    You’re right actually, IPv6 can be used to provide addresses for all of the universe’s stars, not atoms. Thanks for this, I’ll update my post!

    The XKCD comic is quite popular at Microsoft. However, we’re more focused on the positive benefits of IPv6 like better performance and security, rather than the possible risk of a nanobot takeover. 🙂

  33. hamakaze japan says:

    Although it was a Japanese person, and the very last measurement came out, the net service using my home corresponded only iPV4.

    Is a previous version also arranged in Windows 8?

  34. pmbAustin says:

    "it's not about this post but i would know if the magic trackpad and other multitouch trackpad will work with multitouch gestures in windows 8"

    In the release version, yes.  Gestures will be supported on trackpads and magic mice.  I understand you can get that support from the Microsoft Touch Mouse with the Release Preview if you download the updated drivers and install them.

  35. UnhappySystemAdministrator says:

    Your new UI on the server is horrible! I took me 5 minutes to open prompts and I never found out how to log off. 🙁

  36. kudo says:

    @Christopher Palmer

    thank for the info about the IP helper service. I think that you need to update the description of this service with what you told me. In services.msc it still show about in-box IPv6 transition technologies…

  37. Future Apple customer says:

    Metro…. Metro…. Oh MEEETRO……


  38. StevOZ says:

    Keep to the topic people. June 6th is World IPv6 Day, so go grab a copy of IPv6 third edition ;-0.

    Oh and by the way, the more I use Metro the more I love and this is coming from a once-anti-Metro user.

    The traditional desktop is sooooo boring and outdated.

    Something exciting and new from Microsoft at last.

  39. xpclient says:

    Why doesn't Windows support RFC 6106 and when will it support it? Linux already does and it is better than DHCPv6 IMHO.

  40. reseul says:

    Wasn't the first supported IPv6 stack in "Windows XP SP1 with Advanced Networking Pack" ?

  41. Keyboard says:

    Metro sucks on the desktop! +1

  42. Abhishek Gupta says:

    Hi Steven,

                 I am having a doubt that. Since CP and RP of Windows 8 , MS launched CP and RP of Visual studio 2012 too, by introducing greyed icons there in visual studio so now again there is mismatch between the theme of SQL server management studio 2012 and Visual studio 2012 . I think when SQL server 2012 was in development you people may know that your are going to change the theme of Visual studio product so now here is big mismatch between the theme of both Visual studio and SQL server management studio while splash screen of sql server management studio says " powered by visual studio ".       May i m commenting on wrong blog but I think Steven is most appropriate person to whom we can talk about multiple products rather than windows 8 specifically.

  43. Keyboard says:

    Sorry for my last comment…

    Just want to say Metro rocks an the Deskstop! + 50000000000000000000000000000000000000000000000000

  44. Bob says:

    Show some class people. Microsoft should turn off comments. Too many children ruining the discussion.

  45. My biggest concern with IPv6 is that a lot of consumer kit has not been tested properly with it, or simply doesn't support it at all. And ISPs are going to be reluctant to switch to IPv6 if they break consumers so they'll have to do some dumbed down hybrid model. They probably also have enough IP addresses already so it's not like they have a problem which actually needs fixing. This immobility all cascades up the chain and means here we are 20 years after IPv6 was proposed still not adopting it.

    I think Microsoft, Google, Yahoo, Amazon etc. have the means to hasten adoption by deprecating IPv4 along some reasonable timeframe and leaning on ISPs to follow suit.

  46. Mitsutani says:

    @hamakaze japan: 申し訳ありませんが、何が言いたいか理解出来ませんでした。良ければ日本語のメッセージを送って頂ければ英語に直します。[Sorry, but I am not sure what you wanted to say. If it pleases you, send a Japanese message and I will translate it into English.]

  47. Marco says:

    Great job, thank you. Customers probably will not notice any change but it's a big step for the internet

  48. Mircea says:

    Metro sucks on Desktop! +1111111111111111111111111

  49. Mircea says:

    Metro rocks on Desktop!

  50. Thanks for Killing Silverlight says:

    @Steven Sinofsky,

    You can take away all of the Windows 8 options for your customers and you can force Windows 8 desktop users to use Metro but, what you don't seem to get is that your customers have a choice to not develop for Windows 8 or buy Windows 8 – a lesson that I feel you will learn in less than one year from now.

    I have been a loyal MS stack developer and MCT for the last 23 years and still develop Enterprise Windows products 50 hours per week; however, thanks to your ridged "control the information flow" and "force your customers to do things your way" I have become a very competent iOS iPhone and iPad developer.

    I realize that you will never listen but I suspect that when the Microsoft board see the sales results for Windows 8 that there will be some changes made at Microsoft.

    Go ahead Steven – delete this.

  51. Craig says:

    Compared to Apple, Microsoft used to offer more choice, now they are telling everyone they know best.  Stop drinking the Apple Cider and start listening to customers.  For me the Metro interface is a deal breaker, for others it may be what they need.  Please allow users to choose between interfaces; is it really that hard?  If people have to learn something radically different they may as well learn Linux, Apple, Android, etc.  

  52. Großer Gott says:

    Metro rocks on the desktop. Metro is the greatest UI innovation of all time. It's beautiful, productive, modern, fast and fluid. Classic desktop sucks. +2

    When you agree, post the same. 😀

  53. F says:

    Metro sucks on desktop!

  54. kinokijuf says:

    Metro sucks on Desktop

  55. Musti says:

    @Steven Sinofsky

    May are you present one article about windows start menu . without it i don't work in Desktop Systems ?

  56. Stefano says:

    What is needed for IPv6? Modem/router since what year? ISP support? OS support since?

    For example a router/modem starting from the year 20xx, Windows 7 and later and ISP support.

    Will it be easy for ISP's in all the world to move to IPv6?

    I'm going to change my router/modem only when it will be mandatory and the Internet won't work anymore 🙂

  57. Matt D. says:

    Metro rocks on the desktop!!

  58. Matt D. says:

    where the f did they take my

    'Metro sucks on the desktop! +' comment?

    wtf Microsoft!

  59. James D. says:

    Metro sucks on the desktop!!! +100000000000000 From Switzerland!

  60. Chris Smith says:

    +1 for Metro sucking.

    I don't give a rat's rear about IPv6 changes if I'm going to have to suffer Metro. Please just get rid of it.


  61. Metro sucks says:

    Metro sucks everywhere!

  62. woland_y2k says:

    Metro sucks on the desktop! +1

  63. JGodo says:

    Desktop tile is the only one I have in metro start. So for me metro is only one more click to go to the real computer desktop everytime and the annoying charms. So for me, yes, metro sucks on desktop.

  64. raymond says:

    Why does metro windows 8 seem to be developed for landscape mode on tablet? I actually use tablets in portrait mode and never use it in landscape unless watching a full screen show/movie. Metro tiles don't seem to be developed to work as nice panning vertically on windows 8

  65. Metro sucks on the desktop! +∞

  66. Pol says:

    Metro sucks everywhere Sinofsky!

  67. Darren says:

    Metro sucks Mr. Sinofsky!!!!!!!

  68. Alvaro says:

    Are you sure that you switched on IPv6??? When i resolve dont see any IPv6 address (as opposite to



    Default Server:  srv01.dom.loc



    Server:  srv01.dom.loc


    Non-authoritative answer:





    Server:  srv01.dom.loc


    Non-authoritative answer:


    Addresses:  2607:f8b0:4002:802::1002







  69. Vincent says:

    Nice job Microsoft keeping up with the times. I love metro on the desktop and think it will be brilliant once you remove aero and put metro on everything.

    However I'm having issues with the release preview where the PC will randomly freeze from time to time from an unknown issue. I think it relates to internet usage. Chrome is most likely to crash the machine but internet explorer is doing it too. If music is playing, it will sound like its jumping and then slowly you loose mouse control where finally you can do nothing. There is NO blue screens involved.

  70. Lester says:

    @Alvaro, Microsoft first implemented IPV6 capabilities in Windows 2000 (12 years ago). Linux bring it later and Apple introduced it in 2010 or 11 (with Mac 10.X..)? and its derivate with different locale went through test-runs several times on IPV6 and (another derivative of Microsoft) has it activated for gaming purposes.


    Addresses:  2a01:111:f009::3b03


  71. sevenacids says:

    What has this post to do with the Metro environment? I mean, seriously.

    There are people who say it sucks, and others who say it rocks. Now, who's right? I mean, is this some kind of kindergarten here, or what? Microsoft, or the Windows team, won't change their mind because of your whining, so get over it. If you don't need any of the new features of Windows 8, it's just OK to stick with Windows 7 and wait and see what the future will bring. Maybe this Windows release will be the beginning of a change, and your next PC operating system might not be Windows anymore. No one is forcing you to use what you don't like. It's still your decision. Now, please focus on the topic.

    PS: I think there's only one thing to criticize about Metro: It's current limitations, and that Microsoft is going the Apple-way now, heading to a closed-down system. When will Jailbreak for Windows be released to fix this?

  72. Metallica says:

    @UnhappySystemAdmin, In windows 7 to open the cmd, I press WindowKey and type cmd and press enter. It search, find and open cmd automagically.

    Now, In windows 8 to open the cmd, I press WindowKey and type cmd (yes don't need to click search just type ON metro as soon as it comes) and press enter.

    Same goes for logout. On windows 7, if your default power action is shutdown, you press WindowKey, click on small arrow with shutdown and click on logout. In Windows 8, you press WindowKey click on your name at top right corner and click Sign out.

    When in metro app, always remember to use "charms" (Ctrl+C) to see if the app has "contract" with charm.

    Metro rocks! it really does.. its a matter of time yall get used to it.

    @Microsoft, please disable (or gray-out) the icons for those charms with whom the current app has no contract.

    ~ M for Microsoft, Metallica, Metal Gear Solid & Nothing Else Matters !!

  73. Ows Wind 8 says:

    I just upgrade Windows 8 to Windows 7 it feels so nice to use windows 7 after using W8 it feels futuristic. I dont like Windows 8 (Bad service pack)

  74. Future Apple Customer says:

    "~ M for Microsoft, Metallica, Metal Gear Solid & Nothing Else Matters !!"

    How old are you?

  75. I WTF'd says:


    VS Express can only compile metro apps?

    you are so dead msft…

  76. Metallica says:

    @Future Apple Customer, old enough to know that Apple sucks big time!

  77. Bon says:

    metro could be a really great iOS competitor on the tablet market, but please please please.. i don't want super large icons and texts on my desktop/laptop. I rather stick to windows 7 when i can pin a lot of programs on my start menu, and in one click i see them all.

  78. abdelkarim says:

    Metro sucks on Desktop! +1


  79. danpetalbo says:

    Metro ROCKS on desktop and tablets! +1

  80. Anonymous says:
  81. Jeez says:

    Holy sh*t, playing/organizing media in metro is a huge struggle!

  82. Windows 8 says:

    Metro is only an experiment. If it falls, there will be aero in the next version of windows 8

  83. Friemo says:

    Metro sucks on Desktop! +1

  84. peter hu says:

    Wow this is an amazing software Windows 8 is fantastic.

    I haven't been this excited about an operating system .

    the start screen has really grown on me. I have to admit that my initial reaction almost a year back was a bit "meh"

    but now can be  wonderful and As much as I like it on the desktop, I can't wait to use it on a tablet, as I know it'll be even better there.

    so can everyone not hate this amazing software and work harder to understand and love a new things!

  85. Metro says:

    Im rucking on the Desktop !!!

  86. Metroagain says:

    Im rocking on te Desktop AND Tablets !!!

    Wonderfull peace of Sotware is the Wondows 8…

  87. Metro says:

    I suck on desktop +1

  88. m says:

    I had windows 8 on my laptop but the monitor didn't work. it needs a diver

  89. Steffo says:

    I wonder why people here don't understand what way Microsoft is going. They are going the same way as (Cr)Apple. Locking in their users to buy apps only through their store so they can earn a lot of money. I as a desktop user want freedom to choose where i buy software and i want my freedom to choose what i install. Microsoft will probably try to prevent this freedom by force Metro down their users throats. I will ofcourse not stay faithful to Microsoft, even if i have used Windows since NT4. The only way to go in the future, if Microsoft continue this BS is to move to Linux. (Cr)Apple is no alternative, they already do what Microsoft plan to do. Will be cool when all fanboys/fangirls start to jailbreak their Windows to be able to use it the way they want to use it in the future….. Too bad they still don't understand what way Microsoft want to go !

  90. @xpclient

    That’s a good question.  RFC 6106 is intended for assigning IPv6 addresses in environments that don’t have DHCP servers.  We don’t see any demand for it, however, for several reasons.

    First, much of the perceived complexity associated with stateful DHCP has been mitigated with stateless DHCP implementations (RFC 3736).

    Second, the requirements for customer premise equipment (RFC 6204) specify DHCPv6 support as a MUST have, and DHCP is important for lots of other reasons – such as assigning DNS servers.  In other words, most people are going to need to deploy a DHCPv6 server anyway even if they don’t want it for assigning IP addresses.  If Windows supported RFC 6106, it wouldn’t really simplify things for most customers – since they would still have DHCPv6 deployed anyway for configuring other aspects of the hosts.  In fact, RFC 6106 support would further instigate fragmentation of the network configuration space and make it harder for software and hardware partners to engineer IPv6 support.  RFC 5505 discuses some of the principles of host configurations, including the value of minimizing diversity (section 2.3).

  91. Correction-

    RFC 6106 is intended for <<configuring DNS server addresses>> in environments that don’t have DHCP servers.

  92. DarienHawk67 says:

    Metro sucks on Desktop! +1

  93. @Steven

    This is a great analogy for an IP address. It's like a telephone number!

  94. Herc Sherlock says:

    @DarienHawk67 and other bashers, have you actually tried using Windows 8 RP on barebone (as opposed to VM) ??

    I don't think so!

    Metro does rock on desktop and laptop!

    Tip: always use CTRL+C shortcut when in metro apps, it gives you all the shareing controls required in the current app !!

  95. Multi Monitor says:

    As comments aren't accepted there so, I had to ask it here, Multi-Monitor's good but did you check as I'm not able to run metro apps on both displays at the same time, for instance if I'm running music app on one display and go on to select start page on another display, well the music app on the other display minimizes it-self and all I see is desktop view on the other display.

    Why is it so please explain.

  96. usser says:

    Metro is alight-ish on the Desktop…

    But it rocks on a Tab!

    Way to Go!

  97. sevenacids says:

    I wonder how many comments would be left if you'd filter out all the Metro-related ones… :p

  98. @sevenacids says:

    @sevenacids, probably none.

    Metro is the only thing wrong with Windows 8, but it's the biggest part of Windows 8, thus the biggest problem.

    Me, Vista and now 8, will they ever learn? <sigh>

  99. Amit says:

    Windows 8 is going to be a huge flop. Guess, Microsoft will learn only after failure. Just go through all the Windows 8 polls out there, more than 50% don't recommend it

  100. Steve says:

    Metro sucks + 1

  101. Richard says:

    Yes, Metro sucks. Seems like Microsoft is digging it's own coffin…

  102. Darren says:

    Another Windows 8 lover:…/20706

    "On the face of it, Metro UI looks good. It’s new and shiny and refreshing, and it looks like it could actually be quite usable. If you’ve used Windows Phone then the interface feel familiar. Things feel good.

    And then you start to use it."

  103. Why is a majority of users, in these comments, talking about Metro apps and development on an article primarily about the transitioning from IPv4 to IPv6?

  104. Richard says:

    @PS3_Sean1985, its not 'majority of users' its mostly same guy sending messages from different alias. If you wana decide wheter you like Windows 8 or not, give it a try and make your own impressions. These creeping trolls (paid by some bullsh*t company) are plauging you and have no idea about anything.

  105. Clarence says:

    Scrolled past the massive Metro flame-war to say that I first noticed the upgrades for IPV6 when installing the WAMP server. Took a few tweaks to get working but nothing too bad.

  106. Levi says:

    [This is an off-topic comment. Pardon my frustration]

    @Steven Sinofsky, as far as user experience go, metro interface would omit the desktop notifications (especially the IM notifications from MSN, YAHOO and other clients), which is a complete disaster !!Would it be possible for you guys to route the notifications from desktop to Metro, if the user is currently in Metro environment? Please reply.

  107. ariyan says:


  108. Raymond says:

    I've just read the new blog entry on how you improved the metro media apps. Um…How about improving and updating the windows media player making that faster and quicker and all that great stuff you are doing for metro. Desktop users would like a better program for media and basic dvd playback but yet you aren't going to give us either. UPDATE windows media player already. It hasn't been updated in a LONG time. Fix the playback issues the sluggishness and basically improve it like how you improved the media metro apps. I find it offensive that you are completley ignoring the desktop users and the programs we use. How about improving those? Also improving Zune software and not make it look like XBOX. Xbox is ugly and too green. I'm sorry but Even XBOX music should look a little better than what it lools like now. Hideous. Also stop closing comments on the blog before we even get a chance to voice opinions.

    Expecting updates to windows media player that hasn't been updated in a LONG time. Updates to zune software. Basically updates to the all desktop media programs. But nope hasn't happened.

  109. raymond says:

    The metro media app track bar is hideous specifically the square tracker. Should look a little more alive.

  110. Darren says:

    "Would it be possible for you guys to route the notifications from desktop to Metro, if the user is currently in Metro environment?"

    @Levi: This is not going to happen. Microsoft wants that these clients get ported to Metro. So they will not do anything that makes using them like it was before. Metro and desktop are incompatible in any aspect an Microsoft wants you to live with it.

  111. Dan says:

    This post was published 3 days ago and I can comment, "Building a rich and extensible media platform" post was published only 16 hours ago and I can't comment there! WTF?

  112. Thulasi says:

    i am stuck with metro please bring back statr menu..

  113. WindowsVista567 says:

    @Darren, it is very possible and the guys on Windows user experience team are on it. You will get more integration of Metro and Desktop by the time of final RTM. Rest assured, Metro and Desktop, they ain't incompatible!

  114. WindowsVista567 says:

    @Dan, the trouble there is, people were misusing the comment system and bashing each other if you go through the previous comments. I guess Microsoft should impose the access control, so only signed user can post comment. Its easy to keep track of bashers, fan=boys and productive commentators/critics. For example I like Microsoft products and I do criticize if they I find any screw up in them. But since I dont use Apple products, I wont go to their blogs for mere trolling. Now, on each MSDN blog you will find lots of lapdogs coming from other communities and trolling with groundless points. Thats what I hate about an open comment system. Then I guess its just me..

  115. WindowsXP says:

    Long live Windows XP !

Comments are closed.

Skip to main content