discovering which ports are in use

Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers discovering which ports are in use
# 8  
Old 11-03-2009
z/OS implements a Unix compliant subsystem but I'm afraid not that much people familiar with it visit this forum. I might be wrong though.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Discovering TOP process on virtual machine

Hello, on my openvz server, i can output load averages of containers: Code: # vzlist -o laverage,ctid -H 0.00/0.00/0.00 130 0.10/0.10/0.10 150 2.26/2.28/2.28 190please which command/script to use so it outputs top 1 or 2 processes on the linux system with 2.26 laverage? i mean, i want... (1 Reply)
Discussion started by: postcd
1 Replies

2. Infrastructure Monitoring

Discovering Network Topology

Hi all, I am tasked to write a program that learns all possible paths between each pair of nodes in an internetwork. I am not an expert in the area of IP networking/routing. I have been reading about this the last few days. If you know of examples that are close to what I am trying to do, I would... (4 Replies)
Discussion started by: nzeidat
4 Replies

3. UNIX for Advanced & Expert Users


** forum admins: Before you come down on my like a wrath of something, I can get no decent answers so I have to come to these Gurus' court *** I am by no means Unix expert. However, none of our unix admin (aix & hpux) can give me an answer that makes sense. My Issue: Assigned ports in 8601,... (7 Replies)
Discussion started by: rsheikh
7 Replies

4. UNIX for Dummies Questions & Answers


When the netstat -an command is run on current unix machine, it seems that there's an excessive amount of ports established (roughly 600). How can I tell what each of these ports are being used for? (1 Reply)
Discussion started by: lastchance551
1 Replies

5. Solaris


Hi, If for example i try to start tomcat in a solaris server and get errors related to address already in use, how can I know if this port is really used for another process? If someone can point any documentation it will be very helpfull. Thanks! :rolleyes: (9 Replies)
Discussion started by: ffpradella
9 Replies

6. Solaris

regarding ports

Hi , I need one help... Is there any command on solaris 10 to free the ports. For e.g I used netstat -na| grep 8080 it displays either it is listening or established.. i want to free the ports... Anyone please help me on this... Thanks, Shanmuga (2 Replies)
Discussion started by: shanshine
2 Replies

7. Cybersecurity

help with discovering bad passwords question

Is there of a scheme for discovering badly chosen user passwords from a Unix password file? Im not learning anything bad or trying to hack,this a question that was given to me in an information security seminar. Would password cracker be a correct answer? (1 Reply)
Discussion started by: jodders
1 Replies

8. UNIX for Dummies Questions & Answers


Hello UNIX people... This is my first foray into the UNIX world so go easy on me... I have a client who has hired me to do some work on his windows stuff, BUT it just so happens his UNIX server started giving him problems... He is running SCO Open Server 5.0.6 The TTY ports won't... (5 Replies)
Discussion started by: TechKnow
5 Replies

9. IP Networking


What are some good sites that list all TPC/UDP ports? ~thanks (3 Replies)
Discussion started by: ireeneek
3 Replies

10. IP Networking


Ok, I've been working in the IT field for about 3 years now and I never fully understood the concept of ip ports. I just started a new job that uses Solaris and today it kinda clicked in my head and I want to know if I'm right or wrong. Does each ip address have multiple ports. because we... (4 Replies)
Discussion started by: eloquent99
4 Replies
Login or Register to Ask a Question
NC(1)							    BSD General Commands Manual 						     NC(1)

