Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Connecting to SUN server from PC Post 302131854 by zam on Tuesday 14th of August 2007 04:20:10 AM
Old 08-14-2007
PHP

Tried to use Putty ver 6 but it does not give any sign of life when I
try to opem serial connection

I am Using hyperterminal
I did some switch off/on etc... and
now I got prompt Ok ... any more ideas ???


ok ls
Not at a device tree node. Use 'dev <device-pathname>'.
ok
ok /
Stack Underflow
ok
ok tip
 

5 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Connecting to UNIX server

Hi, My knowledge bucket of UNIX is almost empty. I have developed an application in EXCEL which can create XML files (Metadata) from Binaries. These binaries are stored in UNIX server on regular intervals. Currently I am transferring all binaries(GBs of files) to WINDOWS using WINSCP and... (2 Replies)
Discussion started by: bobs
2 Replies

2. Solaris

Problem with connecting with Sun Java Web console

Hi, I have Solaris 10 8/07 on SPARC and I can't log in Web console. When I opened browser (Firefox 3) at localhost:6789 I get Save file dialog which asks me to save some file with .part at the end. What information should I provide to find out where is the trouble?.. Internet explorer says... (3 Replies)
Discussion started by: Sapfeer
3 Replies

3. Shell Programming and Scripting

Connecting to other server thru ftp

Hi, Can someone help me on how to ftp to UNIX server from an another UNIX Server. I tried the follwoing but it is not working. ftp -n 10.10.0.1 quote user usrname quote pass passwd ls Though ftp is starting it is not allowing me run command..... it is asking to Thanks in... (5 Replies)
Discussion started by: EmbedUX
5 Replies

4. Shell Programming and Scripting

Connecting to Windows Server

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

5. Hardware

SUN V245 Connecting To router Through Alom

Hello. I have a sun v245 and I have no hard drive for it yet but i would like to connect it to my home router by ethernet cable so I can use Alom remotely. Could someone please tell me how to set it up. Thank You (1 Reply)
Discussion started by: SunV245
1 Replies
REMOTE(5)							File Formats Manual							 REMOTE(5)

NAME
remote - remote host description file DESCRIPTION
The systems known by tip(1C) and their attributes are stored in an ASCII file which is structured somewhat like the termcap(5) file. Each line in the file provides a description for a single system. Fields are separated by a colon (``:''). Lines ending in a character with an immediately following newline are continued on the next line. The first entry is the name(s) of the host system. If there is more than one name for a system, the names are separated by vertical bars. After the name of the system comes the fields of the description. A field name followed by an `=' sign indicates a string value follows. A field name followed by a `#' sign indicates a following numeric value. Entries named ``tip*'' and ``cu*'' are used as default entries by tip, and the cu interface to tip, as follows. When tip is invoked with only a phone number, it looks for an entry of the form ``tip300'', where 300 is the baud rate with which the connection is to be made. When the cu interface is used, entries of the form ``cu300'' are used. CAPABILITIES
Capabilities are either strings (str), numbers (num), or boolean flags (bool). A string capability is specified by capability=value; e.g. ``dv=/dev/harris''. A numeric capability is specified by capability#value; e.g. ``xa#99''. A boolean capability is specified by simply listing the capability. at (str) Auto call unit type. br (num) The baud rate used in establishing a connection to the remote host. This is a decimal number. The default baud rate is 300 baud. cm (str) An initial connection message to be sent to the remote host. For example, if a host is reached through port selector, this might be set to the appropriate sequence required to switch to the host. cu (str) Call unit if making a phone call. Default is the same as the `dv' field. di (str) Disconnect message sent to the host when a disconnect is requested by the user. du (bool) This host is on a dial-up line. dv (str) UNIX device(s) to open to establish a connection. If this file refers to a terminal line, tip(1C) attempts to perform an exclu- sive open on the device to insure only one user at a time has access to the port. el (str) Characters marking an end-of-line. The default is NULL. `~' escapes are only recognized by tip after one of the characters in `el', or after a carriage-return. fs (str) Frame size for transfers. The default frame size is equal to BUFSIZ. hd (bool) The host uses half-duplex communication, local echo should be performed. ie (str) Input end-of-file marks. The default is NULL. oe (str) Output end-of-file string. The default is NULL. When tip is transferring a file, this string is sent at end-of-file. pa (str) The type of parity to use when sending data to the host. This may be one of ``even'', ``odd'', ``none'', ``zero'' (always set bit 8 to zero), ``one'' (always set bit 8 to 1). The default is even parity. pn (str) Telephone number(s) for this host. If the telephone number field contains an @ sign, tip searches the file /etc/phones file for a list of telephone numbers; c.f. phones(5). tc (str) Indicates that the list of capabilities is continued in the named description. This is used primarily to share common capabil- ity information. Here is a short example showing the use of the capability continuation feature: UNIX-1200: :dv=/dev/cau0:el=^D^U^C^S^Q^O@:du:at=ventel:ie=#$%:oe=^D:br#1200: arpavax|ax: :pn=7654321%:tc=UNIX-1200 FILES
/etc/remote SEE ALSO
tip(1C), phones(5) 4.2 Berkeley Distribution May 15, 1985 REMOTE(5)
All times are GMT -4. The time now is 10:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy