NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Alan, Based on the following information and my observation telnet'ing to waldo, I'd say this is an issue with TCP wrapper configuration. I note that I do get a connection, but it is immediately closed. This means that inetd is correctly reading inetd.conf and exec'ing a in.telnetd process to handle the connection attempt -- only to get shutdown by the TCP wrappers. First, check /etc/hosts.allow (and /etc/hosts.deny) to make sure connections are allowed from the systems attempting those connections. My guess is that the problem will be resolved there... BTW - I've never heard of /usr/hbtcp, nor do any of our systems have it. mike > >From: alan anderson <address@hidden> > >Subject: solarisx86 ver 7 and telnet > >Organization: St. Cloud State > >Keywords: 200005172010.e4HKAp409087 Solarisx86 telnet inetd.conf > > > Good Morning > > As Tom found earlier this month, waldo will not accept a telnet login > from a remote host, although I can telnet out of waldo. > I have checked with our campus system person and > also looked at the sun web site. > > Have looked at the inetd.conf file and things like file location and > size seem to be ok. Have also looked at another near identical terminal > with same OS and on which telnet sessions do work. Comparing > files such as /ect/inetd.conf and usr/sbin/in.telnetd shows they > are in same place, have same size, date permissions and so on. > > The only hint I found on the Sun web site (FAQ's about telnet) was for > what seemed like the same problem; i.e. can telnet out of the machine > but cannot telnet into it. The problem was explained as a corruption of > /etc/inetd.conf but was listed for OS vers. 4.1 > > The solution was to copy another version of the file as follows > > cp /usr/hbtcp/inetd.conf /etc/inetd.conf > > and then kill -1 the original inetd process. > > This looks like another copy of inetd.conf could be found in /usr/hbtcp > and used as a replacement. > On waldo, with Solaris ver. 5.7 , the directory /usr/hbtcp does not > exist, so I assume the above would not apply. I could not find > any other copies of inetd.conf on waldo, except the one in /etc . > > Should I try copying the file inetd.conf from one of our "good" machines > over to waldo and replacing its version of inetd.conf ? Not sure if > this is reasonable as initial check shows they are of same size, but > I suppose that does not mean that waldo's is a "good" version. > > Any other ideas as to how to correct this problem?