Forum Discussion
Issues/Problems with Release 17733
I am sending you a copy of the lab project which gives ALL the steps we use. Note again, everything works fine with Server 2016. Note the lab project name is "Image X" but as you will see, we use DISM.
Update on Docker and DISM - they work now.
On my original problems - #2 and #3, we have solved the issues.
Item #2 Docker failing was due to our not using the newest version of the Docker Engine and Client. Once we downloaded these, we were able to get a Server Core Docker image to run correctly in Server 2019. Also to note - the need for a separate Web Server image for Docker which we had used with Server 2016 isn't necessary - Web Services installed fine with the appropriate Powershell command (as my lab tech figured out) in Server Core, resulting in a working Web Server.
Item #3 The reason DISM wasn't working was that , as above, we were using an older version of DISM from Windows 10, which did work with Server 2016, but not with Server 2019. Once using the version directly from Server 2019, DISM worked fine.
We still have Problem #1 - With Server 2019, Link Local Multicast Name Resolution (LLMNR) does not work with IPv6 when IPv4 is disabled, in other words, single name resolution fails. It worked correctly with Server 2016. We noticed however, that the Computer Browser Service seems to have been eliminated with Server 2016. This should have no effect on the problem however, since it was used for Broadcast Based NetBIOS names with IPv4 only, however I am still very surprised that it has been removed as it provided backward compatibility for older versions of Windows such as XP, etc.
Computer Browser Service showed up once SMB 1.0 was enabled, so that problem is now solved!!!!!!!
However, we STILL have the LLMNR problem with IPv6. Single names flat out don't work with UNC paths, etc. if IPv4 is either disabled or the two computers are on different IPv4 networks forcing IPv6 to be used. Single names worked fine with Server 2016 using IPv6 only!!!!! If this is the intended result, is there some registry setting or something that we can do to bring back this resolution??????
- Brentfor
Microsoft
Bill, what build are you trying this with? 17733 or something newer?
Thanks for reading my information!!! I do appreciate it!!! we have upgraded to 17744 and the problem still persists. LLMNR will not resolve single names with IPv6 - again it works fine with Server 2016. Our scenario is that we put the machines on a private IPv4 network, while we still have other machines on our Public IPv4 network. In trying to reach the machines on the Public network IPv4 network from the ones on the Private Ipv4 network with single names using UNC paths (forcing the use of IPv6) it works fine with Server 2016 - does not resolve with Server 2019 .
Again I appreciate your reading my information in this blog!!!
Bill Reichert
