05-05-2008
Unable to telnet to server
Hi,
I encountered error when I telnet to my server.
Error is as follows:
telnetd: /bin/login: The file access permissions do not allow the specified action
I am able to ssh into my server and I have checked/verified /etc/security and /etc/inetd.conf. I restarted the inetd subsystem via smit.
Thanks and best regards
Solomon
10 More Discussions You Might Find Interesting
1. IP Networking
I tried to telnet to my Sun server (E250) but I received the error message :
"Network error: Connection reset by peer".
I was able to ping my server. And, I had already commented off "CONSOLE=/dev/console" in /etc/default/login.
But, if I rlogin from all other servers, it works.
Is there... (2 Replies)
Discussion started by: dawn_lwf
2 Replies
2. UNIX for Dummies Questions & Answers
:cool: I need some assistance please. I'm setting up a SunOS 5.6 server and sofar I'm able to telnet into the unit but unable to telnet from it. Can anyone help me with this problem. When attempting to telnet from my SunOs to client
terminal I'm receving the following error, "Unable to connect to... (3 Replies)
Discussion started by: sharris82
3 Replies
3. HP-UX
Hi friend,
I'm facing a problem to access the console and telnet to the HP ux 11 server due to the system file is full. How to access this server via single mode and how to mount the folder / and folder /var?
thanks.
vestro (1 Reply)
Discussion started by: vestro
1 Replies
4. UNIX for Dummies Questions & Answers
Hi everybody
i am trying to telnet to sun server from win xp machine but getting message "x21 error connection closed by remote user". i had make changes in /etc/default/login & /etc/fuser file still i have not getting telnet access. my win xp machines ip is 10.205.121.177 & sun server ip is... (1 Reply)
Discussion started by: pshelke
1 Replies
5. Solaris
Hi guys,
After changing my workstation from domain rsm.renesas.com to my.renesas.local, I was unable to telnet to 1 of our Sun Solaris servers.
There r errors in the messages file:
Aug 15 17:35:26 rsmsso1.svc.rsm.renesas.com inetd: warning: can't verify hostname:... (12 Replies)
Discussion started by: *Jess*
12 Replies
6. UNIX for Dummies Questions & Answers
Dear All,
I have Compaq Alpha server running UNIX OS. with Old Hardware specification.
I had FTP conncetion using IP Switch ( FTP client ) to the Unix server in order to copy some files to my workstation. one day after closing the connection we noted that IT operations are not able to... (8 Replies)
Discussion started by: Arehan
8 Replies
7. SuSE
Hi forum,
I face a strange issue. I'm able to telnet as root with ssh.
But I'm not able to telnet (non-ssh) as root to my Suse 10 machine.
Can someone please point to significant files where I need to make changes for Suse 10 machine and resolve this issue.
Thanks in advance. (2 Replies)
Discussion started by: anilgurwara
2 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I have two linux boxes and due to some reasons I have reinstalled OS in one of them. Now Iam unable to telnet one of them. I have included entries in /etc/hosts in both and Iam able to ping each other.
Am I missing anything here or I we need to install/activate telnet server ?
Thanks... (2 Replies)
Discussion started by: ssuhaib
2 Replies
9. Solaris
I have encounter this solaris problem and it happens intermittent. When it happens, the system is freezing and unable to telnet/ssh in but the system ip is still able to ping. after that it will back to the normal and everything seems like be normal again. it is sun cluster setup.
scsi: ... (5 Replies)
Discussion started by: freshmeat
5 Replies
10. Shell Programming and Scripting
i have to connect windows server from one of the unix box so i am using telnet and below is my following code
#!/bin/sh
host=hostname
log=loginid
port=23
pass=password
cmd1=mkdir test1234
( echo open ${host} ${port}
sleep 1
echo ${log}
sleep 3
echo "\r\n"
sleep 3
echo ${pass}... (11 Replies)
Discussion started by: chandan.p
11 Replies
LEARN ABOUT FREEBSD
tcpdmatch
TCPDMATCH(8) System Manager's Manual TCPDMATCH(8)
NAME
tcpdmatch - tcp wrapper oracle
SYNOPSYS
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 or tlid 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 or tlid.conf network configuration file, or when you suspect
that the program 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.
tlid.conf(5), format of the tlid 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)