We need this to find a database that one of our in-house applications
is connecting to(We SHOULD have this information....I agree...but we
dont:))
use nmap scan for port 3306
Yes. Port scanning tools (such as nmap) do this very well, if you
can guess what port it's on (port 3306 is an obvious choice. I
don't know of a standard place to put the SECOND instance of MySQL,
if you ever put more than one on the same server.) If this is YOUR
network, fine. If this is your employer's network, get approval,
preferably in writing first, or you may end up fired or in handcuffs
or both.
>We need this to find a database that one of our in-house applications
>is connecting to(We SHOULD have this information....I agree...but we
>dont:))
If you can get the client to connect to the unknown server, then
run 'netstat' on the client (is this a web server? I'm referring
to the *MySQL* client, which might be PHP or Perl or something
similar) while it's still connected, you should be able to see its
connection. Or you could use 'tcpdump' run on the client to show
packets for any outgoing packets to port 3306.
hmmm.. if you know the client, and it is PHP or PERL - wouldn't you just
get the SA to login to the system and tell you the db server to which
they are connecting? Most of those would have an include script to
connect to the db and it would contain the information they are looking
for.... :) otherwise - nmap and portscan all IP addresses on your
network - and this could take a while if you have a shop as big as the
one in which I work... with more than several thousand servers in the
data centers... not including desktops or windows...