November 9, 2005 at 8:39 am
I have been using OSQL -L to identify SQL Server installations. As I use this command on different servers I get inconsistent results. Some servers detect other servers which cannot detect them in return.
For example:
Server1 can detect a Sql Server on Server2.
Server2 cannot detect Sql Server on Server1 but may find Sql Server on servers that Server1 missed.
I heard this method of detection is limited to servers using the same sub-net. Which does not make sense when one can detect the other but not the other way.
I have used a VBScript from the Microsoft Scripting Guys http://www.microsoft.com/technet/scriptcenter/scripts/sql/srvmgmt/default.mspx
But the results still don't list all installations.
Any ideas why the detection works this way? Is there a better way to detect installations.
David Bird
November 9, 2005 at 10:33 am
Have you tried SQL Scan from Microsoft? It's part of a bundle they released following the Slammer worm. We use it and it seems to find all instances.
Greg
Greg
November 9, 2005 at 3:55 pm
Hi,
It does make sense.
-L Lists the locally configured servers and the names of the servers broadcasting on the network.
The keyword here is Broadcasting. To hide the server: Open Server Network Utility, Click on TCP/IP protocol on General tab assuming it is Enabled, click Properties button, check Hide Server in properties. Then this server will detect other servers that are broadcasting but may or may not be detected itself.
Also a keyword is Locally Configured. This means entries on Alias tab in Client Networ utility. If you have entries on Server 2 for the servers that Server 1 missed then yes, -L option will list these entries even if they are not valid. For example create an entry for Test with the server name Test1 (that does not exist on your network). Then osql -L will list Test too
Regards,Yelena Varsha
November 10, 2005 at 7:20 am
Keep in mind Scan SQL Scan requires the user to be a domain administrator when it is used to target remote machines. As for hiding the Server in the TCP/IP properties, be careful. It will change the port to 1434 and may break applications.
Linda
November 10, 2005 at 7:57 am
These servers are all setup for broadcasting. I checked Server Network Utility settings and they are not setup to be hidden.
These servers are setup with default instance using TCP/IP and so I don't set them up with an Alias in the Client Network Utility.
David Bird
November 10, 2005 at 12:03 pm
I've had good luck 'free' third party tool like SQL Recon from Special Ops Security. Once you install a tool like this you'll need to speak with your network folks and get a list of IP address ranges at you site (e.g. 10.172.0.0 - 10.172.254.254, 10.10.0.0 - 10.10.254.254) and scan the ranges. Otherwise a scan of a range like 10.0.0.0 - 10.254.254.254 may take a week to run !
Beware if you are on a 'switched' network (some of these scripts will not find everything). Also, secure fire-walled subnetworks can be an issue as well (boy do I know this one !).
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply