01-06-2003
I used the same commands you posted and got the same results.
Nothing after connecting via tip.
Of course, I don't have a modem on my system - that's where you are having a problem. The system does not really 'see' your modem. Check the cable connecting it and make sure it's plugged in and works correctly. Also make sure your TERM is set correctly (vt100 works for almost everything!).
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Can anybody help me?
I am developing a utility for automating message paging to a BT alphanumeric pager.
I am using a USR 56K Fax-modem connected to /dev/cuab on a Sun Ultra-10. I am using the UNIX 'tip' utility to connect to the modem and I have configured the modem as follows: Baud Rate:... (2 Replies)
Discussion started by: mybeat
2 Replies
2. Linux
Hi!
I'm looking for a sollution on this task:
is there any way to make linux as some sort of personal ISP, with would let me/somebody else get internet access by dialing up to linux box through phoneline?
to use it as sort of a proxy or something simular?
I could manage it on windows 2000... (2 Replies)
Discussion started by: V@no
2 Replies
3. UNIX for Dummies Questions & Answers
Im using Kinternet with a Lucent modem on Suse 9.0
Ive installed the ltmodem driver and suse says the device is ready and configured. Ive configured it at /dev/ttyS0
This is the log that Kinternet gives after trying to connect:
SuSE Meta pppd (smpppd-ifcfg), Version 1.06 on linux.
Status... (0 Replies)
Discussion started by: Synbios
0 Replies
4. Solaris
I am looking for a dial-up remote printing solution as under :
1. We have a Centralized location where Sun Solaris (A) is installed. From here printing command will be despatched.
2. This printing command will be routed to WAN cloud to Main Branches (B1,B2,B3)and from there, printer at... (0 Replies)
Discussion started by: jayvee
0 Replies
5. UNIX for Dummies Questions & Answers
I currently access a remote Unix server which has an external modem connected to one of it's serial ports (/dev/cua/b). At times, this server undergoes a hard reset and for some reason this disallows us from making use of the modem any longer. A hard reset of the modem always seems to fix the... (0 Replies)
Discussion started by: ebender1
0 Replies
6. Solaris
Dear All,
i have problem during install modem dial up with smc in solaris 10.
i can't find "login" because it's stop in _receive started transmit started.
thanks for your attention.
this is the list during i dial to this number :
altconn called
Device Type ACU wanted... (0 Replies)
Discussion started by: mr.ridho
0 Replies
7. UNIX for Advanced & Expert Users
Hello to all,
I have one problem and hope you'll be able to help me.
It's about connecting Windows PC machine to Unix machine via dial up through Hyper terminal.
Connection was working in the past. In the meantime, windows machine is replaced (win XP) and unix machine stayed as is. So nothing is... (1 Reply)
Discussion started by: Mick
1 Replies
8. Solaris
I am having troubles with carrier detection for dialing in via a modem or direct connection via a null modem connection under Solaris 8 (i.e. login session remains active after the modem disconnects). I tried two different dumb modems (which do not respond to AT commands) on the machine that I am... (6 Replies)
Discussion started by: rstor
6 Replies
9. Shell Programming and Scripting
Hi All,
Need to connect to target host and execute a command and connect back to source host to continue with next set of command execution.
Is there a utility/command using which we can connect to target host ?
Please suggest.
Note: Netezza database is instaled on Linux server. ... (4 Replies)
Discussion started by: Nagaraja Akkiva
4 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)