07-23-2004
I've never tried connecting a windows and a unix via a serial cable. But if there's an ethernet port in both machines, a crossover cable (about $10) can get the two machines to communicate with each other.
Another problem I ran into while doing this was the IP detection settings. Apparently, the two machines need to have the same setting. Here at work, the two computers we've connected both expect static IP addresses (which you can set). I haven't tried it yet, but it might be possible to have both machines expect dynamic IP addresses, too.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi ,
I need to have an application where in I am able to create a virtual Serial port on a UNIX machine for a remote device which is accessible by a IP address and a port number (by terminal server). Both the machine and the remote device are on the same network. So after this application is... (1 Reply)
Discussion started by: naveenkj
1 Replies
2. UNIX for Dummies Questions & Answers
We're running SCO Unix Openserver 5.05 and I'm having trouble with serial communication between the com2 serial port and a handheld device. Downloading data from Unix to the handheld works perfectly, but the other way around creates a major problem. I don't know whether it's a buffer overflow or... (1 Reply)
Discussion started by: Aretha
1 Replies
3. UNIX for Dummies Questions & Answers
I need make serial data from virtual serial ports available on a TCP/IP network.
For communications with hardware COM ports to send and receive serial data over a local network or the Internet.
Example:
POSIX machine (/dev/ttyS0) <--- TCP/IP ---> Windows machine COM1
Please help! I try use... (0 Replies)
Discussion started by: steel98
0 Replies
4. Solaris
I am working with solaris 9 sparc and I want to connect physical device in serial port but when I am connecting it,It is showing the error window saying--
So can any1 tell me the reason or is there any package I have to add to work with serial port??? (2 Replies)
Discussion started by: smartgupta
2 Replies
5. UNIX for Dummies Questions & Answers
A neighbour's Ubuntu 10.04 machine has five serial ports, one on the motherboard and four on a PCI card. However, only four cards are showing:
# dmesg | grep tty
console enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
00:08: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
... (2 Replies)
Discussion started by: dotancohen
2 Replies
6. Shell Programming and Scripting
Hi,
I have a external board connected to my serial port. I need to execute "shutdown -r now" command when system boot up. When system boots up it requires a username ans password. Then I need to run my command. I can use rc script but that is rebooting system before it asks for username and... (0 Replies)
Discussion started by: charlie.arya
0 Replies
7. UNIX for Advanced & Expert Users
Hi,
can anyone please tell me how can i do port forwarding from unix box to windows box.
Which command will be used for this one.
thanks in advance.
Arpit (1 Reply)
Discussion started by: thearpit
1 Replies
8. Solaris
Hi Everyone,
In my environment, I have few T5220. On the iLOM Management Card, I have both Network and Serial port are cabled, I don't have any issues while I try to connect using Network Management port, but when I try to connect the serial port for the same server which is actually connected... (3 Replies)
Discussion started by: bobby320
3 Replies
9. Shell Programming and Scripting
hi,
when i finish running some scripts in unix...some csv file is getting generated...now im manually taking this csv file from this generated directory and using FTP, i'm importing to windows os and saving in a directory...
please give me a script to automate this..so that i can add in my... (1 Reply)
Discussion started by: dll_fpga
1 Replies
10. Solaris
Hello,
I have an unloaded T5140 machine and want to access the ILOM for the first time and subsequently the network port after that., and then load Solaris 10 the final January 2011 build.
The first part is what confuses me -the cabling.
I am coming from a Windows machine (w/appropriate... (5 Replies)
Discussion started by: joboy
5 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)