nc -- arbitrary TCP and UDP connections and listens SYNOPSIS
nc [-e command] [-g intermediates] [-G hopcount] [-i interval] [-lnrtuvz] [-o filename] [-p source port] [-s ip address] [-w timeout] [hostname] [port[s...]] DESCRIPTION
The nc (or netcat) utility is used for just about anything under the sun involving TCP or UDP. It can open TCP connections, send UDP pack- ets, listen on arbitrary TCP and UDP ports, do port scanning, and source routing. Unlike telnet(1), nc scripts nicely, and separates error messages onto standard error instead of sending them to standard output, as telnet(1) does with some. Destination ports can be single integers, names as listed in services(5), or ranges. Ranges are in the form nn-mm, and several separate ports and/or ranges may be specified on the command line. Common uses include: o simple TCP proxies o shell-script based HTTP clients and servers o network daemon testing o source routing based connectivity testing o and much, much more The options are as follows: -e command Execute the specified command, using data from the network for stdin, and sending stdout and stderr to the network. This option is only present if nc was compiled with the GAPING_SECURITY_HOLE compile time option, since it allows users to make arbitrary programs available to anyone on the network. -g intermediate-host Specifies a hop along a loose source routed path. Can be used more than once to build a chain of hop points. -G pointer Positions the "hop counter" within the list of machines in the path of a source routed packet. Must be a multiple of 4. -i seconds Specifies a delay time interval between lines of text sent and received. Also causes a delay time between connections to multiple ports. -l Is used to specify that nc should listen for an incoming connection, rather than initiate a connection to a remote host. Any host- name/IP address and port arguments restrict the source of inbound connections to only that address and source port. -n Do not do DNS lookups on any of the specified addresses or hostnames, or names of port numbers from /etc/services. -o filename Create a hexadecimal log of data transferred in the specified file. Each line begins with ``<'' or ``>''. ``<'' means "from the net" and ``>'' means "to the net". -p port Specifies the source port nc should use, subject to privilege restrictions and availability. -r Specifies that source and/or destination ports should be chosen semi-randomly instead of sequentially within a range or in the order that the system assigns. -s hostname/ip-address Specifies the IP of the interface which is used to send the packets. On some platforms, this can be used for UDP spoofing by using ifconfig(8) to bring up a dummy interface with the desired source IP address. -t Causes nc to send RFC854 DON'T and WON'T responses to RFC854 DO and WILL requests. This makes it possible to use nc to script telnet sessions. The presence of this option can be enabled or disabled as a compile-time option. -u Use UDP instead of TCP. On most platforms, nc will behave as if a connection is established until it receives an ICMP packet indi- cating that there is no program listening to what it sends. -v Verbose. Cause nc to display connection information. Using -v more than once will cause nc to become even more verbose. -w timeout Specifies the number of seconds nc should wait before deciding that an attempt to establish a connection is hopeless. Also used to specify how long to wait for more network data after standard input closes. -z Specifies that nc should just scan for listening daemons, without sending any data to them. Diagnostic messages about refused con- nections will not be displayed unless -v is specified twice. EXAMPLES
nc Wait for the user to type what would normally be command-line arguments in at stdin. nc 42 Open a TCP connection to port 42 of If the connection fails, do not display any error messages, but simply exit. nc -p 31337 42 Open a TCP connection to port 42 of, and use port 31337 as the source port. nc -w 5 42 Open a TCP connection to port 42 of, and time out after five seconds while attempting to connect. nc -u 53 Send any data from stdin to UDP port 53 of, and display any data returned. nc -s 42 Open a TCP connection to port 42 of using as the IP for the local end of the connection. nc -v 42 Open a TCP connection to port 42 of, displaying some diagnostic messages on stderr. nc -v -v 42 Open a TCP connection to port 42 of, displaying all diagnostic messages on stderr. nc -v -z 20-30 Attempt to open TCP connections to ports 20 through 30 of, and report which ones nc was able to connect to. nc -v -u -z -w 3 20-30 Send UDP packets to ports 20-30 of, and report which ones did not respond with an ICMP packet after three seconds. nc -l -p 3000 Listen on TCP port 3000, and once there is a connection, send stdin to the remote host, and send data from the remote host to stdout. echo foobar | nc 1000 Connect to port 1000 of, send the string "foobar" followed by a newline, and move data from port 1000 of to std- out until closes the connection. SEE ALSO
cat(1), telnet(1) The netcat README. AUTHOR
*Hobbit* [] BSD
August 1, 1996 BSD