Export (0) Print
Expand All

Primary WINS server failed to respond

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2005-11-18

The Microsoft® Exchange Server Analyzer Tool queries the Win32_NetworkAdapterConfiguration Microsoft Windows® Management Instrumentation (WMI) class to obtain the WINSPrimaryServer attribute. This attribute is the IP address of the primary Windows Internet Name Service (WINS) server for the Exchange Server computer. After the Exchange Server Analyzer retrieves the address of the primary WINS server, the Exchange Server Analyzer opens a TCP socket connection to port 137 on the server. This connection is made by using a custom object processor that returns a specific string if the connection is successful. If the Exchange Server Analyzer does not receive 137 Available as part of the returned string, the Exchange Server Analyzer displays a warning.

This warning indicates that the server did not respond to a connection attempt on TCP port 137. By default, WINS servers listen on TCP socket 137 for communications such as name resolution queries.

If the primary WINS server is unreachable and you are running Exchange Server, mail delivery will be slow, especially in larger organizations. You should troubleshoot why the primary WINS server is not available, or change the WINS settings on the Exchange server to use a different WINS server for name resolution.

To correct this warning
  1. Make sure that the WINS server has been started and is connected to the network.

  2. Use the PING command to determine whether the WINS server is reachable.

For information about why WINS is required for Exchange 2000 Server and Exchange Server 2003, see the Microsoft Knowledge Base article 837391, "Exchange Server 2003 and Exchange 2000 Server require NetBIOS name resolution for full functionality" (http://go.microsoft.com/fwlink/?LinkId=3052&kbid=837391).

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft