08-01-2001
Yes, you can see that inetd.conf is OK by your post.
The problem could also be that the IP address does not resolve to the host name and your machine is configured to disallow telnet from clients without a proper DNS IP to name entry.
Just a thought....
Also, you might check to see if your telnetd server is running identd and if so, in what configuration.....
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am trying to run a Perl script using rsh. I need to be able to capture the return code value, so the calling script can handle failures properly.
I cannot modify the Perl script I need to run because we use it for all of our servers.
Does anyone have a suggestion? (1 Reply)
Discussion started by: kscase
1 Replies
2. UNIX for Dummies Questions & Answers
hi friends,
i've access to three machines mc1,mc2,mc3,on which i can log in as root.
and in order to run a simple command on a remote machine(say remote) on which i cant log in,i use a command as;
# rsh remote ls
the above runs properly but if i do an ls on following it doesnt work
# rsh mc2... (1 Reply)
Discussion started by: mxms755
1 Replies
3. Solaris
Hi ,
I have a Solaris 9 machine in which I can ftp but telnet/rsh/ssh is not working, although it was working before. I cannot also log in through the console. I get the banner for telnet but it kicks me out.
Any ideas?
rte (2 Replies)
Discussion started by: run_time_error
2 Replies
4. Linux
Hi All,
I want to execute a command from my Windows machine to Linux machine.
d:> rsh <Linux machine add> -l <user_name> pwd>dir
in linux machine users home directory in .rhosts file I entered the windows machine IP address and user name.
In linux etc/hosts.equiv file I entered the... (1 Reply)
Discussion started by: sarwan
1 Replies
5. UNIX for Advanced & Expert Users
Hi All,
I want to execute a command from my Windows machine to Linux machine using RSH only
d:> rsh <Linux machine add> -l <user_name> pwd>dir
in linux machine users home directory in .rhosts file I entered the windows machine IP address and user name.
In linux etc/hosts.equiv file I... (1 Reply)
Discussion started by: sarwan
1 Replies
6. Shell Programming and Scripting
Somewhat long story:
I have a simple Perl CGI script that uses Expect to Telnet to a device and grab some data, and then spits it back to Perl for display on the Webpage.
This works for many devices I've tried, but one device just fails, it keeps rejecting the password on this device, only... (1 Reply)
Discussion started by: jondo
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I was writing one script which includes to switch to the another telnet automatically from the present telnet server. I was using rlogin but firstly it takes the same user name of the present telnet and secondly it is prompting for the password.
But i want to switch to the another telnet... (2 Replies)
Discussion started by: Prateek
2 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I want to know the difference between these two services. Both are under xinetd. Both are used for enabling and disabling Telnet service. So, can somebody please explain me the difference between the two ?
Thanks in advance :) (0 Replies)
Discussion started by: kashifsd17
0 Replies
9. AIX
telnet or rsh or ftp to an AIX machine takes too much time, like have to wait 3 minutes before the prompt appears.
What can I look to troubleshoot this problem
thanks (4 Replies)
Discussion started by: filosophizer
4 Replies
10. AIX
Hello I have a LPAR AIX 6.1 on Power VM, Vio 2.2.3 and when I execute a rcp to this machine, I cant, simultaneosly, rlogin, telnet, rsh to this same LPARt. This commands stay hanged till the copy end, and Imeddiatlely the comand is executed (rlogin, telnet, rhs, etc).
Someone can give me... (1 Reply)
Discussion started by: artur_dietrich
1 Replies
LEARN ABOUT REDHAT
tcpdmatch
TCPDMATCH(8) System Manager's Manual TCPDMATCH(8)
NAME
tcpdmatch - tcp wrapper oracle
SYNOPSIS
tcpdmatch [-d] [-i inet_conf] daemon client
tcpdmatch [-d] [-i inet_conf] daemon[@server] [user@]client
DESCRIPTION
tcpdmatch predicts how the tcp wrapper would handle a specific request for service. Examples are given below.
The program examines the tcpd access control tables (default /etc/hosts.allow and /etc/hosts.deny) and prints its conclusion. For maximal
accuracy, it extracts additional information from your inetd network configuration file.
When tcpdmatch finds a match in the access control tables, it identifies the matched rule. In addition, it displays the optional shell com-
mands or options in a pretty-printed format; this makes it easier for you to spot any discrepancies between what you want and what the pro-
gram understands.
ARGUMENTS
The following two arguments are always required:
daemon A daemon process name. Typically, the last component of a daemon executable pathname.
client A host name or network address, or one of the `unknown' or `paranoid' wildcard patterns.
When a client host name is specified, tcpdmatch gives a prediction for each address listed for that client.
When a client address is specified, tcpdmatch predicts what tcpd would do when client name lookup fails.
Optional information specified with the daemon@server form:
server A host name or network address, or one of the `unknown' or `paranoid' wildcard patterns. The default server name is `unknown'.
Optional information specified with the user@client form:
user A client user identifier. Typically, a login name or a numeric userid. The default user name is `unknown'.
OPTIONS
-d Examine hosts.allow and hosts.deny files in the current directory instead of the default ones.
-i inet_conf
Specify this option when tcpdmatch is unable to find your inetd.conf network configuration file, or when you suspect that the pro-
gram uses the wrong one.
EXAMPLES
To predict how tcpd would handle a telnet request from the local system:
tcpdmatch in.telnetd localhost
The same request, pretending that hostname lookup failed:
tcpdmatch in.telnetd 127.0.0.1
To predict what tcpd would do when the client name does not match the client address:
tcpdmatch in.telnetd paranoid
On some systems, daemon names have no `in.' prefix, or tcpdmatch may need some help to locate the inetd configuration file.
FILES
The default locations of the tcpd access control tables are:
/etc/hosts.allow
/etc/hosts.deny
SEE ALSO
tcpdchk(8), tcpd configuration checker
hosts_access(5), format of the tcpd access control tables.
hosts_options(5), format of the language extensions.
inetd.conf(5), format of the inetd control file.
AUTHORS
Wietse Venema (wietse@wzv.win.tue.nl),
Department of Mathematics and Computing Science,
Eindhoven University of Technology
Den Dolech 2, P.O. Box 513,
5600 MB Eindhoven, The Netherlands
TCPDMATCH(8)