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
Smokeping_probes_OpenSSHJunOSPing(3)				     SmokePing				      Smokeping_probes_OpenSSHJunOSPing(3)

NAME
Smokeping::probes::OpenSSHJunOSPing - Juniper SSH JunOS Probe for SmokePing SYNOPSIS
*** Probes *** +OpenSSHJunOSPing forks = 5 offset = 50% packetsize = 100 step = 300 timeout = 15 # The following variables can be overridden in each target section junospass = password # mandatory junosuser = user # mandatory pings = 5 psource = 192.168.2.129 source = 192.168.2.1 # mandatory # [...] *** Targets *** probe = OpenSSHJunOSPing # if this should be the default probe # [...] + mytarget # probe = OpenSSHJunOSPing # if the default probe is something else host = my.host junospass = password # mandatory junosuser = user # mandatory pings = 5 psource = 192.168.2.129 source = 192.168.2.1 # mandatory DESCRIPTION
Connect to Juniper JunOS via OpenSSH to run ping commands. This probe uses the "extended ping" of the Juniper JunOS. You have the option to specify which interface the ping is sourced from as well. VARIABLES
Supported probe-specific variables: forks Run this many concurrent processes at maximum Example value: 5 Default value: 5 offset If you run many probes concurrently you may want to prevent them from hitting your network all at the same time. Using the probe- specific offset parameter you can change the point in time when each probe will be run. Offset is specified in % of total interval, or alternatively as 'random', and the offset from the 'General' section is used if nothing is specified here. Note that this does NOT influence the rrds itself, it is just a matter of when data acqusition is initiated. (This variable is only applicable if the variable 'concurrentprobes' is set in the 'General' section.) Example value: 50% packetsize The (optional) packetsize option lets you configure the packetsize for the pings sent. Default value: 100 step Duration of the base interval that this probe should use, if different from the one specified in the 'Database' section. Note that the step in the RRD files is fixed when they are originally generated, and if you change the step parameter afterwards, you'll have to delete the old RRD files or somehow convert them. (This variable is only applicable if the variable 'concurrentprobes' is set in the 'General' section.) Example value: 300 timeout How long a single 'ping' takes at maximum Example value: 15 Default value: 5 Supported target-specific variables: junospass The junospass option allows you to specify the password for the username specified with the option junosuser. Example value: password This setting is mandatory. junosuser The junosuser option allows you to specify a username that has ping capability on the JunOS Device. Example value: user This setting is mandatory. pings How many pings should be sent to each target, if different from the global value specified in the Database section. Note that the number of pings in the RRD files is fixed when they are originally generated, and if you change this parameter afterwards, you'll have to delete the old RRD files or somehow convert them. Example value: 5 psource The (optional) psource option specifies an alternate IP address or Interface from which you wish to source your pings from. Routers can have many many IP addresses, and interfaces. When you ping from a router you have the ability to choose which interface and/or which IP address the ping is sourced from. Specifying an IP/interface does not necessarily specify the interface from which the ping will leave, but will specify which address the packet(s) appear to come from. If this option is left out the JunOS Device will source the packet automatically based on routing and/or metrics. If this doesn't make sense to you then just leave it out. Example value: 192.168.2.129 source The source option specifies the JunOS device that is going to run the ping commands. This address will be used for the ssh connection. Example value: 192.168.2.1 This setting is mandatory. AUTHORS
Tobias Oetiker lttobi@oetiker.chgt based on Smokeping::probes::TelnetJunOSPing by S H A N ltshanali@yahoo.comgt. NOTES
JunOS configuration The JunOS device should have a username/password configured, as well as the ability to connect to the VTY(s). Make sure to connect to the remote host once from the commmand line as the user who is running smokeping. On the first connect ssh will ask to add the new host to its known_hosts file. This will not happen automatically so the script will fail to login until the ssh key of your juniper box is in the known_hosts file. Some JunOS devices have a maximum of 5 VTYs available, so be careful not to hit a limit with the 'forks' variable. Requirements This module requires the Net::OpenSSH and IO::Pty. 2.6.8 2013-03-17 Smokeping_probes_OpenSSHJunOSPing(3)
All times are GMT -4. The time now is 09:13 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy