![using zenmap using zenmap](https://miloserdov.org/wp-content/uploads/2021/05/zenmap-2.png)
By looking for SQL Servers listening via the TCP protocol on port 1433.When it comes to detecting SQL Servers on the network, we can use nmap to do this two ways: Failure to get written permission from the right person can lead to what we call a "career altering event." Avoid this by doing the legwork to get the permission. If something goes wrong ( you're in IT, so you always plan for something to go wrong, or at least you should be) you want to be able to show you had permission to do what you were doing. You don't want to go on verbal permission. When you do get said permission, make sure it is in "writing." Email is fine. It usually falls to a security or networking manager to authorize this. In alot of organizations, the DBA manager does not have this permission. If you're going to use this tool within your organization, make sure you have permission to do so by someone who is actually authorized to give you that permission. The nmap tool is often considered a hacking tool by organizations. That makes it a great tool for detecting anything, especially Microsoft SQL Server installations.
![using zenmap using zenmap](https://i.ytimg.com/vi/tZjSOhuvKDg/maxresdefault.jpg)
![using zenmap using zenmap](https://www.cyberciti.biz/media/new/cms/2012/11/nmap-usage-examples-output.png)
#USING ZENMAP FREE#
While there are several good tools out there, the one that has been used by network and security professionals for years is a free tool called nmap. We know there are a couple of appliances that are potentially running SQL Server and we want to see them, too. I need to try and find all SQL Servers, not just the ones in my domain. I've recently been asked to identify and report on any SQL Servers listening on my network. Brian Kelley | Updated: | Comments (13) | Related: > Security