<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Accessible ports script in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814380#M100162</link>
    <description>with NMAP you scan a full subnet, or portions.. &lt;BR /&gt;&lt;BR /&gt;for example &lt;BR /&gt;&lt;BR /&gt;nmap -v 192.168.0.0/24 &lt;BR /&gt;&lt;BR /&gt;will scan all addresses in the 192.168.0.0 subnet. &lt;BR /&gt;&lt;BR /&gt;if you change your bit mask to 16 it will be 192.168.0.0 so anything from 192.168.0.0-192.168.255.255 &lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Thu, 29 Jun 2006 13:32:25 GMT</pubDate>
    <dc:creator>rmueller58</dc:creator>
    <dc:date>2006-06-29T13:32:25Z</dc:date>
    <item>
      <title>Accessible ports script</title>
      <link>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814376#M100158</link>
      <description>I need help with a script.  We have servers on this side of the firewall, and servers on that side.  I need to find a way to see what common ports (21, 22, 23, 1521, etc) are accessible from what servers.  Like can serverA on one side of the firewall access 1521 on serverB on the other side of the firewall. &lt;BR /&gt;&lt;BR /&gt;Any ideas?  Thanks!  I know the firewall people should be able to tell me but that is worse than pulling teeth, and I would rather find out as much as I can from my end...*if* I can.</description>
      <pubDate>Wed, 28 Jun 2006 13:14:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814376#M100158</guid>
      <dc:creator>Coolmar</dc:creator>
      <dc:date>2006-06-28T13:14:58Z</dc:date>
    </item>
    <item>
      <title>Re: Accessible ports script</title>
      <link>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814377#M100159</link>
      <description>The best took I know to identify open ports is NMAP. Download it from here:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://hpux.cs.utah.edu/hppd/hpux/Networking/Admin/nmap-3.93/" target="_blank"&gt;http://hpux.cs.utah.edu/hppd/hpux/Networking/Admin/nmap-3.93/&lt;/A&gt;</description>
      <pubDate>Wed, 28 Jun 2006 13:27:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814377#M100159</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2006-06-28T13:27:40Z</dc:date>
    </item>
    <item>
      <title>Re: Accessible ports script</title>
      <link>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814378#M100160</link>
      <description>Hi Sally:&lt;BR /&gt;&lt;BR /&gt;It seems to me that (s)he who maintains the rules should be able to *recite* the rules!  :-))&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Wed, 28 Jun 2006 13:27:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814378#M100160</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2006-06-28T13:27:57Z</dc:date>
    </item>
    <item>
      <title>Re: Accessible ports script</title>
      <link>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814379#M100161</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;[root@tehran ~]# nmap localhost&lt;BR /&gt;&lt;BR /&gt;Starting nmap 3.70 ( &lt;A href="http://www.insecure.org/nmap/" target="_blank"&gt;http://www.insecure.org/nmap/&lt;/A&gt; ) at 2006-06-28 13:29 CDT&lt;BR /&gt;Interesting ports on tehran (127.0.0.1):&lt;BR /&gt;(The 1651 ports scanned but not shown below are in state: closed)&lt;BR /&gt;PORT      STATE SERVICE&lt;BR /&gt;22/tcp    open  ssh&lt;BR /&gt;53/tcp    open  domain&lt;BR /&gt;111/tcp   open  rpcbind&lt;BR /&gt;631/tcp   open  ipp&lt;BR /&gt;953/tcp   open  rndc&lt;BR /&gt;5801/tcp  open  vnc-http-1&lt;BR /&gt;5901/tcp  open  vnc-1&lt;BR /&gt;6001/tcp  open  X11:1&lt;BR /&gt;10000/tcp open  snet-sensor-mgmt&lt;BR /&gt;&lt;BR /&gt;Nmap run completed -- 1 IP address (1 host up) scanned in 0.789 seconds&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thats a server in the US. We like to name them after cities in "The Axis of Evil" Poking a little fun.&lt;BR /&gt;&lt;BR /&gt;nmap works great and is standard on Linux. Its instalable or compilable on HP-UX but this is much less fun.&lt;BR /&gt;&lt;BR /&gt;This tool does something called portscanning. This is something that network admins hate. So get permission before you use it.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 28 Jun 2006 13:31:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814379#M100161</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2006-06-28T13:31:31Z</dc:date>
    </item>
    <item>
      <title>Re: Accessible ports script</title>
      <link>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814380#M100162</link>
      <description>with NMAP you scan a full subnet, or portions.. &lt;BR /&gt;&lt;BR /&gt;for example &lt;BR /&gt;&lt;BR /&gt;nmap -v 192.168.0.0/24 &lt;BR /&gt;&lt;BR /&gt;will scan all addresses in the 192.168.0.0 subnet. &lt;BR /&gt;&lt;BR /&gt;if you change your bit mask to 16 it will be 192.168.0.0 so anything from 192.168.0.0-192.168.255.255 &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 29 Jun 2006 13:32:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814380#M100162</guid>
      <dc:creator>rmueller58</dc:creator>
      <dc:date>2006-06-29T13:32:25Z</dc:date>
    </item>
    <item>
      <title>Re: Accessible ports script</title>
      <link>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814381#M100163</link>
      <description>Ok, thanks.  Will nmap scan all ports, or can you specify for it to just check the ports you list (23, 22, 5021, etc)?</description>
      <pubDate>Fri, 30 Jun 2006 06:31:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814381#M100163</guid>
      <dc:creator>Coolmar</dc:creator>
      <dc:date>2006-06-30T06:31:26Z</dc:date>
    </item>
    <item>
      <title>Re: Accessible ports script</title>
      <link>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814382#M100164</link>
      <description>You can specify port ranges (what follows after the -p), like&lt;BR /&gt;  &lt;BR /&gt;nmap -P0 -sT -p 20-25,115,80,143 some.host.or.ip</description>
      <pubDate>Fri, 30 Jun 2006 07:29:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814382#M100164</guid>
      <dc:creator>Ralph Grothe</dc:creator>
      <dc:date>2006-06-30T07:29:17Z</dc:date>
    </item>
    <item>
      <title>Re: Accessible ports script</title>
      <link>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814383#M100165</link>
      <description>Sally,&lt;BR /&gt;&lt;BR /&gt;If you have many hosts to scan, nmap also accepts a list of hostnames:&lt;BR /&gt;&lt;BR /&gt;nmap -iL &lt;INPUTFILENAME&gt; ...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;PCS&lt;/INPUTFILENAME&gt;</description>
      <pubDate>Fri, 30 Jun 2006 07:43:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814383#M100165</guid>
      <dc:creator>spex</dc:creator>
      <dc:date>2006-06-30T07:43:11Z</dc:date>
    </item>
    <item>
      <title>Re: Accessible ports script</title>
      <link>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814384#M100166</link>
      <description>Though I can fully understand your reluctance to get in touch with your firewall admis&lt;BR /&gt;(these folks are really taciturn, probably a symptom of their trade?) you should rather talk to them before you open fire with a port scanner on their firwalls.&lt;BR /&gt;Apart from the spurios trafic you generate you could inadvertently trigger of some bogus alerts.&lt;BR /&gt;nmap is a very powerful tool and has sophisticated methods of randomizing and stealthing its scans as you may read in its manpage.</description>
      <pubDate>Fri, 30 Jun 2006 07:46:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/accessible-ports-script/m-p/3814384#M100166</guid>
      <dc:creator>Ralph Grothe</dc:creator>
      <dc:date>2006-06-30T07:46:38Z</dc:date>
    </item>
  </channel>
</rss>

