12-03-2003
UNIX, remote access problem
Hi,
I am new to UNIX and I am given the responsibility of administering a UNIX machine recently. The system is a AIX 3.1 IBM. And, I am having problems in accessing the UNIX machine thru SSH.
All the users were able to logon to the Unix machine using SSH protocol earlier. But, I dont know what happened, one day it started giving the following error message when any user tried to login. " The host
is unreachable. The host may be down, or there may be a problem with the network connection. Sometimes, such problems may be caused by a misconfigured firewall." But this doesnt happen when I login thru putty/rlogin.
Can any one help me in identifying the problem and fixing . Any suggestions would be appreciated. Please be detail in your replies as I am new and dont understand UNIX terminology.
Thanx
pdepa.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi
I need to access files from a specific folder of a Linux system from an another Linux System Remotely.
I know how to, Export a folder on One SCO System & can access the same by using Import via., NFS in the Sco Unix SVR4 System using the scoadmin utility.
Also, I know to use mount -t ... (2 Replies)
Discussion started by: S.Vishwanath
2 Replies
2. UNIX for Advanced & Expert Users
I have set up a modem in SCO Unix .. I want to dial in from a remote terminal program, what else is needed .. do I have to configure UUCP ?? How ? Any other configurations ?
CHRIS (1 Reply)
Discussion started by: germiphene
1 Replies
3. Solaris
Hi
We access all our SPARC/x86 servers (Solaris 8,9 & 10) using ssh. I am looking for a open source tool that allows me to get the GUI on to my laptop. I tried with x-org and some other applications like Hummingbird. Encountered problems with license issues and CPU compatability of my laptop.
... (2 Replies)
Discussion started by: chrs0302
2 Replies
4. Shell Programming and Scripting
hey guys, i am on a box named pluto and i need to be able to log into another box named genesis. i need to be able to ssh into genesis as root and not get asked for the password. what file do i need to edit on genesis to make this happen? i searched for the .rhosts file it doesn't seem to exist.... (1 Reply)
Discussion started by: Terrible
1 Replies
5. Filesystems, Disks and Memory
Hello Moto
I hope someone can help
We's here at work, have a unix box with sco openserver 5 on it, so it has a nice gui interface.. and also a fair few windows computers..
a system admin guy b4 me, has set up a user called neil, which can, when u try to access the unix box using windows... (2 Replies)
Discussion started by: haggo
2 Replies
6. Shell Programming and Scripting
I have Tomcat installed on a Unix box and I need to start it remotely from another Unix box.
Tomcat is started using a script. When this script is run locally everything is fine. When I run the same script from remote box, tomcat starts but the command running the script does not terminate.:(
... (2 Replies)
Discussion started by: shrgh
2 Replies
7. Shell Programming and Scripting
How can we create new directory/Or execute command on remote unix machine from another unix machine.
We can use SSH command to execute command on remote machine but problem is that ssh will prompt for password before executing command.
My requirment is to execute command without manual... (1 Reply)
Discussion started by: pasricha.kunal
1 Replies
8. Homework & Coursework Questions
Dear Friends,
This is not a problem , it's a course work (UNIX scenario)....
As part of it I am searching Remote Attacks and find points as
1. Exploiting a listening service
2. Routing through Unix system that is providing security between 2 or more networks
3. User initiated Remote execution... (1 Reply)
Discussion started by: anespa
1 Replies
9. Shell Programming and Scripting
Hi All
I need to transfer a file from a UNIX server to a windows server.
I saw that it is possible to do this using scp command by looking at the forum listed below:
... (2 Replies)
Discussion started by: vx04
2 Replies
LEARN ABOUT NETBSD
rhosts
HOSTS.EQUIV(5) BSD File Formats Manual HOSTS.EQUIV(5)
NAME
hosts.equiv, .rhosts -- trusted remote hosts and host-user pairs
DESCRIPTION
The hosts.equiv and .rhosts files list hosts and users which are ``trusted'' by the local host when a connection is made via rlogind(8),
rshd(8), or any other server that uses ruserok(3). This mechanism bypasses password checks, and is required for access via rsh(1).
Each line of these files has the format:
hostname [username]
The hostname may be specified as a host name (typically a fully qualified host name in a DNS environment) or address, ``+@netgroup'' (from
which only the host names are checked), or a ``+'' wildcard (allow all hosts).
The username, if specified, may be given as a user name on the remote host, ``+@netgroup'' (from which only the user names are checked), or a
``+'' wildcard (allow all remote users).
If a username is specified, only that user from the specified host may login to the local machine. If a username is not specified, any user
may login with the same user name.
EXAMPLES
somehost
A common usage: users on somehost may login to the local host as the same user name.
somehost username
The user username on somehost may login to the local host. If specified in /etc/hosts.equiv, the user may login with only the same
user name.
+@anetgroup username
The user username may login to the local host from any machine listed in the netgroup anetgroup.
+
+ +
Two severe security hazards. In the first case, allows a user on any machine to login to the local host as the same user name. In the
second case, allows any user on any machine to login to the local host (as any user, if in /etc/hosts.equiv).
WARNINGS
The username checks provided by this mechanism are not secure, as the remote user name is received by the server unchecked for validity.
Therefore this mechanism should only be used in an environment where all hosts are completely trusted.
A numeric host address instead of a host name can help security considerations somewhat; the address is then used directly by iruserok(3).
When a username (or netgroup, or +) is specified in /etc/hosts.equiv, that user (or group of users, or all users, respectively) may login to
the local host as any local user. Usernames in /etc/hosts.equiv should therefore be used with extreme caution, or not at all.
A .rhosts file must be owned by the user whose home directory it resides in, and must be writable only by that user.
Logins as root only check root's .rhosts file; the /etc/hosts.equiv file is not checked for security. Access permitted through root's
.rhosts file is typically only for rsh(1), as root must still login on the console for an interactive login such as rlogin(1).
FILES
/etc/hosts.equiv Global trusted host-user pairs list
~/.rhosts Per-user trusted host-user pairs list
SEE ALSO
rcp(1), rlogin(1), rsh(1), rcmd(3), ruserok(3), netgroup(5)
HISTORY
The .rhosts file format appeared in 4.2BSD.
BUGS
The ruserok(3) implementation currently skips negative entries (preceded with a ``-'' sign) and does not treat them as ``short-circuit'' neg-
ative entries.
BSD
November 26, 1997 BSD