- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- telnet issue
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
тАО11-06-2007 09:46 PM
тАО11-06-2007 09:46 PM
telnet issue
Nodename as registered in kernel is mmp3.sems.com
Have two interfaces configured as follows:
Tu0: 128.6.5.10 netmask : 255.255.0.0 hostname: mmp3.sems.com
Tu3: 128.6.5.33 netmask : 255.255.0.0 hostname : mmp33.sems.com
When configured as above, we can ping to the IP addresses.
When telnet to the hostname, it gives an error тАУ unable to open port on interface or similar.
What is wrong with the configuration ?
Interface ip hostname
Tu0 128.6.5.10 mmp3.sems.com
Tu1 100.100.100.10 mhdb2
Tu2 100.100.100.11 mhdb3
Tu3 128.6.5.11 mmp33.sems.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-06-2007 09:49 PM
тАО11-06-2007 09:49 PM
Re: telnet issue
Yours
Danny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-06-2007 09:57 PM
тАО11-06-2007 09:57 PM
Re: telnet issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-06-2007 11:26 PM
тАО11-06-2007 11:26 PM
Re: telnet issue
If you grep for telnet in /etc/inetd.conf, what does the line enableing telnetd look like?
Yours
Danny
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2007 12:39 AM
тАО11-07-2007 12:39 AM
Re: telnet issue
How do I know what the latest one is? More
important, how do I know that _you_ know what
the latest one is?
> When telnet to the hostname
From where? To which address does the host
name resolve wherever you're Telnetting from?
> [...] it gives an error [...] or similar.
Who is "it"? What's the actual error
message? A transcript showing what you did
and what happened when you did it might be
much more helpful than a vague description.
> [...]
> Tu3: 128.6.5.33
> [...]
> Tu3 128.6.5.11 mmp33.sems.com
Eh?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-09-2007 02:08 AM
тАО11-09-2007 02:08 AM
Re: telnet issue
Having two network interfaces on the same subnet is likely to cause you problems...
Check whether telnetd is listening, by looking at the output of "netstat -a"
You might also want to review your routing configuration... "netstat -rn"
Cheers,
Rob