We could be more specific if you state which version of Windows and which version of unix.
The general solution is to use Windows "rsh" which is specifically for running unix commands on a unix server from a Windows command prompt (or Windows Batch File). Check with your Network Administrator whether remote shell is allowed in your security policy.
You will find many methods described on the Internet to get Windows rsh to work. Here is the simplest.
1) Choose a user on the unix server "unixserver" to host the commands. "unixuser".
Do not use "root" because this is inherantly insecure.
2) Note the username you use to log into you PC. "dosuser".
3) Create (or add to) a .netrc file in the home directory of "unixuser" with permissions 600 owned by "unixuser" and containing:
On some systems where we have IP address above it has to be fully qualified host name which you can find out by issuing "who -R am i" from a telnet session from the same PC.
4) Test rsh from the Windows command prompt. For example run unix command "pwd".
Interestingly the obvious command to try is "who am i" but this will not work because "rsh" does not have a terminal context.
The command to be executed from rsh could be a shell script containing thousands of commands.
Ok I've lost myself and hit a brick wall.
What I am trying to do is avoid the login screen when the machine is turned on. So no login screen is needed unless you turn the machine on and log out to login and change users. But as I said before I've hit a brick wall. I got not an idea of what I... (4 Replies)
Hey all,
I'm trying to configure a system so when it reboots it'll automatically log as a user I have selected. I've never done this nor' as I to sure on how to. This is teh best I have found on teh web and well I've changed a few things. but does anyone who has done this know if it'll work... (1 Reply)
I am trying to bypass the login screen when the system boots and auto-login to open windows. I believe I need to modify the S99dtlogin but I don't know what to add/modify. Has anyone ever created an auto-login for Solaris 8? (1 Reply)
I am trying to bypass the login screen when the system boots and auto-login to open windows. I believe I need to modify the S99dtlogin but I don't know what to add/modify. Has anyone ever created an auto-login for Solaris 8? (1 Reply)
Hi All,
We have some HP unix servers and sometimes we logon there thru a dedicated Windows server that has Reflection X on it in case we need X. In this case we always need to export DISPLAY=winservername:0.0
I want to automate this thing in .profile file. If e.g. $TERM = hpterm (thru... (2 Replies)
Hi All,
How do you get around SFTP not having the 'cat' command to set up scripts to run cron jobs for passwords?
I am use to the FTP allowing that, but we are converting to SFTP and need to be able to still run the same scripts in off hrs. Is there a way to still cat the password at the prompt... (14 Replies)
Hi,
I looked into lot of posts on this question but i could not figure out the solution. we are using the following ftp shell program to send the file to target server.
#!/usr/bin/ksh
ftp -n -i<<EOF 2>&1
open <target server ip>
user <username> <pwd>
lcd /sc/doc/prd/FCSTP
put file1.txt... (3 Replies)
Hi,
While trying to supress password prompt using ssh. I have added .ssh folder manually and generated public key and added to authorized_keys file in the remote machine. But still it's prompting for passwords with the following message:
Permission denied... (5 Replies)
Hello All ,
Requiremnt : i want to login to putty automatically and change the settings like i want , for ex : changing the "lines of scrollback" , " under colors , want to check to checkmark the option use system colors" . Like this i want to do .
I have a bash file created to login . But... (2 Replies)
Discussion started by: radha254
2 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)