06-11-2015
Telnet is not happening on port number 8080
Dear Experts,
I am trying to open 8080 port on my Aix 7.1 server. I made an entry in /etc/services for the port. and refreshed the inetd service. But when I try to telnet localhost 8080, telnet is not happening. connection refused error is coming.
I can able to telnet localhost 23 its working fine, but its not working for 8080.
Can someone please help me on this?
Regards,
Rockie
10 More Discussions You Might Find Interesting
1. IP Networking
Hi
I have my DNS servers (BIND 8) running on two Solaris 8 boxes. I need to be able to resolve an address blah.xxx.net to an IP address followed by :8080 - (for Tomcat). I tried doing this in my zone file but it failed. Can someone give me a pointer on where this configuration should be done?... (1 Reply)
Discussion started by: korfnz
1 Replies
2. UNIX for Dummies Questions & Answers
hey everyone,
i have just finished configuring apache 2.0 with the php and pgsql modules installed on it.. httpd.conf is configured and everything is running right after a lengthy bit of reading and struggling with the system.. the only problem left is how do i enable the port that i would access... (3 Replies)
Discussion started by: moxxx68
3 Replies
3. AIX
HI all,
Ping is happening to a AIX box...but telnet is not happening...
AIX box doesn't have any conslole...
Please help how to resolve it.
Thanks in advance ..
Manu (2 Replies)
Discussion started by: b_manu78
2 Replies
4. AIX
Hi All,
We are not able to ping to a AIX box...Network is ok..when we give ping from that AIX box..it is giving 0821-067 ping: The socket creation call failed.there is no enough buffer space for the requested socket operation.
refresh -s inetd is also giving socket error.
Please help to... (1 Reply)
Discussion started by: b_manu78
1 Replies
5. 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
6. AIX
Hi All,
I would like to monitor the volume of Data that is transferred through a single port in AIX. I have nmon installed in my machine. What is the best possible solution for this problem.
Thanks in Advance. (3 Replies)
Discussion started by: bravo13
3 Replies
7. 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
8. UNIX for Dummies Questions & Answers
Hi,
Well this is probably a silly one that I should know...but I don't !
I'm telnetting to various ports from a shell script and the telnet is echoing back that it's 'trying xxx.xx.xx.xx...' but not the port number it's trying!
Any help much appreciated
Thanks (1 Reply)
Discussion started by: Grueben
1 Replies
9. Red Hat
Hi Experts,
I am receiving below error while trying to connect port 8080.
Could not open connection to the host, on port 8080 : connection refused.
iptables configuration
/etc/sysconfig/iptables
# Firewall configuration written by system-config-firewall
# Manual customization of... (1 Reply)
Discussion started by: sai_2507
1 Replies
10. Solaris
please find the below o/p for your reference
bash-3.00# fcinfo hba-port
HBA Port WWN: 21000024ff295a34
OS Device Name: /dev/cfg/c2
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 05.03.02
FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies
LEARN ABOUT CENTOS
telnet-probe
TELNET-PROBE(1) General Commands Manual TELNET-PROBE(1)
NAME
telnet-probe - lightweight telnet-like port probe
SYNOPSIS
$PCP_BINADM_DIR/telnet-probe [-c] [-v] host port
DESCRIPTION
telnet-probe allows the pmdashping(1) daemons to establish connections to arbitrary local and remote service-providing daemons so that
response time and service availability information can be obtained.
The required host and port number arguments have the same meaning as their telnet(1) equivalents.
The -c option causes telnet-probe to perform a connect(2) only. This skips the read(2) and write(2) exercise that would otherwise be done
after connecting (see below).
The -v option causes telnet-probe to be verbose while operating.
Once the telnet connection has been established, telnet-probe reads from stdin until end-of-file, and writes all the input data to the tel-
net connection. Next, telnet-probe will read from the telnet connection until end-of-file, discarding whatever data it receives. Then
telnet-probe exits.
To operate successfully, the input passed via telnet-probe to the remote service must be sufficient to cause the remote service to close
the connection when the last line of input has been processed, e.g. ending with ``quit'' when probing SMTP on port 25.
By default telnet-probe will not produce any output, unless there is an error in which case a diagnostic message can be displayed (in ver-
bose mode only) and the exit status will be non-zero indicating a failure.
PCP ENVIRONMENT
Environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP. On each installation, the
file /etc/pcp.conf contains the local values for these variables. The $PCP_CONF variable may be used to specify an alternative configura-
tion file, as described in pcp.conf(5).
DIAGNOSTICS
If telnet-probe succeeds, then 0 will be returned. If the attempt to establish a connection fails or is terminated, then a non-zero exit
status is returned.
SEE ALSO
PCPintro(1), pmdashping(1), pmie(1), telnet(1), connect(2), read(2) and write(2).
Performance Co-Pilot PCP TELNET-PROBE(1)