Sponsored Content
Operating Systems AIX Ping is happening, telnet is not happening Post 61354 by zazzybob on Wednesday 2nd of February 2005 03:46:24 PM
Old 02-02-2005
Why is telnet "not happening"? Do you receive an error message? Do you receive any messages at all? Please provide more information about the particular problems being encountered.

From the small amount of information you've provided it could well be that the telnet daemon isn't running on the target server. Have a look at /etc/inetd.conf on the server (if you have access) and see if the telnetd line is commented out. If it is, there are many good reasons for this - telnet is inherently insecure. Consider using SSH instead (sshd may already be set up on the target box - try ssh'ing into the host instead).

Cheers
ZB
 

8 More Discussions You Might Find Interesting

1. AIX

Ping/Telnet is not happening

Hi All, We are not able to ping to a AIX box...Network is ok..when we give ping from that AIX box..it is giving 0821-067 ping: The socket creation call failed.there is no enough buffer space for the requested socket operation. refresh -s inetd is also giving socket error. Please help to... (1 Reply)
Discussion started by: b_manu78
1 Replies

2. UNIX for Dummies Questions & Answers

what's happening with my keyboard

hi everybody. i ussually use unix and windows, but mainly unix-mandriva distribution, and i have a problem. i have like main os unix, and windows as secondary, and this one is loaded by vmware application. well, when a i load vmware to execute windows afterwards when i return to unix, in this... (1 Reply)
Discussion started by: tonet
1 Replies

3. Shell Programming and Scripting

Incrementing a variable is not happening

Hi All, Iam trying to increment a variable Following is the code #!/usr/bin/ksh i=1; i='expr $i+1'; echo $i; Output: expr $i+1 not able to understand why its happening in that way i was expecting result as 2... if the above method is worng .. can you help how i can get... (3 Replies)
Discussion started by: kiranlalka
3 Replies

4. Red Hat

PXE Kickstart not happening

We have a lab where installation is done through PXE . The installation always run fine usually but suddenly we are getting the below mentioned error any idea whats happening ? ==quote== | Erros parsing Kickstart Config | The following error was found while parsing your kickstart... (0 Replies)
Discussion started by: thevishy
0 Replies

5. Programming

[SQL] Why Update is happening twice?

Example 1=> I have unix ksh file and I am calling sql file from it. (table 1 contains 2 rows - ID Name 1 test't 2 Pet's ) below sql statement is part of sql file: update table1 set name = replace(name,'''','''''') where instr(name,'''') > 0 ; --I see below... (3 Replies)
Discussion started by: rshivarkar
3 Replies

6. Fedora

Leap second happening

Have anybody heard about the Leap second problem Leap second :A leap second is a one-second adjustment that is occasionally applied to Coordinated Universal Time (UTC) in order to keep its time of day close to the mean solar time. How could i avoid such thing in my script which i deal with... (6 Replies)
Discussion started by: wnaguib
6 Replies

7. AIX

Telnet is not happening on port number 8080

Dear Experts, I am trying to open 8080 port on my Aix 7.1 server. I made an entry in /etc/services for the port. and refreshed the inetd service. But when I try to telnet localhost 8080, telnet is not happening. connection refused error is coming. I can able to telnet localhost 23 its working... (9 Replies)
Discussion started by: aix.rockie
9 Replies

8. Shell Programming and Scripting

Function call is not happening

set -x QM=$1 port=$2 KILLQ () { ps -efww | grep $QM | grep -v grep | tr -s " " " " | cut -d" " -f2 |xargs kill -9 sleep 3 echo "Checking the Queue" CHKQ } CRTQ () { strmqm $QM runmqlsr -m $QM -t TCP -p $port & } CHKQ () (6 Replies)
Discussion started by: nikhil jain
6 Replies
External(3pm)						User Contributed Perl Documentation					     External(3pm)

NAME
Net::Ping::External - Cross-platform interface to ICMP "ping" utilities SYNOPSIS
In general: use Net::Ping::External qw(ping); ping(%options); Some examples: use Net::Ping::External qw(ping); # Ping a single host my $alive = ping(host => "127.0.0.1"); print "127.0.0.1 is online" if $alive; # Or a list of hosts my @hosts = qw(127.0.0.1 127.0.0.2 127.0.0.3 127.0.0.4); my $num_alive = 0; foreach (@hosts) { $alive = ping(hostname => $_, timeout => 5); print "$_ is alive! " if $alive; $num_alive++; } print "$num_alive hosts are alive. "; # Using all the fancy options: ping(hostname => "127.0.0.1", count => 5, size => 1024, timeout => 3); DESCRIPTION
Net::Ping::External is a module which interfaces with the "ping" command on many systems. It presently provides a single function, "ping()", that takes in a hostname and (optionally) a timeout and returns true if the host is alive, and false otherwise. Unless you have the ability (and willingness) to run your scripts as the superuser on your system, this module will probably provide more accurate results than Net::Ping will. Why? o ICMP ping is the most reliable way to tell whether a remote host is alive. o However, Net::Ping cannot use an ICMP ping unless you are running your script with privileged (AKA "root") access. o The system's "ping" command uses ICMP and does not usually require privileged access. o While it is relatively trivial to write a Perl script that parses the output of the "ping" command on a given system, the aim of this module is to encapsulate this functionality and provide a single interface for it that works on many systems. ping() OPTIONS This module is still "alpha"; it is expected that more options to the "ping()" function will be added soon. o "host, hostname" The hostname (or dotted-quad IP address) of the remote host you are trying to ping. You must specify either the "hostname" option or the "ip" option. "host" and "hostname" are synonymous. o "ip" A packed bit-string representing the 4-byte packed IP address (as returned by "Socket.pm"'s "inet_aton()" function) of the host that you would like to ping. o "timeout" The maximum amount of time, in seconds, that "ping()" will wait for a response. If the remote system does not respond before the timeout has elapsed, "ping()" will return false. Default value: 5. o "count" The number of ICMP ping packets to send to the remote host. Eventually, Net::Ping::External will return the number of packets that were acknowledged by the remote host; for now, however, "ping()" still returns just true or false. Default value: 1. o "size" Specifies the number of data bytes to be sent. The default is 56, which translates into 64 ICMP data bytes when combined with the 8 bytes of ICMP header data. Default value: 56. SUPPORTED PLATFORMS Support currently exists for interfacing with the standard ping utilities on the following systems. Please note that the path to the `ping' should be somewhere in your PATH environment variable (or your system's closest equivalent thereof.) Otherwise, Net::Ping::External will be unable to locate your system's `ping' command. o Win32 Tested OK on Win98, Win XP. It should work on other Windows systems as well. o Cygwin Tested OK on Cygwin 1.5.21. Problem is that we may be running windows ping. They have different options. o Linux Tested OK on Debian 2.2 and Redhat 6.2. It appears that different versions of Linux use different versions of ping, which support different options. Not sure how I'm going to resolve this yet; for now, all the options but "count" are disabled. o BSD Tested OK on OpenBSD 2.7 and 3.0, Netbsd 1.5.3, Freebsd 4.6.2, 5.4. Needs testing for BSDi. o Solaris Tested OK on Solaris 2.6 and 2.7. o IRIX Tested OK on IRIX 6.5. o AIX, DEC OSF, UNICOSMK, NeXTStep, HP-UX, BSD/OS (BSDi), BeOS Support for these systems is integrated into this module but none have been tested yet. If you have successful or unsuccessful test results for any of these systems, please send them to me. On some of these systems, some of the arguments may not be supported. If you'd like to see better support on your system, please e-mail me. More systems will be added as soon as any users request them. If your system is not currently supported, e-mail me; adding support to your system is probably trivial. BUGS
This module should be considered beta. Bugs may exist. Although no specific bugs are known at this time, the module could use testing on a greater variety of systems. See the warning below. WARNING
This module calls whatever "ping" program it first finds in your PATH environment variable. If your PATH contains a trojan "ping" program, this module will call that program. This involves a small amount of risk, but no more than simply typing "ping" at a system prompt. Beware Greeks bearing gifts. AUTHOR
Alexandr Ciornii (alexchorny AT gmail.com), Colin McMillen (colinm AT cpan.org) This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. CREDITS
Dan Moore contributed command-line options and code for NeXT, BeOS, HP-UX, and BSD/OS. Jarkko Hietaniemi contributed a huge list of command-line options and results for the `ping' command on 9 different systems. Randy Moore contributed several patches for Win32 support. Marc-Andre Dumas contributed a patch for FreeBSD support. Jonathan Stowe fixed a bug in 0.09 that prevented the module from running on some systems. Numerous people sent in a patch to fix a bug in 0.10 that broke ping on Windows systems. Peter N. Lewis contributed a patch that works correctly on Mac OS X 10.2 (and hopefully other versions as well). SEE ALSO
Net::Ping perl v5.10.1 2008-12-18 External(3pm)
All times are GMT -4. The time now is 06:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy