Sponsored Content
Top Forums UNIX for Advanced & Expert Users 30 tcp connections Established for a while and after a few minutes are close Post 303030676 by alexcol on Wednesday 13th of February 2019 08:37:05 PM
Old 02-13-2019
Thanks you very much for your support and explanation, it is useful for me to grow. Unfortunately i dont have enough documentation at hand for every party (ip adresses,ports, services and so on) to provide and to keep the resolution . AS soon as i get this i will let you know. THanks once again for your support
This User Gave Thanks to alexcol For This Post:
 

10 More Discussions You Might Find Interesting

1. Programming

C Prog to close a socket in established state

I have a SUN environment running an WebLogic that communicates w/a 3rd party running IIS. When the IIS site goes down (frequently), I am stuck with sockets in an ESTABLISHED state, and cannot seem to figure out how to avoid this. No exceptions are thrown as I can still open connections to the IIS... (1 Reply)
Discussion started by: teledelux
1 Replies

2. UNIX for Dummies Questions & Answers

close tcp port

Hello, I have a service running (ODBC) and every now and then it will hang and I will have to stop and restart the service. The problem is when I stop the service, it indeed stops the service, but netstat reports a tcp port still open with the fin_wait_2 status. Then I must close the client... (1 Reply)
Discussion started by: raidzero
1 Replies

3. Programming

close existing tcp connection in C

Hello. I would like to know how to close an existing tcp socket. I have read some stuff and learned how to create a socket and then close it but have not found anything about how to close an existing tcp socket created by another application. The situation is this: I have an ODBC server running and... (6 Replies)
Discussion started by: raidzero
6 Replies

4. Red Hat

How to kill all active tcp connections from an IP?

How to kill all active tcp connections from an IP? I am using CentOS (3 Replies)
Discussion started by: an00p
3 Replies

5. Solaris

How to kill the TCP ESTABLISHED connection in netstat

Hello, Actually there are some bugs in application which does not close the TCP connection to other server though CORBA. We need to kill that ESTABLISHED connections as new connection are not happeneing as the allocated ports were used and showing as ESTABLISHED Is there any... (4 Replies)
Discussion started by: GIC1986
4 Replies

6. Solaris

Established connections causing lag?

I'm not to sure how to go about this questions, so I will just ask it and then get criticized. How many Established connections should a V440 be able to support? (4 Replies)
Discussion started by: adelsin
4 Replies

7. Programming

TCP trashing data on application close

I am using c to send data to a socket with the following commands: socket = socket(AF_INET, SOCK_STREAM, ptrp->p_proto); ioctl(socket, FIONBIO, (char *)&on); connect(socket) send(socket,data) shutdown(socket, SHUT_WR); recv(socket) //ready last of data waiting on the port //note this is... (3 Replies)
Discussion started by: metrix
3 Replies

8. IP Networking

How to test max number of tcp connections

Hello, I wanna test max tcp connection value. Please suggest how to do that. Thanks. (2 Replies)
Discussion started by: gstoychev
2 Replies

9. Solaris

many tcp connection in close-wait

Hi, I use solaris Unix . I find there is some problem in application and it generate many "close-wait" tcp connect and stay in the server . it is generate by process id 7740 root@XX # netstat -an | grep CLOSE_WAIT | wc -l 285 root@XX # netstat -an | grep CLOSE_WAIT 10.158.35.4.34805 ... (2 Replies)
Discussion started by: abcdef
2 Replies

10. IP Networking

Need to know reason for connections closed in netstat -p tcp

Hello netstat -p give below 6634176 connections as closed.How do we trace that which all connections are being closed on the server? 1366888371 data packet headers correctly predicted 1195906 connection requests 5227320 connection accepts 5992919... (6 Replies)
Discussion started by: Vishal_dba
6 Replies
scanssh(1)						    BSD General Commands Manual 						scanssh(1)

NAME
scanssh -- scans the Internet for open proxies and SSH servers SYNOPSIS
scanssh [-VIERph] [-s scanners,...] [-n ports,...] [-e excludefile] addresses... DESCRIPTION
ScanSSH scans the given addresses and networks for running services. It mainly allows the detection of open proxies and Internet services. For known services, ScanSSH will query their version number and displays the results in a list. The adresses can be either specified as an IPv4 address or an CIDR like IP prefix, ipaddress/masklength. Ports can be appended by adding a colon at the end of address specification. Additionally, the following two commands can be prefixed to the address: random(n[,seed])/ The random command selects random address from the address range specified. The arguments are as follows: n is the number of address to randomly create in the given network and seed is a seed for the pseudo random number generator. split(s,e)/ The split command is used to split the address range in several unique components. This can be use to scan from serveral hosts in parallel. The arguments are as follows: e specifies the number of hosts scanning in parallel and s is the number of the host this particular scan runs on. The options are as follows: -V Causes scanssh to print its version number. -I Does not send a SSH identification string. -E Exit the program, if the file containing the addresses for exclusion can not be found. -R If addresses are generated at random, this flag causes the program to ignore excluded addresses from the exclude file. The default behaviour is to always exclude addresses. -p Specifies that ScanSSH should operate as a proxy detector. This flag sets the default modes and default scanners to detect open proxies. -h Displays the usage of the program. -n ports,... Specifies the port numbers to scan. Ports are separated by commas. Each specified scanner is run for each port in this list. The default is 22. -s scanners Specifies a number of scanners should be executed for each open port. Multiple scanners are separated by commas. The fol- lowing scanners are currently supported: ssh Finds versions for SSH, Web and SMTP servers. socks5 Detects if a SOCKS V5 proxy is running on the port. socks4 Detects if a SOCKS V4 proxy is running on the port. http-proxy Detects a HTTP get proxy. http-connect Detects a HTTP connect proxy. telnet-proxy Detects telnet based proxy servers. -e excludefile Specifies the file that contains the addresses to be excluded from the scan. The syntax is the same as for the addresses on the command line. The output from scanssh contains only IP addresses. However, the IP addresses can be converted to names with the logresolve(8) tool included in the Apache webserver. EXAMPLES
The following command scans the class C network 10.0.0.0 - 10.0.0.255 for open proxies: scanssh -p 10.0.0.0/24 The next command scans for ssh servers on port 22 only: scanssh -n 22 -s ssh 192.168.0.0/16 The following command can be used in a parallel scan. Two hosts scan the specified networks randomly, where this is the first host: scanssh 'random(0,rsd)/split(1,2)/(192.168.0.0/16 10.1.0.0/24):22,80' BUGS
At the moment, scanssh leaves a one line entry in the log file of the ssh server. It is probably not possible to avoid that. BSD
July 17, 2000 BSD
All times are GMT -4. The time now is 03:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy