07-26-2001
Follow up
Thank you to all those who replied to my question. Below is a summary of my findings when incorporating RSH. Perhaps this might help others.....
RSH [options] host [command] (sample test command used = rsh myserver -l username df -k)
-The log on "user" must have a valid user account on the Windows machine.
- The log on "user" must have a valid user account on the Unix machine. The user's log on name on both the Unix and Windows machine must be identical.
-On the Unix machine, the etc/hosts.equiv file must contain both the sending machine's fully qualified hostname (DNS) and the "user" name. Use the “man rsh” command in unix for details.
-If the RSH command is used in a batch file invoked by a Windows Service, the Service requires the "Log On As" name to be the same user name listed in the etc/hosts.equiv file.
-The Windows machine must have a registered name in the local DNS.
-While not recommended, if the local Windows machine is not registered in DNS, as might be the case for temporary test servers in development environments, you can override by putting the Windows machine's IP address and fully qualified server name in the Unix machine's etc/inet/hosts file (i.e. 123.45.67.89 myserver.mycompany.com loghost).
8 More Discussions You Might Find Interesting
1. Programming
Hello.
I am programming in C on HP-UNIX system,i want ftp a file from remote pc which is window 2000 system,i donot how config my HP-UNIX and pc, i donot how program in C or in shell.
Thank you for help. (3 Replies)
Discussion started by: bdyjm
3 Replies
2. Windows & DOS: Issues & Discussions
Dear user
sorry if the subject is not for that fourm .. but I get mad .. I wana solve that problem.. I started my new semster .. and last semster.. and there I use the net under a very huge list of restriction .. no msn massenger .. no yahoo massenger .. no underground site .. no fourms (I am ... (2 Replies)
Discussion started by: RuDe_BuT_CoOoL
2 Replies
3. UNIX for Dummies Questions & Answers
I am trying to set samba up to join my windows 2000 domain and I am having troubles
If anyone if familiar with this help would be greatly appreciated
I issue the following command
# ./smbpasswd -j DOMAIN -r DOMAINCONTROLER
And the following gets returned
load_client_codepage: filename... (4 Replies)
Discussion started by: gennaro
4 Replies
4. UNIX for Dummies Questions & Answers
Hi Brothers,
Please, I've just purchased a new PC and I would like to have both win 2000 and freebsd in the same hard drive, ( 40GB and 128Mb ) can you please help how to set up my new hard drive , please!
Thank you.....
aka Polymorphous (2 Replies)
Discussion started by: Polymorphous
2 Replies
5. Programming
Hello
I need to translade the power of unix command shell (grep, sed, awk, wc, etc..) to windows.
In my work every day I administrate 15 unix server ans 18 windows server, and I have the problem the absolutly limitation of windows shell. I´m a system administrator but I know programming.
I... (2 Replies)
Discussion started by: dalmus
2 Replies
6. UNIX for Dummies Questions & Answers
All,
I am looking for the easiest solution that will let me remote access from a Windows 2000 client into a Solaris 8 server. Any suggestions?
Thanks Kevin (3 Replies)
Discussion started by: Kevin1166
3 Replies
7. Windows & DOS: Issues & Discussions
i have pleasure in using shell scripts and vi editor.
VI Improved on Linux is also good.
Is there a way that allows using shell as command interpretor
and VIm as editor to work on windows? (not vi.exe)
any help....... (1 Reply)
Discussion started by: paresh n doshi
1 Replies
8. Shell Programming and Scripting
I need to run a shell script on unix machine from windows 7.
I used the "RSH" command in win XP successfully for this, But on win 7 it is not working.
Can any body tell me how to run RSH on win 7 or any other command for similar use.
I use the command as below
rsh <unix m/c> -l <username>... (1 Reply)
Discussion started by: arup1980
1 Replies
LEARN ABOUT DEBIAN
xpamethod
xpamethod(7) SAORD Documentation xpamethod(7)
NAME
XPAMethod - XPA Communication Methods
SYNOPSIS
XPA supports both inet and unix (local) socket communication.
DESCRIPTION
XPA uses sockets for communication between processes. It supports three methods of socket communication: inet, localhost, and unix. In gen-
eral, the same method should be employed for all XPA processes in a session and the global environment variable XPA_METHOD should be used
to set up the desired method. By default, the preferred method is "inet", which is appropriate for most users. You can set up a different
method by typing something like:
setenv XPA_METHOD local # unix csh
XPA_METHOD=local; export XPA_METHOD # unix sh, bash, windows/cygwin
set XPA_METHOD=localhost # dos/windows
The options for XPA_METHOD are: inet, unix (or local), and localhost. On Unix machines, this environment setup command can be placed in
your shell init file (.cshrc, .profile, .bashrc, etc.) On Windows platforms, it can be placed in your AUTOEXEC.BAT file (I think!).
By default, inet sockets are used by XPA. These are the standard Internet sockets that are used by programs such as Netscape, ftp. etc.
Inet sockets utilize the IP address of the given machine and a (usually random) port number to communicate between processes on the same
machine or between different machines on the Internet. (Note that XPA has an Access Control mechanism to prevent unauthorized access of XPA
access points by other computers on the Net). For users connected to the Internet, this usually is the appropriate communication method.
For more information about setting up XPA communication between machines, see Communication Between Machines.
In you are using XPA on a machine without an Internet connection, then inet sockets are not appropriate. In fact, an XPA process often will
hang for many seconds while waiting for a response from the Domain Name Service (DNS) when using inet sockets. Instead of inet sockets,
users on Unix platforms can also use unix sockets (also known as local sockets). These sockets are based on the local file system and do
not make use of the DNS. They generally are considered to be faster than inet sockets, but they are not implemented under Windows. Use
local sockets as a first resort if you are on a Unix machine that is not connected to the Internet.
Users not connected to the Internet also can use localhost sockets. These are also inet-type sockets but the IP address used for the local
machine is the localhost address, 0x7F000001, instead of the real IP of the machine. Depending on how sockets are set up for a given plat-
form, communication with the DNS usually is not required in this case (though of course, XPA cannot interact with other machines). The
localhost method will generally work on both Unix and Windows platforms, but whether the DNS is required or not is subject to individual
configurations.
A final warning/reminder: if your XPA-enabled server hangs at startup time and your XPA_METHOD is inet, the problem probably is related to
an incorrect Internet configuration. This can be confirmed by using the unix method or (usually) the localhost method. You can use these
alternate methods if other hosts do not need access to the XPA server.
SEE ALSO
See xpa(7) for a list of XPA help pages
version 2.1.14 June 7, 2012 xpamethod(7)