Client in LAN cannot connect to SQL Server using machine name

In production environments, it is sometimes required to use machine names to connect to SQL Server servers, but sometimes it can't be connected for a long time.

For this issue to make a short record, to prevent later on their own can not remember the reason, but also convenient for other peers!

Needless to say, as an old guy who worked for years, the following work is sure to be ensured:

The "Named pipes" protocol on the SQL Server server side is turned on!

The SQL Server server side of the network card NetBIOS resolution function is also turned on!

The classic 1433 port used on the SQL Server server is an exception to the firewall!

You have ensured that the client uses IP to connect to the SQL Server server!

After releasing the ICMPV4 firewall exception on the server, ping IP is no problem, but Ping machine name is not! Don't tell me to set up the Hosts file, this thing I do not say it can not do, even if it does not work I do, because that will tie the IP, then I might as well directly with ip!

Check to find out is the firewall in the "File and Printer Sharing (nb-name-in)" Inbound rules are not released , it is specifically to control the NetBIOS resolution to use UDP 137 port;

Hidden deep, record, the following is the effect of the ping before and after the release, of course, the SQL Server client can also be connected by the machine name!

Client in LAN cannot connect to SQL Server using machine name