ux rejects telnet

[Tim Killinger]

I just installed (cold) UX on a rp5450. When I telnet from a remote host, it connects, but then ux rejects the session. Thru SAM, telent shows "system permission allowed".

Any hints?

Thanks!

[Robert Gamble]

Is inetd still running ?

[Tim Killinger]

telnetd is not running, and I don't know how to enable it.

[Tim Killinger]

inetd is running and contains a line:

telnet stream tcp nowait root /usr/lbin/telnetd telnetd -b /etc/warning.txt

[Marco Santerre]

Look in /etc/inetd.conf and make sure that the telnet line is not commented out or make sure it is there. It should look like this :
telnet stream tcp nowait root /usr/lbin/telnetd telnetd

Do a inetd -c after if you've made any changes to that file.

[Balaji N]

hi,

telnetd is started by inetd. if inetd is not running then telnetd wont get started.

see if it is running.

else /sbin/init.d/inetd start.

hth
-balaji

[Marco Santerre]

if inetd is running and your telnet line is not commented out, try running inetd -c to have your inetd.conf file re-configured.

[Patrick Wallek]

Check and see if you have a /var/adm/inetd.sec file. If you do check the contents as that file can be used to (dis)allow access via any of the inetd services.

[Marco Santerre]

if inetd is running and your telnet line is not commented out, try running inetd -c to have your inetd.conf file re-configured.

[Marco Santerre]

if inetd is running and your telnet line is not commented out, try running inetd -c to have your inetd.conf file re-configured.

[Marco Santerre]

if inetd is running and your telnet line is not commented out, try running inetd -c to have your inetd.conf file re-configured.

[Marco Santerre]

if inetd is running and your telnet line is not commented out, try running inetd -c to have your inetd.conf file re-configured.

[Marco Santerre]

if inetd is running and your telnet line is not commented out, try running inetd -c to have your inetd.conf file re-configured.

[Marco Santerre]

if inetd is running and your telnet line is not commented out, try running inetd -c to have your inetd.conf file re-configured.

[Tim Killinger]

I have a working machine that has no inetd.sec. The machine that I CANNOT telnet to has a inetd.sec and it looks like:

# Hosts and network names must be official names, not aliases.
# See the inetd.sec(4) manual page for more information.
dtspc allow 127.0.0.1 loopback
telnet allow
#

inetd -c does nothing to help and

inetd -k
followed by
/sbin/init.d/inetd start

doesn't change anything either.

[Umapathy S]

anything on syslog.log

[Marco Santerre]

Sorry for the many replies.. some strange reason IE screwed up on me

[Tim Killinger]

here's a clue... syslog.log says:

telnetd[1273]: I_LINK_DEV ioctl failed: Invalid argument

[Umapathy S]

Tim,

Check this link

http://bizforums.itrc.hp.com/cm/QuestionAnswer/0,,0x49a3854994d9d4118fef0090279cd0f9,00.html

HTH
Umapathy

[RolandH]

See waht I have found to your problem in the Knowledge Trees of HP.

document id: 4000041655

You may provide feedback on this document

PROBLEM

After installing a GR (General Release) Telnet patch on an HP-UX
11.0 system, all inbound telnet connections fail and the following
message is logged in /var/adm/syslog/syslog.log.

telnetd: I_LINK_DEV ioctl failed: Invalid argument

CONFIGURATION

Operating System - HP-UX
Version - 11.X
Subsystem - telnet

RESOLUTION

Telnet patches are comprised of telnet kernel and telnetd components.
If, for example, the kernel rebuild failed or the system was not
rebooted after the Telnet patch installation, then the Telnet patch
is only partially installed and the telnet kernel and telnetd user
space components may now be incompatible.

To correct this problem, use swremove(1M) to remove the partially
installed Telnet patch and then re-install it again using
swinstall(1M). Refer to the Telnet patch documentation to verify
that the patch is correctly installed.


ALT KEYWORDS

telnet
telnetd
"i_link_dev"
"telnetd: i_link_dev"
"telnetd: i_link_dev ioctl failed"
"telnetd: i_link_dev ioctl failed: invalid argument"

[V. V. Ravi Kumar_1]

hi,
search for the DOC Id 4000041655 in HP knowledge base


Regards