Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.
Windows Server TechCenter >
> 
> 
IPv6-Only Support (Windows not ready?)

Discussão Geral IPv6-Only Support (Windows not ready?)

  • Monday, November 12, 2012 5:01 PM
     
     
    Sign In to Vote
    0

    So I was setting up a new Server 2012 VM (as a template for future deployments) - and decided to not add an IPv4 address (thinking I'd have to change it later, and not having one would ensure I set the final hosts' assigned address, as things wouldn't work otherwise) - and just use IPv6.

    I hit a few snags, detailed below:

    Windows Update worked fine.

    Converting to Microsoft Update did not:

    • In the 'Windows Update' window, the link to convert to Microsoft update uses http://go.microsoft.com/ (Specifically, http://go.microsoft.com/fwlink/?LinkID=230963 )
    • http://go.microsoft.com/ does not have an AAAA record, thus no IPv6.
    • If you look up the above Go link, it will redirect you to: http://fe1.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en - which IS IPv6-capable.
    • So if you manually enter the fe1.update.microsoft.com address from above, it'll work - you just can't use the handy shortcut.

    Windows Activation does not work - cannot find the DNS entry for whatever system it uses.  Biggest showstopper I think, as it requires v4 address, NAT64, or a phone call.

    Time synchronization by default uses time.windows.com - NOT IPv6-enabled.  Had to point this at another resource ( I chose X.pool.ntp.org and had no issues)

    I find it both interesting and funny that (many) microsoft.com and windows.com URLs don't work with IPv6 - yet both Bing.com and Xbox.com have IPv6 capability enabled.

    Hopefully Microsoft can work towards enabling these last few things, so as folks set up IPv6-only servers without NAT64 things work.

    What else isn't working OOTB (Out Of The Box) on IPv6-only enabled systems?