Telnet service broken?
I recently acquired a ultra 25 running Solaris 10 that seems to have a broken telnet service. Any help appreciated.
Yes, I still have some devices that don't support ssh :)
Inbound telnet is blocked by ipf.
When I try to telnet out I get
$ telnet anyhost.anywhere
anyhost.anywhere: service name not available for the specified socket type
svcs shows
# svcs | grep telnet
maintenance15:44:18 svc:/network/telnet:default
When I try to restart the service (and at bootup) I see these console messages:
inetd[214]: [ID 702911 daemon.error] Property 'name' of instance svc:/network/telnet:default is missing, incon sistent or invalid
inetd[214]: [ID 702911 daemon.error] Property 'proto' of instance svc:/network/telnet:default is missing, inconsistent or invalid
inetd[214]: [ID 702911 daemon.error] Invalid configuration for instance svc:/network/telnet:default, placing in maintenance
[968 byte] By [
cmiller] at [2007-11-26 11:19:10]
# 1
Hi,
I had a similar problem with a service while setting up a cvs server. The service was put into maintenance mode and when I tried to restart it the following message appeared in syslog:
Apr 11 11:35:08 vts3 inetd[7250]: [ID 702911 daemon.error] Property 'proto' of instance svc:/network/cvspserver/tcp:default is missing, inconsistent or invalid
Apr 11 11:35:08 vts3 inetd[7250]: [ID 702911 daemon.error] Invalid configuration for instance svc:/network/cvspserver/tcp:default, placing in maintenance
I found out that if a system uses NIS or LDAP a line like this in nsswitch.conf can cause problems:
# cat /etc/nsswitch.conf
networks:ldap [NOTFOUND=return] files
protocols: ldap [NOTFOUND=return] files
rpc:ldap [NOTFOUND=return] files
ethers:ldap [NOTFOUND=return] files
netmasks:ldap [NOTFOUND=return] files
I moved the "[NOTFOUND=return]" to the end and rebooted the machine (because I dont know how to reread nsswitch.conf). Now all services which were on maintenance before (about 10) are online..
Seams that this was the problem for me..
# 2
Hello.
What does inetadm -l telnet
say?
Perhaps you may use "inetadm" to repair the problem. On my computer the following is returned:
# inetadm -l telnet
SCOPENAME=VALUE
name="telnet"
endpoint_type="stream"
proto="tcp6"
isrpc=FALSE
wait=FALSE
exec="/usr/sbin/in.telnetd"
user="root"
default bind_addr=""
default bind_fail_max=-1
default bind_fail_interval=-1
default max_con_rate=-1
default max_copies=-1
default con_rate_offline=-1
default failrate_cnt=40
default failrate_interval=60
default inherit_env=TRUE
default tcp_trace=FALSE
default tcp_wrappers=FALSE
Please look for "telnet" in /etc/services, too.
Martin
