Sponsored Content
Operating Systems AIX Telnet is not happening on port number 8080 Post 302946773 by bakunin on Friday 12th of June 2015 04:21:16 AM
Old 06-12-2015
As it is, the AIX telnetd looks up /etc/services when it starts. I forgot to mention that in my first post because it is in the man page and i thought it to be obvious. To configure such a service for a specific port you do the following (note that you might have to change some details for your purpose, the picture should be clear anyways):

enter a line in /etc/services defining a (best unique) service name and the port:

Code:
telnet8080          8080/tcp

Then modify your /etc/inetd.conf by adding a line to define this service:

Code:
telnet8080    stream    tcp   nowait  root    /usr/sbin/telnetd       telnetd

finally you ned to restart inetd, which is controlled by the System Resource Controller:

Code:
root@yourhost # refresh -s inetd

To test the connection try:

Code:
user@remotesystem # telnet yourhost 8080

You might further test with

Code:
user@yourhost # netstat -a | grep LISTEN
[...]
tcp        0      0  *.telnet8080           *.*                    LISTEN
[...]

which should show your daemon listening to the port.

I hope this helps.

bakunin
This User Gave Thanks to bakunin For This Post:
 

10 More Discussions You Might Find Interesting

1. IP Networking

Resolving port 8080 in DNS

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

enabling port 8080

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

Ping is happening, telnet is not happening

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

Ping/Telnet is not happening

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

disabled telnet now need port 23 or port 22

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

Monitoring the network activity happening in a port in AIX 5.3

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

telnet for port 5433 is not working while it works for port 22

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

telnet echoing 'trying ip' but no port number

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

Unable to Open port 8080

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

How to find port number wwn of particular port on dual port HBA,?

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
inetd.conf(4)						     Kernel Interfaces Manual						     inetd.conf(4)

NAME
inetd.conf, inetd.conf.local - The default configuration files for the inetd daemon SYNOPSIS
The default configuration file for all cluster members is: /etc/inetd.conf The configuration file for a specific member in a cluster is: /etc/inetd.conf.local The inetd.conf.local file is a Context-Dependent Symbolic Link (CDSL) and must be maintained as such. See the System Administration manual for more information. DESCRIPTION
If the inetd daemon is started without specifying an alternate configuration file, the inetd daemon reads the inetd.conf file and inetd.conf.local file, in this order, for information on how to handle Internet service requests. For this reason, if an entry exists in both configuration files, the entry in /etc/inetd.conf.local overrides the entry in /etc/inetd.conf. The inetd daemon reads its configuration files only when the inetd daemon starts or when the inetd daemon receives a SIGHUP signal. Each line in theinetd configuration files defines how to handle one Internet service request. Each line is of the form: ServiceName SocketType ProtocolName Wait/NoWait UserName ServerPath ServerArgs (Note: The backslash and the continuation of information on to a second line is for display purposes only. In the configuration file, the entries appear on a single line.) These fields must be separated by spaces or tabs. Continuation lines are terminated with a (backslash). Comments are denoted with a # (number sign). The fields have the following meanings: Specifies the name of an Internet service defined in the /etc/services file. For services provided internally by the inetd daemon, this name must be the official name of the service. That is, the name must be identical to the first entry on the line that describes the service in the /etc/services file. Specifies the name for the type of socket used for the service. You can use either the stream value for a stream socket, the dgram value for a datagram socket, the raw value for a raw socket, the rdm value for a reliably delivered message socket, or the seqpacket value for a sequenced packet socket. You can also use xstream and xdgram to permit the transparent mode of connections for stream and datagram sockets, respectively. Currently, only applica- tion gateways for firewall services use the transparent mode of connection. Specifies the name of an Internet protocol defined in the /etc/protocols file. For example, use the tcp value for a service that uses the TCP/IP protocol and the udp value for a service that uses the UDP protocol. When you use a tcp or udp value, inetd creates AF_INET sockets; this is the default behavior. If you want inetd to create AF_INET6 sockets, use the tcp6 or udp6 value. The inetd daemon maps these values to the tcp and udp protocol names internally. For RPC services the field consists of the string rpc followed by a slash (/) and one of the following: An asterisk (*) One or more nettypes One or more netids A combination of nettypes and netids If you specify an invalid nettype, it is treated as a netid. For example, if you specify rpc/*, it specifies the service uses all the transports supported by the system. Contains either the wait or the nowait instruction. For datagram servers, specify wait. This instructs the inetd daemon to wait for a datagram server to read at least one datagram from the socket before exiting. Single- threaded datagram servers process all incoming datagrams, then they time out (for example, comsat, biff, and talkd). Multithreaded datagram servers read one datagram from the socket, create a new socket, then fork and exit (for example, tftpd). For servers using stream sockets, specify nowait for multithreaded servers. This instructs inetd to accept connection requests and pass a newly accepted socket that is connected to the client of the service to the server. Specify wait for single-threaded servers. This instructs inetd to pass the listening socket to the server and wait. The server must accept at least one connection request before exiting. Specifies the username that the inetd daemon should use to start the server. This variable allows a server to be given less permission than root. Specifies the full pathname of the server that the inetd daemon should execute to provide the service. For services that the inetd daemon provides internally, this field should be internal. If you want to disable this service, this field should be disable in the /etc/inetd.conf.local file. Specifies the command line arguments that the inetd daemon is to pass to the server specified in ServerPath. The arguments to ServerPath should be just as they normally are, starting with the name of the program. For services that the inetd daemon provides internally, this field should be blank. EXAMPLES
The following are sample entries in the /etc/inetd.conf file for an inetd daemon that: Uses the ftpd daemon for servicing ftp requests on an AF_INET6 socket Uses the talkd daemon for ntalk requests on an AF_INET socket Provides time requests internally on AF_INET6 sockets ftp stream tcp6 nowait root /usr/sbin/ftpd ftpd ntalk dgram udp wait root /usr/sbin/talkd talkd time stream tcp6 nowait root internal time dgram udp6 wait root internal How you enable and disable services in a cluster depends on the number of cluster members. The following two examples show the same clus- ter that has three members (0, 1, and 2), but shows two diferent methods to accomplish the same goal. Choose the method most suitable to your cluster environment. If you want to enable the ftpd daemon on all cluster members except member 2, do the following: To enable the ftpd daemon for all members, enter the following in the /etc/inetd.conf file: ftp stream tcp nowait root /usr/sbin/ftpd ftpd To disable the ftpd daemon for member 2, enter the following in the /etc/inetd.conf.local for member 2: ftp stream tcp nowait root disable If you want to disable the ftpd daemon on all cluster members (the whole cluster), but enable it on members 0 and 1, do the following: To disable the ftpd daemon by default for the whole cluster, enter the following in the /etc/inetd.conf file: #ftp stream tcp nowait root /usr/sbin/ftpd ftpd To enable the ftpd daemon for member 0, enter the following in the /etc/inetd.conf.local file for member 0: ftp stream tcp nowait root /usr/sbin/ftpd ftpd To enable the ftpd daemon for member 1, enter the following in the /etc/inetd.conf.local file for mem- ber 1: ftp stream tcp nowait root /usr/sbin/ftpd ftpd Member 2 does not have an ftpd entry in its /etc/inetd.conf.local file. Therefore, the ftpd daemon is not started. RELATED INFORMATION
Commands: biff(1), comsat(8). Daemons: inetd(8), talkd(8), tftpd(8). Files: protocols(4), services(4). delim off inetd.conf(4)
All times are GMT -4. The time now is 10:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy