Forum Discussion

Spc .'s avatar
Spc .
Brass Contributor
Nov 06, 2018

Windows Server 2019 - 1809 - Build 17763.107 - LAN names return .local

In Windows Server 2019 - 1809 - Build 17763.107 when user pings or tracert ( trace routes ) a LAN name, name has 50% chance to return .local at the end. Example:   How to reproduce: 1. ...
General
networking
Mary Hoffman's avatar
Mary Hoffman
Former Employee
Nov 13, 2018

17763 in any form was never made available to Server Insiders. The last build that was offered to Insiders was Build 17744.  17763.1 was live very briefly on some external channels on 10/2 but almost immediately removed from all external channels. 17763.107 was not made available externally until today, 11/13.  How did you obtain the .107 build in time to provide feedback on 11/6?

Spc .'s avatar
Spc .
Brass Contributor
Nov 14, 2018

Before MS took down all the links,  Windows Server 2019 evaluation was available for download, this was 17763.1 "trial", same as full version but trial version.

17763.107 was available for Windows 10 insiders as "windows10.0-kb4464455-x64.cab"

http://download.windowsupdate.com/c/msdownload/update/software/updt/2018/11/windows10.0-kb4464455-x64_de985f6d38215b316470dbecabb453c762a217af.cab

 

 

Anyone can use DISM in powershell to install and upgrade 17763.1 (ws2019 trial) to .107, this also applies to windows server as both windows 10 and server share almost the same code.

 

So Windows server 2019 17763.1 (trial) + kb4464455 = 17763.107 (trial)

 

If you do this you get Windows Server 2019 17763.107, which is for "insiders" to test things out.

 

So this was the method i used to test new patches.

I will again download the new updated trial version when links show up:
https://www.microsoft.com/en-us/cloud-platform/windows-server-trial

And test it again, fresh clean install and report back.

 

  • Spc .'s avatar
    Spc .
    Brass Contributor
    Nov 15, 2018

    This ".local" bug might also be a related problem for this:
    https://support.microsoft.com/en-gb/help/4471218/mapped-network-drives-don-t-work-in-windows-10-version-1809

    • Spc .'s avatar
      Spc .
      Brass Contributor
      Jan 08, 2019

      .local bug still present in 17763.253, Windows 10 Pro 17763.253 does the same.

       

      While pinging or trace routing a windows name in local network, ipv6 always returns .local

       

      Example:

      Pinging SEA.local [fe80::49ab:74ed:a10:32f7%3] with 32 bytes of data:
      Reply from fe80::49ab:74ed:a10:32f7%3: time<1ms

       

      If IPV6 is turned off and only IPV4 is used it always displays normal name "SEA" Example:
      Pinging SEA [192.168.0.4] with 32 bytes of data:
      Reply from 192.168.0.4: bytes=32 time<1ms TTL=128

      .local name only appears if ipv6 is in use, because of this bug some network shares might not work correctly as SMB uses local ipv6 addresses to resolve Windows name.

       

      *This does not happen in Windows Server 2016 (all latest updates). Windows Server 2016 always displays correct name via ipv6 local name in my example:


      Pinging SEA [fe80::49ab:74ed:a10:32f7%3] with 32 bytes of data:
      Reply from fe80::49ab:74ed:a10:32f7%3: time<1ms

       

       

       

Resources