11-17-2006
You can't connect 10baseT to a serial port! It won't work. 10baseT is not a serial port. They've got nothing to do with each other unless you've set up something crazy like SLIP.
I can't be certain from the description you've given me, but it sounds like the server has a nonstandard serial port connector that
looks like 10baseT -- not unheard of -- and you've found or made an adaptor cable for it to connect to your windows machine's serial port. If that's correct, you need to communicate with the serial port, not the network -- a serial port has nothing to do with networking unless you've set up SLIP or something. Think of a serial port as a single, devoted telnet connection that always exists and never closes.
I reccomend
tutty for communicating with serial consoles in Windows. Select the 'serial' protocol when you open it, leave the phone number blank since you're not talking to a modem, and pick the port options the console needs under the
connection -> serial options.
9 More Discussions You Might Find Interesting
1. Linux
Hi All,
I'm running RH 9.0 on a PII box with 160MB RAM. Just downloaded RealVNC X86 Linux (version 3.3.7). How can I get the HTTP listening port up ?
Thanks,
KENT (6 Replies)
Discussion started by: kxchen_home
6 Replies
2. UNIX for Advanced & Expert Users
I want to write a server application that would accept HTTP requests from client.
The server would be on a machine that has no connection to the INTERNET.
The clients that would be posting their HTTP requests would be doing so through webbrowser .Thus it would be sort of intranet application.... (0 Replies)
Discussion started by: rraajjiibb
0 Replies
3. UNIX for Dummies Questions & Answers
I want my server socket to listen on two ports in my machine. How do i achieve it? I will have two clients one connecting to 1 port and another to a different port. So my server needs to listen to both.
Thanks. (1 Reply)
Discussion started by: abc.working
1 Replies
4. UNIX for Advanced & Expert Users
Hello there,
I have a big problem, and I hope somebody can help me. I try to realize a port forward over three server. Here is a picture...
Client Server1 | Server2
------- ------- | -------
|...... | |...... | | |...... ... (2 Replies)
Discussion started by: Art007
2 Replies
5. UNIX for Dummies Questions & Answers
Server has more TIME_WAIT connections in Apache(port 80) Hi,
My webserver has 16GB of RAM and CentOS 5.5, Apache 2.2.3, It's shared webserver used of for webhosting. I have optmized the server as :
<IfModule prefork.c>... (4 Replies)
Discussion started by: chandranjoy
4 Replies
6. Cybersecurity
Hi Guys,
My certificate in /etc/ssh is different to what is on port 22.
username@server:~$ ssh-keyscan -p 22 127.0.0.1 > /tmp/rsa.tmp
# 127.0.0.1 SSH-1.99-OpenSSH_33.33
username@server:~$ ssh-keygen -lf /tmp/rsa.tmp
1024 46:something..................... 127.0.0.1... (0 Replies)
Discussion started by: mu100
0 Replies
7. UNIX for Dummies Questions & Answers
Hi Guys,
My certificate in /etc/ssh is different to what is on port 22.
username@server:~$ ssh-keyscan -p 22 127.0.0.1 > /tmp/rsa.tmp
# 127.0.0.1 SSH-1.99-OpenSSH_33.33
username@server:~$ ssh-keygen -lf /tmp/rsa.tmp
1024 46:something..................... 127.0.0.1... (0 Replies)
Discussion started by: mu100
0 Replies
8. Solaris
please find the below o/p for your reference
bash-3.00# fcinfo hba-port
HBA Port WWN: 21000024ff295a34
OS Device Name: /dev/cfg/c2
Manufacturer: QLogic Corp.
Model: 375-3356-02
Firmware Version: 05.03.02
FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies
9. Cybersecurity
Hi,
There is a recent case whereby it was reported that one of the production servers was hacked on port 1521. However, I am not sure how this was possible, as I checked that the OS firewall (iptables) is on :
# /etc/init.d/iptables status
Table: nat
Chain PREROUTING (policy ACCEPT)
num ... (7 Replies)
Discussion started by: anaigini45
7 Replies
ports(7) Miscellaneous Information Manual ports(7)
NAME
ports, port_names - Device (tty and lp) names for serial and parallel ports
SYNOPSIS
Default Serial Ports:
/dev/tty00
/dev/tty01 (not present on a single-port system)
Parallel Port:
/dev/lp0
DESCRIPTION
AlphaStation and AlphaServer systems provide one or two 9-pin serial communication ports. These ports are usually labelled 1 (COMM1) and 2
(COMM2), but they may be identified by different icons. Using the appropriate serial cable and terminator, you can connect a serial
printer, external modem, or character-cell terminal to a serial port. Most AlphaStation and AlphaServer systems also provide one parallel
port, for use with a parallel printer.
When you add a device to your system, the installation documentation may instruct you to map the device pathname to the port. These
devices are located in the /dev directory.
For serial-line ports, the two default device pathnames are: This pathname always maps to 1, COMM1, the lowest port number, an icon for a
terminal console, or the only serial port (on a single-port system). This pathname always maps to 2, COMM2, the next numbered port, or (if
one serial port is labeled with an icon for a terminal console) the remaining serial port.
If your system hardware has been extended to include additional serial ports, the pathnames /dev/tty02, /dev/tty03, and so forth, may also
be available to you. However, most systems have only /dev/tty00 and /dev/tty01 as the device pathnames for serial ports.
The one parallel port on an AlphaStation or AlphaServer may be labeled with the word printer or a printer icon. On some systems, the paral-
lel port may not be labeled. The device pathname for the parallel port is /dev/lp0. Currently, Tru64 UNIX does not fully support parallel
printers, so fewer devices are connected to this port as compared to serial ports.
If you are connecting a terminal console to your system, it must be connected to the serial port mapped to /dev/tty00. For other serial
devices, it does not matter which of the serial ports you choose for the connection. For example, suppose you are setting up a system that
has two serial ports, labeled 1 and 2. You intend to use a serial-line terminal rather than a workstation monitor as the system console and
also want to connect a serial-line printer to the system. In this case, you must connect the terminal to the port labeled 1 (with the
device pathname /dev/tty00). Therefore, you must connect the printer to the remaining port labeled 2 (with the device pathname /dev/tty01).
If, for the same type of system, you intend to use a workstation monitor as the system console, it does not matter which serial port you
use for a serial-line printer or modem. In other words, you can connect the printer to either port 1 (with pathname /dev/tty00) or port 2
(with pathname /dev/tty01). When prompted to enter a /dev/tty** pathname by the lprsetup script or the Print configuration tool in the CDE
Application Manager, you would specify /dev/tty00 if you connected the printer to port 1 or /dev/tty01 if you connected the printer to port
2.
See the System Administration manual for more information on setting up consoles (including remote consoles) and printers. See the
modem(7) reference page for more information on setting up modems.
SEE ALSO
Commands: lprsetup(8)
Devices: ace(7), modem(7)
System Administration delim off
ports(7)