05-09-2019
Check telnet port multiple server
Dear Team,
I want to check multiple linux server to check port open.
eg. 192.168.1.12 80,192.168.1.12 443
Please provide script for that?
Last edited by rbatte1; 05-09-2019 at 10:24 AM..
10 More Discussions You Might Find Interesting
1. Solaris
we disabled telnet on solaris 9 via previous a thread. We use CMS (call management system) supervisor which used port 23 (telnet). We cannot use telnet via local directive and it was shut down as stated when we shut down telnet in the inetd file. I cannot now log into the CMS box since port 23 is... (3 Replies)
Discussion started by: panzerkw
3 Replies
2. Shell Programming and Scripting
Hi,
I would like to create a simple script that will telnet a number of IP and Ports one after the other to confirm connectivity to those addresses.
I don't need to log on, just output to a file what the response is, i.e Escape Character, connectivity refused etc.
Complete newbie to... (6 Replies)
Discussion started by: asou
6 Replies
3. AIX
can some one help me ?
what happens when we telnet to a port ?
example
telnet 192.168.0.xx 1234
where 1234 is a port number
Thank you (5 Replies)
Discussion started by: anwesh
5 Replies
4. Windows & DOS: Issues & Discussions
Hello all.
I have an old computer with M$-DOS 7. I want to use it like a dumb terminal, with telnet. I need to connect it to my desktop These are my questions:
How can i configure the serial port on dos?
How can i telnet form dos to the serial port?
How can i set up a telnet server on the... (12 Replies)
Discussion started by: mghis
12 Replies
5. Cybersecurity
Hi, we have recently setup a new UNIX server with solaris 10 and I am having issue with with SMTP/sendmail.
telnet localhost 25 --- works
telnet hostname.domain.com 25 -- does not work.
# telnet hostname.domain.com 25
Trying 10.122.1.111...
telnet: Unable to connect to remote host:... (1 Reply)
Discussion started by: esmgr
1 Replies
6. Red Hat
My linux version is 2.6.18-194.e14 (Oracle enterprise linux).
Could you please tell me how to enable telnet on the server.
When I try to connect the server through another pc using telnet it is throwing error.
Connecting To <ip address>...Could not open connection to the host, on port 23.... (3 Replies)
Discussion started by: oradba_arun
3 Replies
7. HP-UX
Hi,
I have an application running on HP-UX, from this application I need to findout if the port number. lets say 7890,7891, 7892 are listening on the remote server running on HP-UX.
Is there any way of doing it using "system()" function or any other?
I noticed that nmap, netcat are not... (0 Replies)
Discussion started by: einsteinBrain
0 Replies
8. IP Networking
Hi,
I am trying to set up a dev environment and I have Ubuntu server (10.16.1.92) and a CentOS VM (10.16.3.235) on this. On the CentOS I have a program running on port 5433. Now my problem is that I am unable to telnet this port from another Windows server whereas I can telnet port 22 from... (5 Replies)
Discussion started by: rishav
5 Replies
9. Shell Programming and Scripting
Hello EveryOne,
I am new to *ix. some could help to write a script.
Problem :- Have to ssh to so many client and check port or filesystem usage, so thinking to automate using script.
What i Need:- when i run script on my Launchpad server, it should
Should ask and SSH to user provided... (3 Replies)
Discussion started by: MeFirst
3 Replies
10. Shell Programming and Scripting
Hi,
I do a telnet to a single server using command :telnet tibserver001 9640
The output i get is :
Trying 10.19....
Connected to tibserver001
However i need to put all the servers in a single file and get the output to see if the server is connected or not.
#! /bin/bash
telnet... (3 Replies)
Discussion started by: samrat dutta
3 Replies
LEARN ABOUT DEBIAN
shorewall-exclusion
SHOREWALL-EXCLUSION(5) [FIXME: manual] SHOREWALL-EXCLUSION(5)
NAME
exclusion - Exclude a set of hosts from a definition in a shorewall configuration file.
SYNOPSIS
!address-or-range[,address-or-range]...
!zone-name[,zone-name]...
DESCRIPTION
The first form of exclusion is used when you wish to exclude one or more addresses from a definition. An exclaimation point is followed by
a comma-separated list of addresses. The addresses may be single host addresses (e.g., 192.168.1.4) or they may be network addresses in
CIDR format (e.g., 192.168.1.0/24). If your kernel and iptables include iprange support, you may also specify ranges of ip addresses of the
form lowaddress-highaddress
No embedded whitespace is allowed.
Exclusion can appear after a list of addresses and/or address ranges. In that case, the final list of address is formed by taking the first
list and then removing the addresses defined in the exclusion.
Beginning in Shorewall 4.4.13, the second form of exclusion is allowed after all and any in the SOURCE and DEST columns of
/etc/shorewall/rules. It allows you to omit arbitrary zones from the list generated by those key words.
Warning
If you omit a sub-zone and there is an explicit or explicit CONTINUE policy, a connection to/from that zone can still be matched by the
rule generated for a parent zone.
For example:
/etc/shorewall/zones:
#ZONE TYPE
z1 ip
z2:z1 ip
...
/etc/shorewall/policy:
#SOURCE DEST POLICY
z1 net CONTINUE
z2 net REJECT
/etc/shorewall/rules:
#ACTION SOURCE DEST PROTO DEST
# PORT(S)
ACCEPT all!z2 net tcp 22
In this case, SSH connections from z2 to net will be accepted by the generated z1 to net ACCEPT rule.
In most contexts, ipset names can be used as an address-or-range. Beginning with Shorewall 4.4.14, ipset lists enclosed in +[...] may also
be included (see shorewall-ipsets[1] (5)). The semantics of these lists when used in an exclusion are as follows:
o !+[set1,set2,...setN] produces a packet match if the packet does not match at least one of the sets. In other words, it is like NOT
match set1 OR NOT match set2 ... OR NOT match setN.
o +[!set1,!set2,...!setN] produces a packet match if the packet does not match any of the sets. In other words, it is like NOT match set1
AND NOT match set2 ... AND NOT match setN.
EXAMPLES
Example 1 - All IPv4 addresses except 192.168.3.4
!192.168.3.4
Example 2 - All IPv4 addresses except the network 192.168.1.0/24 and the host 10.2.3.4
!192.168.1.0/24,10.1.3.4
Example 3 - All IPv4 addresses except the range 192.168.1.3-192.168.1.12 and the network 10.0.0.0/8
!192.168.1.3-192.168.1.12,10.0.0.0/8
Example 4 - The network 192.168.1.0/24 except hosts 192.168.1.3 and 192.168.1.9
192.168.1.0/24!192.168.1.3,192.168.1.9
Example 5 - All parent zones except loc
any!loc
FILES
/etc/shorewall/hosts
/etc/shorewall/masq
/etc/shorewall/rules
/etc/shorewall/tcrules
SEE ALSO
shorewall(8), shorewall-accounting(5), shorewall-actions(5), shorewall-blacklist(5), shorewall-hosts(5), shorewall_interfaces(5),
shorewall-ipsets(5), shorewall-maclist(5), shorewall-masq(5), shorewall-nat(5), shorewall-netmap(5), shorewall-params(5),
shorewall-policy(5), shorewall-providers(5), shorewall-proxyarp(5), shorewall-rtrules(5), shorewall-routestopped(5), shorewall-rules(5),
shorewall.conf(5), shorewall-secmarks(5), shorewall-tcclasses(5), shorewall-tcdevices(5), shorewall-tcrules(5), shorewall-tos(5),
shorewall-tunnels(5), shorewall-zones(5)
NOTES
1. shorewall-ipsets
http://www.shorewall.net/manpages/shorewall-ipsets.html
[FIXME: source] 06/28/2012 SHOREWALL-EXCLUSION(5)