- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: telnet not accessible?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2011 01:41 PM
тАО01-19-2011 01:41 PM
telnet not accessible?
This one's got me buggered. I apparently need to enable telnet on an HPUX 11.00 system. Telnet's uncommented in /etc/inetd.conf and I'm able to telnet to localhost on the box.
No one off the box, though, can telnet to the system - we get a connection timed out error.
I've verified that telnet's not wrapped via tcpwrappers and that the /var/adm/inetd.sec file is all commented out.
The networking people swear there's no firewall between the system and anything else in the network.
Anyone have any ideas what may be blocking telnet on this antique?
Thanks for any hints/tips/suggestions.
Doug O'Leary
------
Senior UNIX Admin
O'Leary Computers Inc
linkedin: http://www.linkedin.com/dkoleary
Resume: http://www.olearycomputers.com/resume.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2011 01:55 PM
тАО01-19-2011 01:55 PM
Re: telnet not accessible?
> [...]
> [...] I'm able to telnet to localhost on
> the box.
That sounds enabled, doesn't it? How about
to its real interface name, not "localhost"?
Bad routes? (Can't see 'em from here.)
Firewall (external)? Is Telnet the only
service affected?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2011 02:35 PM
тАО01-19-2011 02:35 PM
Re: telnet not accessible?
did you remove the hash in the inetd.conf or was it always uncommented?
if you uncommented it did you run the inetd -c command to re-read the config file?
or have you checked the /etc/services file as well? check the port?
or use netstat to see if telnet is running something like this
#netstat -an |grep LISTEN |grep 23
Andy
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2011 03:45 PM
тАО01-19-2011 03:45 PM
Re: telnet not accessible?
I can ssh to the system so the network routes are good. I just checked and telnet/ftp both are unable to connect.
So, to rephrase:
1. I can connect to telnetd on the localhost
2. I can ssh to the system, ping it, etc.
3. telnetd/ftpd both get connection time outs.
4. network people say there's no firewall on the network affecting these protocols
5. telnet/ftp aren't wrapped, have always been uncommented, and /var/adm/inetd.sec is empty.
Any ideas?
Thanks.
Doug O'Leary
------
Senior UNIX Admin
O'Leary Computers Inc
linkedin: http://www.linkedin.com/dkoleary
Resume: http://www.olearycomputers.com/resume.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2011 04:08 PM
тАО01-19-2011 04:08 PM
Re: telnet not accessible?
Find new network people?
If you had enough loose junk lying around,
then you could run an experiment like: Take
a system which works properly as a Telnet/FTP
server, yank the problem system, and
reconfigure/substitute the known-working
system for the problem system. (So, same IP
address, same network cable, ...) If the
problem remains, then I'd show the evidence
to the network people. If it disappears,
then I'd throw up my hands, because I haven't
thought of another good reason for the
problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2011 04:48 PM
тАО01-19-2011 04:48 PM
Re: telnet not accessible?
>>Find new network people?
Yea, that's kind of where I ended up too. I just wanted to reconfirm that there's nothing else in the OS that could be blocking this.
Thanks; appreciate the replies.
Doug
------
Senior UNIX Admin
O'Leary Computers Inc
linkedin: http://www.linkedin.com/dkoleary
Resume: http://www.olearycomputers.com/resume.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2011 08:31 PM
тАО01-19-2011 08:31 PM
Re: telnet not accessible?
> there's nothing else in the OS that could
> be blocking this.
My inability to think of it is not exactly a
proof of nonexistence, but, on the bright
side, at least I'm not suggesting that you
check to see if the server's listening after
you said that you were "able to telnet to
localhost on the box."
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2011 10:42 PM
тАО01-19-2011 10:42 PM
Re: telnet not accessible?
I would like to ask one question, since you are not able to telnet/ftp to your server... Are you able to do an rlogin or remsh?? If that is also not happening then something sounds fishy with the inetd superdaemon. Your /etc/hosts has a loopback address entry?? I know that sounds like a strange question but upper layer protocols do not function properly without the presence of loopback address in the /etc/hosts file. Just a small tip documented in a lotta places. Sometimes getting out of the troublshooting loop involves checking really simple stuff, like is the inetd control variable set as 1 on your /etc/rc.config.d/netdaemons?
Regards
Ismail Azad
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-20-2011 05:45 AM
тАО01-20-2011 05:45 AM
Re: telnet not accessible?
Hey;
All the insecure protocols work on the box itself. For instance, I can ssh to the system, then run "telnet 0" and get an immediate response from the indetd/telnetd.
loopback is in the /etc/hosts file too. Confirmed that just now.
I just kicked the service call back to the network people. I love these ping-pong trouble tickets
Thanks again for the replies.
Doug O'Leary
------
Senior UNIX Admin
O'Leary Computers Inc
linkedin: http://www.linkedin.com/dkoleary
Resume: http://www.olearycomputers.com/resume.html