12-01-2003
Oh, I remeber seeing such a thread before, where I had written that you can have a server socket listening on windows and the client socket on your unix system. So if your job on unix gets ovre the client socket on unix will notify the server socket on the windows system.
Let me find that thread and post it as a link (doing this for the first time)
here is the link
Last edited by linuxpenguin; 12-01-2003 at 02:08 PM..
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. 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
4. 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
5. IP Networking
Hello,
I have a requirement like -
I need to connect to specific Unix machine.That machine authenticates the user who is logging in. I am accessing from XP machine.
Is possible to supply the Username & Password along with Host name and port, from Windows command prompt? If so how? (13 Replies)
Discussion started by: cassiel
13 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 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)