How Domain Controllers respond to LDAP Ping on UDP 138 port

Symptoms

Consider the following scenario:  

- LMHOSTS file on Windows Server does not contain client hostname.
- WINS server is not configured on Windows Server, or WINS server does not resolve client hostname.
- Windows Server and client are in another network segment.

In this scenario, Windows Server 2008 or later OS do not respond to LDAP Ping (UDP 138 port) from client machine.

More Information

In Windows Server 2003 or older, Windows Server operating systems reply to LDAP Ping on UDP 138 port from client, the behavior however changed since Windows Server 2008.
To make Windows Server 2008 or later to reply to LDAP Ping, configure either of the following settings.

(A) Add LMHOSTS

1. Move to %windir%\system32\drivers\etc folder

2. Add IP address and hostname of client to LMHOSTS file.

  ** See following links for details.

  Domain Browsing with TCP/IP and LMHOSTS Files
  https://support.microsoft.com/en-us/kb/150800

(B) Add WINS server

Configure TCP/IP to use WINS server which can resolve client hostname to Windows Server.

  Configure TCP/IP to use WINS
  https://msdn.microsoft.com/en-us/library/cc757386(v=ws.10).aspx

(C) Place Windows Servers and client machines in the same segment.

Windows Server resolves client hostname by using NetBIOS broadcast if Windows Server and clients are on the same subnet.

Note: DNS is the primary method of resolving name queries in Active Directory starting with Windows Server 2000 and including Windows Server 2003, Windows Server 2008, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016 and beyond. 
Properties

Article ID: 3088277 - Last Review: 21 Aug 2015 - Revision: 1

Feedback