Use nmap. Unless you deliberately changed the IP port you should have no problem. Are you the one who setup all the servers?
On Wed, Nov 17, 2010 at 4:03 PM, Frederiko Costa <freder...@gmail.com>wrote: > True. However, I was just assuming that Postgres was running on default > ports. If not, you could also probe in port ranges or even probe the network > for open ports to have an idea and get closer. It might be faster option if > software such as Spiceworks is not being used. > > Spiceworks looks a good option too. > > ~Fred > > > On Wed, Nov 17, 2010 at 12:56 PM, Scott Whitney <sc...@journyx.com> wrote: > >> That only works in the event that you have PG listening on port 5432. >> >> A product like Spiceworks will provide much more detail, presuming you >> have the IT credentials to talk to the machines. >> >> ------------------------------ >> >> nmap is the way to go. Try to scan for port 5432 in a range of IP of your >> LAN. >> >> ~Fred >> Linkedin profile: http://www.linkedin.com/in/frederikocosta >> >> >> On Sun, Nov 14, 2010 at 8:52 AM, ojas dubey <ojas.du...@gmail.com> wrote: >> >> > Hi, >> > >> > I wanted to know if there is a way to get the hostnames of all the >> systems >> > running PostGres DB servers on a local network on Windows (XP/Vista/7) >> using >> > JDBC or any other Java API ? >> > >> > >> > Regards, >> > Ojas >> > >> >> >> >
