Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Hyperterminal null modem connection to Solaris Post 54476 by seethams on Sunday 15th of August 2004 06:20:41 PM
Old 08-15-2004
Hyperterminal null modem connection to Solaris

I am new to Unix. I just got my SUN box from ebay with Solaris supposedly preloaded. The problem is I am unable to connect via Hyperterminal to Solaris, or more to the point, cannot tell if I have a successful connection and that solaris is the one not properly booted up.

I hooked up a null modem cable between my PC serial port and one of the A/B ports on SUN. I setup the hyperterminal to use COM1; the connection fails with error 633, what ever that is. In the control panel on windows, I defined a new 'direct computer-to-computer' connection via COM1 and checked the SLIP unix connection option,; it did not work.

When I used COM3 instead when setting up the Hyperterminal it successfully connected and I have a blank screen with no prompt. I have no idea as to what to do next. Any help will be appreciated. Thanks.
 

10 More Discussions You Might Find Interesting

1. Solaris

null modem serial cable for server testing

HI all, i still have a problem when using null modem to see the output from my server(sun ultra en 3000). i followed the instruction from the internet, but it is not working. 1. i am using db9(5 4, 2 rows,put in laptop serial port) and db25(13 12, 2 rows,put in (A) server serial port). 2.... (3 Replies)
Discussion started by: waterbear
3 Replies

2. Solaris

null modem for testing

hi all.. sorry for repeating the same question many times, i just set up a null modem, i am using this as reference : DB25 DB9 -- - 2 TD ---- 2 RD 3 RD ---- 3 TD 4 RTS ---- 8 CTS 5 CTS ---- 7 RTS 7 GND ---- 5 GND 6 DSR -+ +--- 4 DTR 8... (0 Replies)
Discussion started by: waterbear
0 Replies

3. Solaris

Solaris Hyperterminal

Hi all, I currently have my WinXP machine connected to my Sun server via serial cable then hyperterminal. I would like to connect my Solaris 10 machine to the server via serial cable but there doesn't appear to be a hyperterminal application included with Solaris 10. Anyone know of a... (3 Replies)
Discussion started by: bad-ash
3 Replies

4. Solaris

hyperterminal serial solaris 8

Hi All, I connected my serial connection to the installation of solaris 8 and sorry to tell you I use XP/hyperterminal, don't get mad on me... I might use ubuntu later. When I'm installing it, it's ask me below: What type of terminal are you using? 1) ANSI Standard CRT 2) DEC VT52 ... (3 Replies)
Discussion started by: itik
3 Replies

5. Solaris

Null modem cable in Ultra sparc 10

Hi Gurus, Can I use null modem cable in Ultra sparc 10 workstation Thanks (3 Replies)
Discussion started by: kumarmani
3 Replies

6. AIX

serial modem connection

I configured the serial modem in my P6-550 AIX 5.3 box But i dont have telephone line. when I run the command # cu -l /dev/tty1 the output is as follows does it mean that my modem is responding to the command? can i say my serial port is working and communicating fine? Connected ... (3 Replies)
Discussion started by: pchangba
3 Replies

7. Hardware

Serial connection CAT5 instead of RS232 and Null Modem or Straight cable.

Hello, I want to connect a VT520 terminal to p3 linux box. I have two questions regarding the connection. First, is it possible to use RJ45 instead of RS232 cable. (with DB9 pin to RJ45 and DB25 to RJ45 converter). Second point is that; do i need null modem cable or straight cable... (5 Replies)
Discussion started by: vectrum
5 Replies

8. Solaris

No prompt from Solaris to WinXP Hyperterminal

hi I am new to unix and have found a SPARCstation 5 in the shed. I'm told by my father that it was working when it was put there about 8 years ago. It seems to boot up and makes all the right noises, both discs appear to make a noise, the keyboard lights flash etc., etc., but i can't seem to get... (2 Replies)
Discussion started by: harrystrickland
2 Replies

9. Hardware

Modem connection between two local PCs

Hello everybody, I didn't know were to post this, so i posted here in hardware section. I'm having some troubles while trying to interconnect two pc's via modem (soft fax modem, RJ-11 jack). One is a Handheld PC (HP Jornada 728) with a single fax modem slot, and the other computer is a PC with... (6 Replies)
Discussion started by: Zykl0n-B
6 Replies

10. Solaris

Carrier Detection in Solaris 8 for Dial in and Null Modem Connections

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
asy(7D) 							      Devices								   asy(7D)

