Sponsored Content
Special Forums IP Networking can ping but can not telnet UNIX Post 97091 by RTM on Thursday 26th of January 2006 08:46:13 AM
Old 01-26-2006
What is the OS and version of the UNIX box? That helps in giving correct information of how to turn on telnet (although it's not recommended - using telnet may be a security risk - ssh would be a better choice).

In general, you need to find the file where services are set up to start - (on Solaris it would be /etc/inetd.conf) - make sure the telnet line is not commented out with #.
 

10 More Discussions You Might Find Interesting

1. IP Networking

ping and telnet

I can ping other computers in my office. I can telnet other users in my office but i cannot get out of the office network. If i try to go out side of my network it cannot find host. Any ideas? (5 Replies)
Discussion started by: macdonto
5 Replies

2. SCO

Openserver 5.0.4 can't be ping or telnet into from a remote site

Hi, Can anybody help me out why l can't not ping my server with Openserver 5.0.4 with my windows machine from a remote site. The machine could see the local LAN with the Router however, i can't ping or telnet unto the server from another site on the WAN. The default gateway was configure on the... (0 Replies)
Discussion started by: kayode
0 Replies

3. 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

4. Infrastructure Monitoring

no telnet, ping ok...

We have a Sun Solaris Netra 20 server. Our O&M Server gets Alarm Processor not responding. When Alarm occurs, you can ping the sun server but cannot telnet it. We keep getting Interrupt level not serviced. var/adm/message log is > tail -f messages Apr 12 20:09:56 cama pcisch: PCI-device:... (9 Replies)
Discussion started by: krabu
9 Replies

5. UNIX for Dummies Questions & Answers

Only execute telnet and ping for user

Hello for all! This is the situation: I must create many users that only can execute telnet and ping. Create users is not a problem, but I donīt know how limit the users privileges, to only execute telnet and ping. I hope you can help me. Thank's for all. Bye :) PD: Sorry for my... (4 Replies)
Discussion started by: bobbasystem
4 Replies

6. UNIX for Advanced & Expert Users

ping and telnet - HP-UX

Hi all, I am not sure if my problem is specific to HP-UX or not. Hopefully someone can tell me what's wrong. I have a server name server1 10.100.50.10 in the /etc/hosts file and if I do a ping server1, it shows the right IP address. However, if I run telnet server1, it is not using... (4 Replies)
Discussion started by: newbie_01
4 Replies

7. AIX

ping OK - telnet refused

Hi, After a crash of our older AIX server it happend as it is in the title: ping is ok, but telnet: What it can be this strange thing? Franci (2 Replies)
Discussion started by: frajer
2 Replies

8. UNIX for Dummies Questions & Answers

ping,telnet, traceroute

can you provide the command in solaris8 if I wanted to ping,telnet, traceroute an IP address with a port? thanks (1 Reply)
Discussion started by: lhareigh890
1 Replies

9. Shell Programming and Scripting

ping and telnet timeout

Hello, I need help, I have the following which save in the result file ping and telnet:port test. Basically the script works but I should implement a check on ping and telnet command so that ping has 5 seconds threshold and telnet (more important) 10 seconds. Over that threshold ping and... (0 Replies)
Discussion started by: marmellata
0 Replies

10. BSD

Ping remote sever, nc, telnet, whatever

I put this thread to shell and bsd, because I want to resolve this matter on bsd. May somebody can explain to me how to ping a remote server, in unix. BTW the following code examples were tried on a linux system as well, with the same output, nothing. But on my bsd are not installed nmap neither... (4 Replies)
Discussion started by: 1in10
4 Replies
fping(8)						      System Manager's Manual							  fping(8)

NAME
fping - send ICMP ECHO_REQUEST packets to network hosts SYNOPSIS
fping [ options ] [ systems... ] DESCRIPTION
fping is a program like ping(8) which uses the Internet Control Message Protocol (ICMP) echo request to determine if a target host is responding. fping differs from ping in that you can specify any number of targets on the command line, or specify a file containing the lists of targets to ping. Instead of sending to one target until it times out or replies, fping will send out a ping packet and move on to the next target in a round-robin fashion. In the default mode, if a target replies, it is noted and removed from the list of targets to check; if a target does not respond within a certain time limit and/or retry limit it is designated as unreachable. fping also supports sending a specified number of pings to a tar- get, or looping indefinitely (as in ping ). Unlike ping, fping is meant to be used in scripts, so its output is designed to be easy to parse. OPTIONS
-a Show systems that are alive. -A Display targets by address rather than DNS name. -bn Number of bytes of ping data to send. The minimum size (normally 12) allows room for the data that fping needs to do its work (sequence number, timestamp). The reported received data size includes the IP header (normally 20 bytes) and ICMP header (8 bytes), so the minimum total size is 40 bytes. Default is 56, as in ping. Maximum is the theoretical maximum IP datagram size(64K), though most systems limit this to a smaller, system-dependent number. -Bn In the default mode, fping sends several requests to a target before giving up, waiting longer for a reply on each successive request. This parameter is the value by which the wait time is multiplied on each successive request; it must be entered as a floating-point number (x.y). The default is 1.5. -c Number of request packets to send to each target. In this mode, a line is displayed for each received response (this can suppressed with -q or -Q). Also, statistics about responses for each target are displayed when all requests have been sent (or when inter- rupted). -C Similar to -c, but the per-target statistics are displayed in a format designed for automated response-time statistics gathering. For example: % fping -C 5 -q somehost somehost : 91.7 37.0 29.2 - 36.8 shows the response time in milliseconds for each of the five requests, with the "-" indicating that no response was received to the fourth request. -d Use DNS to lookup address of return ping packet. This allows you to give fping a list of IP addresses as input and print hostnames in the output. -e Show elapsed (round-trip) time of packets. -f Read list of targets from a file. This option can only be used by the root user. Regular users should pipe in the file via stdin: % fping < targets_file -g Generate a target list from a supplied IP netmask, or a starting and ending IP. Specify the netmask or start/end in the targets por- tion of the command line. If a network with netmask is given, the network and broadcast addresses will be excluded. ex. To ping the network 192.168.1.0/24, the specified command line could look like either: fping -g 192.168.1.0/24 or fping -g 192.168.1.1 192.168.1.254 -h Print usage message. -in The minimum amount of time (in milliseconds) between sending a ping packet to any target (default is 25). -l Loop sending packets to each target indefinitely. Can be interrupted with Ctrl-C; statistics about responses for each target are then displayed. -m Send pings to each of a target host's multiple interfaces. -n Same as -d. -p In looping or counting modes (-l, -c, or -C), this parameter sets the time in milliseconds that fping waits between successive packets to an individual target. Default is 1000. -q Quiet. Don't show per-target results, just set final exit status. -Qn Like -q, but show summary results every n seconds. -rn Retry limit (default 3). This is the number of times an attempt at pinging a target will be made, not including the first try. -s Print cumulative statistics upon exit. -Saddr Set source address. -Iif Set the interface (requires SO_BINDTODEVICE support) -tn Initial target timeout in milliseconds (default 500). In the default mode, this is the amount of time that fping waits for a response to its first request. Successive timeouts are multiplied by the backoff factor. -Tn Ignored (for compatibility with fping 2.4). -u Show targets that are unreachable. -Tn Set the typ of service flag (TOS). n can be either decimal or hexadecimal(0xh) format. -v Print fping version information. -Hn Set the IP TTL field (time to live hops). EXAMPLES
The following perl script will check a list of hosts and send mail if any are unreachable. It uses the open2 function which allows a pro- gram to be opened for reading and writing. fping does not start pinging the list of systems until it reads EOF, which it gets after INPUT is closed. Sure the open2 usage is not needed in this example, but it's a good open2 example none the less. #!/usr/bin/perl require 'open2.pl'; $MAILTO = "root"; $pid = &open2("OUTPUT","INPUT","/usr/local/bin/fping -u"); @check=("slapshot","foo","foobar"); foreach(@check) { print INPUT "$_ "; } close(INPUT); @output=<OUTPUT>; if ($#output != -1) { chop($date=`date`); open(MAIL,"|mail -s 'unreachable systems' $MAILTO"); print MAIL " The following systems are unreachable as of: $date "; print MAIL @output; close MAIL; } Another good example is when you want to perform an action only on hosts that are currently reachable. #!/usr/bin/perl $hosts_to_backup = `cat /etc/hosts.backup | fping -a`; foreach $host (split(/ /,$hosts_to_backup)) { # do it } AUTHORS
Roland J. Schemers III, Stanford University, concept and versions 1.x RL "Bob" Morgan, Stanford University, versions 2.x David Papp, versions 2.3x and up, David Schweikert, versions 3.0 and up fping website: http://www.fping.org DIAGNOSTICS
Exit status is 0 if all the hosts are reachable, 1 if some hosts were unreachable, 2 if any IP addresses were not found, 3 for invalid com- mand line arguments, and 4 for a system call failure. BUGS
Ha! If we knew of any we would have fixed them! RESTRICTIONS
If certain options are used (i.e, a low value for -i and -t, and a high value for -r) it is possible to flood the network. This program must be installed as setuid root in order to open up a raw socket, or must be run by root. In order to stop mere mortals from hosing the network (when fping is installed setuid root) , normal users can't specify the following: -i n where n < 10 msec -r n where n > 20 -t n where n < 250 msec SEE ALSO
netstat(1), ping(8), ifconfig(8c) fping(8)
All times are GMT -4. The time now is 10:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy