03-17-2005
Hello,
I would first like to thank you for the quick response. I guess I haven't projected the exact problem. I was using it in the same way as you said.
c:> telnet x.x.x.x 23
Thing is...I need to check the connectivity to different hosts, and all of them require authorization.We were checking them in the same way - first connect to the host,then supply the username & password. And then check for the remaining hosts similarly.It takes atleast 1-2 mins to test each host.We have to check different host with different login credentials. Also, this is a repetitive process which has to be done from time to time. So, this is consuming a lot of time.Is there any alternative to reduce this time taken?
I am looking for, if it is possible to write a batch file for it, but upto now I couldnot makeout any thing.
Also I have very little knowledge of Unix.
Thanks
KK
10 More Discussions You Might Find Interesting
1. IP Networking
I am trying to network an SGI running Irix 6.5 through an ethernet line to a PC running Windows 2000 (I have connected other PC's to this PC without any problems.) The PC has a DSL connection from Verizon that does not support Unix. I tried using DHCP on the SGI, but when I open a web browser on... (2 Replies)
Discussion started by: mdbanas
2 Replies
2. UNIX for Dummies Questions & Answers
I connected my windows 2k professional to sco openserver. i want to know how i should setup sco , so when i login from windows it will log me into my home dir on sco (1 Reply)
Discussion started by: scoman
1 Replies
3. UNIX for Advanced & Expert Users
how to connect to windows from unix??? (7 Replies)
Discussion started by: hemant30
7 Replies
4. Windows & DOS: Issues & Discussions
Is there a way to connect to Windows from UNIX. From Windows to UNIX, there is a putty that can be used. Is putty also possible to use to connect? (2 Replies)
Discussion started by: punyenye
2 Replies
5. UNIX for Advanced & Expert Users
Hi
Can someone giv me some knowledge on accesing windows from unix and executing DOS scripts using SSH
I would like to know how to go abt it...am new to it.
Thanks in advance (1 Reply)
Discussion started by: lakshmis10
1 Replies
6. Solaris
Ok i have a bad slice on my solaris 10 hard drive. And that so happens to be where the data is that i need. there are 10 corrupt block that are not allowing it to mount. I tried everything fro ufsdump to fsck -Y -o f and nothing works.
so i took the drive out and plugged it into a external USB ->... (4 Replies)
Discussion started by: deaconf19
4 Replies
7. Shell Programming and Scripting
Hi,
One of the folders in UNIX is mapped with a drive on Windows.From this UNIX machine I want to connect to the Windows Server, perform some checks and view the results back on the UNIX machine.
For e.g. if I touch a file under the shared folder on UNIX, I should be able to telnet to Windows... (2 Replies)
Discussion started by: swasid
2 Replies
8. Windows & DOS: Issues & Discussions
Hi
Is there any command which we can try connecting unix from windows without using any third party tool.
Thanks in advance
KVB (9 Replies)
Discussion started by: bikky6
9 Replies
9. Virtualization and Cloud Computing
Hi ,
I have installed Centos 6.5 in my VMWare on windows 7 , My Internet is running fine on both VMWare OS and windows 7 .
When I am trying to connect from putty on my window to Vimware Linux but it does not connect.
Please help what should I do to connect the window system to Linux System (6 Replies)
Discussion started by: kaushik02018
6 Replies
10. Shell Programming and Scripting
I am trying to connect to a Windows server say 10.1.1.10. This servers has a folder named RAJ in which there are multiple .zip files. All these zip files contain a text file called XYZ.txt. Now i have to merge the content of these XYZ.txt files from each of the .zip file and create a new text... (1 Reply)
Discussion started by: swapniljadav
1 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