NAME
asy - asynchronous serial port driver SYNOPSIS
#include <fcntl.h> #include <sys/termios.h> open("/dev/term/n", mode); open("/dev/tty/n", mode); open("/dev/cua/n", mode); DESCRIPTION
The asy module is a loadable STREAMS driver that provides basic support for Intel-8250, National Semiconductor-16450, 16550, and some 16650 and 16750 and equivalent UARTs connected via the ISA-bus, in addition to basic asynchronous communication support. The asy module supports those termio(7I) device control functions specified by flags in the c_cflag word of the termios structure, and by the IGNBRK, IGNPAR, PARMRK, INPCK, IXON, IXANY, or IXOFF flags in the c_iflag word of the termios structure. All other termio(7I) functions must be performed by STREAMS modules pushed atop the driver. When a device is opened, the ldterm(7M) and ttcompat(7M) STREAMS modules are automatically pushed on top of the stream, providing the standard termio(7I) interface. The character-special devices /dev/term/a, /dev/term/b, /dev/term/c and /dev/term/d are used to access the four standard serial ports (COM1, COM2, COM3 and COM4 at I/O addresses 3f8, 2f8, 3e8 and 2e8 respectively). Serial ports on non-standard ISA-bus I/O addresses are accessed via the character-special devices /dev/term/0, /dev/term/1, etc. Device names are typically used to provide a logical access point for a dial-in line that is used with a modem. To allow a single tty line to be connected to a modem and used for incoming and outgoing calls, a special feature is available that is con- trolled by the minor device number. By accessing character-special devices with names of the form /dev/cua/n, it is possible to open a port without the Carrier Detect signal being asserted, either through hardware or an equivalent software mechanism. These devices are commonly known as dial-out lines. Note - This module is affected by the setting of certain eeprom variables, ttya-ignore-cd and ttya-rts-dtr-off (and similarly for ttyb-, ttyc-, and ttyd- parameters). For information on these parameters, see the eeprom(1M) man page. Note - For serial ports on the standard COM1 to COM4 I/O addresses above, the default setting for ttya-ignore-cd and ttya-rts-dtr-off is true. If any of these ports are connected to a modem, these settings should be changed to false. For serial ports on non-standard I/O addresses, the default setting for ttya-ignore-cd and ttya-rts-dtr-off is false. APPLICATION PROGRAMMING INTERFACE
Once a /dev/cua/n line is opened, the corresponding tty line cannot be opened until the /dev/cua/n line is closed. A blocking open will wait until the /dev/cua/n line is closed (which will drop Data Terminal Ready, after which Carrier Detect will usually drop as well) and carrier is detected again. A non-blocking open will return an error. If the /dev/ttydn line has been opened successfully (usually only when carrier is recognized on the modem), the corresponding /dev/cua/n line cannot be opened. This allows a modem to be attached to /dev/term/[n] (renamed from /dev/tty[n]) and used for dial-in (by enabling the line for login in /etc/inittab) or dial-out (by tip(1) or uucp(1C)) as /dev/cua/n when no one is logged in on the line. IOCTLS
The standard set of termio ioctl() calls are supported by asy. Breaks can be generated by the TCSBRK, TIOCSBRK, and TIOCCBRK ioctl() calls. The input and output line speeds may be set to any speed that is supported by termio. The speeds cannot be set independently; for example, when the output speed is set, the input speed is automatically set to the same speed. When the asy module is used to service the serial console port, it supports a BREAK condition that allows the system to enter the debugger or the monitor. The BREAK condition is generated by hardware and it is usually enabled by default. A BREAK condition originating from erroneous electrical signals cannot be distinguished from one deliberately sent by remote DCE. The Alternate Break sequence can be used as a remedy against this. Due to a risk of incorrect sequence interpretation, SLIP and certain other binary protocols should not be run over the serial console port when Alternate Break sequence is in effect. Although PPP is a binary proto- col, it is able to avoid these sequences using the ACCM feature in RFC 1662. For Solaris PPP 4.0, you do this by adding the following line to the /etc/ppp/options file (or other configuration files used for the connection; see pppd(1M) for details): asyncmap 0x00002000 By default, the Alternate Break sequence is a three character sequence: carriage return, tilde and control-B (CR ~ CTRL-B), but may be changed by the driver. For more information on breaking (entering the debugger or monitor), see kbd(1) and kb(7M). ERRORS
An open() will fail under the following conditions: ENXIO The unit being opened does not exist. EBUSY The dial-out device is being opened while the dial-in device is already open, or the dial-in device is being opened with a no-delay open and the dial-out device is already open. EBUSY The unit has been marked as exclusive-use by another process with a TIOCEXCL ioctl() call. EINTR The open was interrupted by the delivery of a signal. FILES
/dev/term/[a-d] /dev/term/[012...] dial-in tty lines /dev/cua/[a-d] /dev/cua/[012...] dial-out tty lines /kernel/drv/amd64/asy 64-bit kernel module for 64-bit x86 platform /kernel/drv/asy.conf asy configuration file ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |x86 | +-----------------------------+-----------------------------+ SEE ALSO
tip(1), kbd(1), uucp(1C), eeprom(1M), pppd(1M), ioctl(2), open(2), termios(3C), attributes(5), ldterm(7M), ttcompat(7M), kb(7M), termio(7I) DIAGNOSTICS
asyn: silo overflow. The hardware overrun occurred before the input character could be serviced. asyn: ring buffer overflow. The driver's character input ring buffer overflowed before it could be serviced. SunOS 5.10 9 Oct 2004 asy(7D)
All times are GMT -4. The time now is 08:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy