01-21-2008
I do not have access to man pages for old openserver versions. The the
a recent telnetd man page says:
Quote:
Telnetd is normally invoked by the internet server (see inetd(8)) for requests to connect to the TELNET port as indicated by the /etc/services file (see services(5)).
This is a fairly standard way of doing things. This means that inetd selects the port, does the listen, and accepts the connection before telnetd ever runs. So you need to edit inetd.conf
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
This is not the usual "unable to telnet to my machine" post. I:
* have ensured that in.telnetd is started from inet.conf
* that hosts.allow/deny are correctly configured
* in.telnetd is listening, and on the correct port
When I check my syslog i notice that tcpd (as I have... (3 Replies)
Discussion started by: sam_pointer
3 Replies
2. IP Networking
/* Linux Slackware */
looking in my logs I see tons of entries similar to below. Does anyone know what these mean, and should I be concerned. I looked up a few of the IP's at Arin.net and saw that many of them belong to isp's (not good).. Any information is helpful..
Body of Messages log... (1 Reply)
Discussion started by: LowOrderBit
1 Replies
3. UNIX for Dummies Questions & Answers
I hope someone can enlighten me on this. A few weeks ago, the root file system my UnixWare 7.1.1 server became corrupt so I ended up doing a full restore of the OS from tape backup.
Since then, after I get about 270 users on the system, the message "telnetd: all network ports in use" is... (1 Reply)
Discussion started by: davekox
1 Replies
4. Cybersecurity
Hi folks. I have a quick question on using "telnetd" vs. "telnetd -a".
OS: AIX 5.x (5.1 through 5.3 ML3)
Some engineers at work want to stop using "telnetd -a" and use "telnetd".
(and of course, if I could get a cogent answer from them, I wouldn't be posting this question...) :mad:
The... (0 Replies)
Discussion started by: davidl9999
0 Replies
5. Solaris
hi mates,
a very important info for all solaris admins, there is a bug in telnetd on nearly every solaris version:
pressy@mp-wst01 # id
uid=100(pressy) gid=1(other)
pressy@mp-wst01 # telnet -l "-froot" 192.168.40.1
Trying 192.168.40.1...
Connected to 192.168.40.1.
Escape character is... (3 Replies)
Discussion started by: pressy
3 Replies
6. Solaris
Hello all,
I've got a problem on a V240 running Solaris 9, the telnet daemon won't start. The error message I get is "telnetd: stdin is not a socket file descriptor." I've never seen this message before and I'm not exactly sure what it means. I know generally what stdin, sockets, and file... (4 Replies)
Discussion started by: ONEX
4 Replies
7. AIX
Hi,
When a client connected to AIX server by telnet is killed/crashes, is there a way for telnetd to recognize that and close/kill the application linked/started by that telnet session?
We have a situation where clients disconnect because of frequent network outages, this leaves the... (2 Replies)
Discussion started by: mreyaz
2 Replies
8. 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 ULTRIX
telnetd
telnetd(8c) telnetd(8c)
Name
telnetd - DARPA TELNET protocol server
Syntax
/etc/telnetd
Description
The server supports the DARPA standard TELNET virtual terminal protocol. The TELNET server is invoked when receives a connection request
on the port indicated in the TELNET service description.
The server operates by allocating a pseudo-terminal device for a client, then creating a login process which has the slave side of the
pseudo-terminal as stdin, stdout, and stderr. The server manipulates the master side of the pseudo terminal, implementing the TELNET pro-
tocol and passing characters between the client and login process.
When a TELNET session is started up, sends a TELNET option to the client side indicating a willingness to do remote echo of characters, to
suppress go ahead, and to receive terminal type information from the remote client. If the remote client is willing, the remote terminal
type is propagated in the environment of the created login process. The pseudo terminal allocated to the client is configured to operate
in cooked mode and with XTABS and CRMOD enabled.
Aside from this initial setup, the only mode changes will carry out are those required for echoing characters at the client side of the
connection.
The server supports binary mode, suppress go ahead, echo, and timing mark. It also allows a remote client to do binary, terminal type, and
suppress go ahead.
Restrictions
Some TELNET commands are only partially implemented.
The TELNET protocol allows the exchange of the number of lines and columns on the user's terminal, but does not make use of them.
The terminal type name received from the remote client is converted to lower case.
The server never sends TELNET go ahead commands.
See Also
telnet(1c), pty(4), tty(4), services(5), inetd(8c)
telnetd(8c)