- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: open port & netstat
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2007 12:29 AM
11-16-2007 12:29 AM
open port & netstat
i need to know if port 3290 is open on my server for others. The following command returns nothing :
# netstat -an|grep 329
Is that meaning that the port is not open or that during the command request there is no communication on this port ?
by open, I mean someone can connect on.
thanks for help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2007 12:36 AM
11-16-2007 12:36 AM
Re: open port & netstat
There are also a few different port scanners you can download too. Like knocker, and I believe nmap will do more then just one server. But I thought you could also do it against just 1.
And another way, which may show. Is just telnet host 329 and see if you get a connection denied.
Hopefully theres no firewalls between you and the server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2007 01:03 AM
11-16-2007 01:03 AM
Re: open port & netstat
But I though lsof was to see open files and I want to see open port on my server.
if the netstat does not answer, is that the port is not open ?
Unfortunatly I think I have firewalls ...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2007 01:15 AM
11-16-2007 01:15 AM
Re: open port & netstat
alcatraz:root /opt/OV/logs # lsof -i | grep -e LISTEN | grep 5060
mad 11841 root 7u IPv4 0xe0000001757a9580 0t0 TCP *:5060 (LISTEN)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2007 01:15 AM
11-16-2007 01:15 AM
Re: open port & netstat
# lsof -i | grep
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2007 01:29 AM
11-16-2007 01:29 AM
Re: open port & netstat
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2007 01:31 AM
11-16-2007 01:31 AM
Re: open port & netstat
http://hpux.cs.utah.edu/hppd/hpux/Sysadmin/lsof-4.78/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-16-2007 01:43 AM
11-16-2007 01:43 AM
Re: open port & netstat
(though it's nice to have)
Your void grep already showed you that there is no listening socket at this port.
You could also run
$ netstat -an|awk '$4~/\.3290$/&&$NF=="LISTEN"'
Your telnet to this port thus should get a "connection refused",
or in protocol parlance your host's tcp stack should answer with an ACK/RST set segment.