Forum Discussion
neelesh kumar
Apr 27, 2018Copper Contributor
Windows 10 RS4-17650, NETBios Resolution Issue
Windows 10 RS4-17650, we are facing issue related to discovery of printer device with netbios name. When we ping the device from console with netbios name in upper case ,we get the error "Ping reque...
Kevin Marchant
May 17, 2018Copper Contributor
Just to say I've got the same problem on 1803. Only one machine exhibits the problem. Ping fails (no LLMNR request is broadcast as shown by Wireshark) if the hostname in the ping matches the destination machine hostname exactly in the same case. PING UPPERCASE fails with "could not find host" if the destination machine is set to UPPERCASE whilst all other case variations (lowercase and MiXed) succeed, If you change the destination machine computername to lowercase then PING lowercase fails with "could not find host", whilst all other case variations (UPPERCASE and MiXed) succeed.
In both scenarios PING UPPERCASE. <trailing Dot) and PING lowercase. succeed.
This is similar to a problem mentioned here.
https://superuser.com/questions/495759/why-is-ping-unable-to-resolve-a-name-when-nslookup-works-fine
but the solution of adding a "." appended DNS domain does not seem to resolve this problem.
Definitely something wonky in 1803.
In both scenarios PING UPPERCASE. <trailing Dot) and PING lowercase. succeed.
This is similar to a problem mentioned here.
https://superuser.com/questions/495759/why-is-ping-unable-to-resolve-a-name-when-nslookup-works-fine
but the solution of adding a "." appended DNS domain does not seem to resolve this problem.
Definitely something wonky in 1803.
diego pego
May 28, 2018Copper Contributor
ping lowercase with dot at the end, and ping all UPPERCASE works in here.