cancel
Showing results for 
Search instead for 
Did you mean: 

resmsh/telnet issue

SOLVED
Go to solution
Malps
Advisor

resmsh/telnet issue

Hi

I am trying to Boot a Client through Ignite. But Ignite can’t connect to the client & couldn’t start the ignition process. It suggests booting it manually but even that doesn’t work.

(/opt/ignite/bin/bootsys -wv -R B.11.11 pandora: 192.168.137.222 2>/var/tmp/baaa28530)

When I check the Error Log File “/var/tmp/baaa28530”

Fatal error on "pandora": (remsh error: rcmd_af: connect: 192.168.137.222: Connection refused)

I can ssh & ping the system but couldn’t Telnet to that system

# telnet 192.168.137.222
Trying...
telnet: Unable to connect to remote host: Connection refused

# telnet 0
Trying...
telnet: Unable to connect to remote host: Connection refused

I checked /etc/inetd.conf on the client but that has following entries (not hashed out)

login stream tcp6 nowait root /usr/lbin/rlogind rlogind

shell stream tcp6 nowait root /usr/lbin/remshd remshd

exec stream tcp6 nowait root /usr/lbin/rexecd rexecd

Then I checked $HOME/.rhosts file (logged in as root) which has following entry:

+ +

Also checked for /var/adm/inetd.sec & that has following entry

dtspc allow 127.0.0.1 loopback pandora

Checked /etc/services


exec 512/tcp # remote execution, passwd required

login 513/tcp # remote login
who 513/udp whod # remote who and uptime

shell 514/tcp cmd # remote command, no passwd used

& Finally Checked /var/admsyslogsyslog.log

Jan 29 10:48:15 inet30 inetd[7808]: Rereading configuration
Jan 29 10:48:15 inet30 inetd[7808]: telnet/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: login/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: shell/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: exec/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: daytime/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: daytime/udp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: time/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: echo/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: echo/udp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: discard/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: discard/udp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: chargen/tcp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: chargen/udp: socket: Protocol not supported
Jan 29 10:48:15 inet30 inetd[7808]: Thru with configuration
Jan 29 10:48:15 inet30 inetd[7808]: Configuration complete

I was trying to install an IPv6 Bundle on that client before reinstalling it.

But that installation failed while it was building kernel (at 24%)

The same bundle installed fine on my other 11.11 machine which was installed from the same depot server.

#netstat –in

Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
* 0 192.168.136.0 192.168.137.222 0 0 4278190080 0 0
0 0.0.48.0 0.0.255.255 9523848 0 0 0 0

What else can be checked?

I would appreciate if you all can help me to boot this client from ignite.

Also please advise on why the netstat output looks like this?
5 REPLIES
Robert Salter
Respected Contributor
Solution

Re: resmsh/telnet issue

Do you have an entry for telnet in /etc/inetd.conf? Looks like this

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

If you add it to inetd.conf be sure to run "inetd -c" to have the conf file re-read.


Beers,

robert
Time to smoke and joke
Robert Salter
Respected Contributor

Re: resmsh/telnet issue



Are those the only entries you have in inetd.conf? If so then you are missing one for telnetd. You could make a copy of you existing inetd.conf file and then copy the /usr/newconfig/etc/inetd.conf file to /etc/inetd.conf. Run "inetd -c" and try your telnet, then your ignite.
Time to smoke and joke
AVV
Super Advisor

Re: resmsh/telnet issue

Hi,

You must have to re-read the /etc/inetd.conf file after any editing on this by inetd -c .
Malps
Advisor

Re: resmsh/telnet issue

Thanks All of you!!!

The Issue is resolved now.

It was an issue with a corrupt IPv6 bundle.

That has caused the tcp/ip parameter values to change & hence the netstat -in o/p.

I have installled a new bundle now & things seem fine.

Thanks Again.
Malps
Advisor

Re: resmsh/telnet issue

Thanks