Telnet Problem

[Bruno Vilardo]

Hello All.

I have the TRU64 V4.0 version
I am having a problem to connect from a workstation to the server thru Telnet.
I can ping the Server, in the /etc/inetd.conf file the telnet is configured and also in the /etc/services file the telnet is configured and is using the default port 23.
I also started the inetd using the inetd start script.
And after checked all of these still doesn´t work.

Does anybody know what might be happening?
Thanks everyone
Bruno Vilar

[G. Vrijhoeven · Accepted solution]

HI Bruno,

Are you able to telnet locally once logged in on the server.
# telnet 0

Can do you get a login prompt or just connectoin refused?

Gideon

[Bruno Vilardo]

Yes i am able to telnet locally.

I try to telnet but the cursor only blinks and nothing happens.

I checked the daemon log and i get the following message:

inetd: [14592]: Cannot register service: RPC:
time out


Thanks for you help
Appreciate
Bruno Vilardo

[Bruno Vilardo]

Hello again .

I am sorry but i can´t telnet locally using the Telnet 0.

Regards
Brun

[Michael Schulte zur Sur]

Hi,

is the portmapper daemon running?

Michael

[Bruno Vilardo]

Yes the portmapper daemon is running ..

TKS

Bruno

[Johan Brusche]

Bruno, could you please post the outcome of the following commands on the Tru64 V4.0 server :

grep telnet /etc/inetd.conf
ps aux | grep -E "port|inet|telnet"
rpcinfo -p | grep port
netstat -an | grep "\.23"

[Bruno Vilardo]

Here you are.


grep telnet /etc/inetd.conf

telnet stream tcp nowait root /usr/sbin/telnetd telnetd


ps aux | grep -E "port|inet|telnet"
root 1425 0.0 0.0 1.75M 184K ?? I 14:20:01 0:00.01 /usr/sbi
n/inetd
root 9631 0.0 0.0 2.21M 152K ?? I 14:45:48 0:00.00 ./portma
p
root 11275 0.0 0.0 1.83M 232K ?? S 14:50:50 0:00.03 telnetd
root 12134 0.0 0.0 1.83M 240K ?? I 14:53:38 0:00.01 telnetd
root 19863 0.0 0.0 1.85M 360K ttyp2 S + 15:17:31 0:00.00 grep -E
port|inet|telnet

rpcinfo -p | grep port
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper

netstat -an | grep "\.23"
tcp 0 0 127.0.0.1.4892 127.0.0.1.2301 TIME_WAIT
tcp 0 0 127.0.0.1.4901 127.0.0.1.2301 TIME_WAIT
tcp 0 0 10.251.36.37.23 198.132.2.62.1241 ESTABLISHED
tcp 0 0 127.0.0.1.4914 127.0.0.1.2301 TIME_WAIT
tcp 0 0 127.0.0.1.4930 127.0.0.1.2301 TIME_WAIT
tcp 0 0 127.0.0.1.4941 127.0.0.1.2301 TIME_WAIT
tcp 0 0 127.0.0.1.4955 127.0.0.1.2301 TIME_WAIT
tcp 0 2 10.251.36.37.23 10.251.38.47.1916 ESTABLISHED
tcp 0 0 *.23 *.* LISTEN
tcp 0 0 *.2301 *.* LISTEN
udp 0 0 10.251.36.37.2301 *.*
udp 0 0 *.2301 *.*

Thanks a lot

[Johan Brusche]

Bruno,

The posted info shows that there are 2 established telnet sessions on the server, one from system 198.132.2.62 and one from 10.251.38.47 .
Each telnetd (PID 11275 and 12134) should have an associated running shell, ie the daemon is the parent of a shell.
"ps ef | grep -e 11275 -e 12134" will show you the pid's of these shells.

Maybe the telnetd that's in "S" mode, does not have a child shell and is stuck in sleep-mode, so you could try to issue a "kill -9" against it's pid.

Johan.

[Al Licause]

How long are you waiting before aborting the telnet attempt ?

Are you using an ip address or a hostname to make the connection ?

If using a hostname, try an ip address. This may a reverse name lookup issue.

Can you ftp to the same system using either a hostname or ip address ?

[Alexey Borchev]

If you've got 2 telnet sessions already established, then it may be licencing issues.

As far as I remeber, 2 logons are granted anyway, but more than that require all licences to be configured.

Please check your console log & event logs for messages like "OFS BASE or OSF-SVR licences not loaded"
or "Maximum nuber of users exeeded".

[Bruno Vilardo]

Thanks for the Help !!!
Now the telnet is working fine ...
I checked some files to be configured and it´s working ..
I appreciate all your help
Thanks all

Bruno Vilar