02-25-2009
netstat -an | grep LISTEN will show ports currently open.
As for how to open/close ports - depends on application you are running if/how you can assign specific port to the application config files.
9 More Discussions You Might Find Interesting
1. Linux
How can I open a port on linux machine ??? (5 Replies)
Discussion started by: mm00123
5 Replies
2. AIX
Hi Guys,
i am trying to open a port in AIX.
but i am not able to get the command for this. AIX is not having the iptables file present.
So please any body can tell me how to open a port in AIX...
Thanks
sanju (2 Replies)
Discussion started by: sanju_d1231
2 Replies
3. IP Networking
Hi. I ran nmap on my server, and I get the following:
Starting Nmap 4.76 ( http://nmap.org ) at 2009-03-19 16:33 EDT
Interesting ports on -------- (-----):
Not shown: 997 closed ports
PORT STATE SERVICE
22/tcp open ssh
80/tcp open http
6881/tcp open bittorrent-tracker
The... (0 Replies)
Discussion started by: Rledley
0 Replies
4. Solaris
Hi All,
Can anyone let me know that how to open a specific port in Solaris 10. I just wanted to know if there are some certain commands to open a port (like ftp, telnet).
It would be also better if someone can tell me if there is another firewall service in Solaris 10 except ipfilter.
... (6 Replies)
Discussion started by: naw_deepak
6 Replies
5. Solaris
Hi All,
I am installing Infosphere (ETL tool) on solaris 10.
One of the requirement is to open multiple ports for different apps that will be installed. I ran netstat -n | grep 9080 (,etc) but that did not return anything.
I have attached the requirement. Can anyone guide me about how to... (3 Replies)
Discussion started by: sumeet
3 Replies
6. UNIX for Advanced & Expert Users
hi experts,
I'm using Linux Centos kernel 2.6
Here is the print out of some my port :
tcp 0 0 127.0.0.1:10080 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:10081 0.0.0.0:* LISTEN
tcp 0 0... (4 Replies)
Discussion started by: justbow
4 Replies
7. IP Networking
i want to kill a tcp connection by killing its pid
with netstat -an i got the tcp ip connection on port 5914
but when i type ps -a or ps-e there is not such process running on port 5914
is it possible that because i do not log on with proper user account i can not see that process running? (30 Replies)
Discussion started by: alinamadchian
30 Replies
8. HP-UX
Hello Experts,
I want to open the port 443 on my HP-UX system.
can you please help ?
Thanks in advance. (1 Reply)
Discussion started by: purushottamaher
1 Replies
9. Solaris
Hi there,
I tried just open a port but I failed ;-(
# telnet localhost 9876
That should work so I did ...
# vi /etc/services
myport 9876/tcp # my port
# svcadm restart inetd
-> New pid, see ps - ef | grep inet
# netstat -an | grep 9876
No port 9876 is waiting ;(
#... (4 Replies)
Discussion started by: System
4 Replies
LEARN ABOUT DEBIAN
sockstat
SOCKSTAT(1) BSD General Commands Manual SOCKSTAT(1)
NAME
sockstat -- list open sockets
SYNOPSIS
sockstat [-clh] [-p ports] [-P pid|process] [-U uid|user] [-G gid|group]
DESCRIPTION
The sockstat command lists open Internet or UNIX domain sockets.
The following options are available:
-c Show connected sockets.
-l Show listening sockets.
-h Show a usage summary.
-p ports Only show Internet sockets if either the local or foreign port number is on the specified list. The ports argument is a comma-
separated list of port numbers and ranges specified as first and last port separated by a dash.
-P pid|process
Only show sockets of the specified pid|process. The pid|process argument is a process name or pid.
-U uid|user
Only show sockets of the specified uid|user. The uid|user argument is a username or uid.
-G gid|group
Only show sockets of the specified gid|group. The gid|group argument is a groupname or gid.
If neither -c or -l is specified, sockstat will list both listening and connected sockets.
The information listed for each socket is:
USER The user who owns the socket.
COMMAND The command which holds the socket.
PID The process ID of the command which holds the socket.
FD The file descriptor number of the socket.
PROTO The transport protocol associated with the socket for Internet sockets, or the type of socket (stream or datagram) for UNIX
sockets.
LOCAL ADDRESS For Internet sockets, this is the address the local end of the socket is bound to (see getsockname(2)). For bound UNIX
sockets, it is the socket's filename. For other UNIX sockets, it is a right arrow followed by the endpoint's filename, or
``??'' if the endpoint could not be determined.
FOREIGN ADDRESS (Internet sockets only) The address the foreign end of the socket is bound to (see getpeername(2)).
SEE ALSO
netstat(1), protocols(5)
HISTORY
The sockstat command appeared in FreeBSD 3.1.
AUTHORS
The sockstat command and this manual page were written by Dag-Erling Smorgrav <des@FreeBSD.org>.
The sockstat command was ported to Linux by William Pitcock <nenolod@nenolod.net>.
BSD
May 18, 2008 BSD