- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Telnet connection problem
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
тАО09-22-2010 09:42 AM
тАО09-22-2010 09:42 AM
Telnet connection problem
I have check the line witch refer telnet in /etc/services et /etc/inetd.conf, in both files this lines are uncomment.
When I do netstat -a | grep *.telnet I got the following messages:Reading from a core file is no longer supported.
I don't know what core the system refers about.
Are someone that have any idea
Thx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-22-2010 10:32 AM
тАО09-22-2010 10:32 AM
Re: Telnet connection problem
system would be nice to have.
uname -a
Also as usual, showing actual commands with
their actual output (copy+paste) might be
more helpful than vague descriptions and
interpretations.
> [...] netstat -a | grep *.telnet [...]
If you're using a normal UNIX shell, then
you should expect it to expand a wildcard
like "*.telnet". You might get better
results from:
netstat -a | grep telnet
or:
netstat -a | grep '*.telnet'
> I try to configure telnet in vain.
Does Telnet not work? Did you try it? How?
What happened when you did?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-22-2010 04:38 PM
тАО09-22-2010 04:38 PM
Re: Telnet connection problem
Did you HUP the inetd daemon?
Try this:
ps -ef |grep inetd
Make a note of the process id of the inetd daemon running on your system.
The run this command:
kill -1 PID
Replace PID with the process number that you found in the ps command output.
Make sure you use the -1 (that's the number one and not the letter ell) switch!
The -1 switch will "hang up" the daemon and will cause it to re-read the inetd.conf.
If you forget the -1 in the kill command it will KILL the inetd daemon instead of just "restarting" it.
Hope this helps.
kev
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-22-2010 05:23 PM
тАО09-22-2010 05:23 PM
Re: Telnet connection problem
> [...]
man inetd
Look for "-c".
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-22-2010 08:50 PM
тАО09-22-2010 08:50 PM
Re: Telnet connection problem
Reading from a core file is no longer supported.
In this case, "core file" refers to /dev/kmem. On PA-RISC hardware, the netstat command apparently got the information by accessing kernel structures directly through /dev/kmem. On Itanium hardware, the interface is apparently somewhat different.
Is your system currently running a "previous" or "backup" kernel configuration (i.e. booted with "hpux vmunix.prev", "hpux backup/vmunix" or "boot backup/vmunix" on Itanium hardware)? In that case, some commands may behave oddly, unless told to use the correct kernel configuration.
(Those commands need to read some data from kernel configuration files in /stand to correctly interpret the information they get from /dev/kmem or whatever...)
Or has someone deleted/renamed/corrupted your /stand/system file or the /dev/kmem device?
MK