01-23-2009
How to close TELNET Connection
Hi,
I have logged into a system using Telnet and iam unable to close the connection to connect to the next system using arrays.
Iam getting error "Connection Timed Out"
Iam using net::Telnet module.
Please suggest..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a new SUN server from a sister company, and have been able to network it, and ping the server...however i can't telnet into the box.
When it was at the sister companies site, we were able to telnet in then...just not not its on out network!
Does anyone have a suggestion to what i need... (3 Replies)
Discussion started by: colesy
3 Replies
2. UNIX for Dummies Questions & Answers
Hi
Can someone help me what is the problem, when i try to login via ftp, though i entered the correct password, i got an error message
Connection refused.
please help. thanks (3 Replies)
Discussion started by: kaibiganmi
3 Replies
3. Shell Programming and Scripting
i have 2 servers
test1
production2
------------------------------------
i have script called naveed2.sh in test1.Actually i m trying to connect from scritp naveed2.sh into server production2.
below the contents of script naveed2.sh
#!/bin/ksh
telnet production2.com< n2.txt... (2 Replies)
Discussion started by: ali560045
2 Replies
4. Programming
Hello. I would like to know how to close an existing tcp socket. I have read some stuff and learned how to create a socket and then close it but have not found anything about how to close an existing tcp socket created by another application. The situation is this: I have an ODBC server running and... (6 Replies)
Discussion started by: raidzero
6 Replies
5. Shell Programming and Scripting
Hi. !
When I use the 'NOHUP' along with the '&', the process will be running in the background. Even when I attempt to close (Meaning 'EXIT') the session (say PUTTY in this case), it wont exit unless the process is completed.
But, say when I forcefully terminate the session (SHUT DOWN the... (2 Replies)
Discussion started by: WinBarani
2 Replies
6. Solaris
Hi,
I use solaris Unix .
I find there is some problem in application and it generate many "close-wait" tcp connect and stay in the server . it is generate by process id 7740
root@XX # netstat -an | grep CLOSE_WAIT | wc -l
285
root@XX # netstat -an | grep CLOSE_WAIT
10.158.35.4.34805 ... (2 Replies)
Discussion started by: abcdef
2 Replies
7. Shell Programming and Scripting
Hello people, I am creating a script that will alert me in an ftp or telnet account on my system expires. FTP part is ok, but when I am entering the 3 script, it stucks. I can see that the script will not close the telnet seession. Can you please check and let me know what I am doing wrong? What if... (7 Replies)
Discussion started by: drbiloukos
7 Replies
8. Solaris
Can ssh to server. Asks for password.
Then seems to time out and close the connection. Any ideas?
---------- Post updated at 09:30 AM ---------- Previous update was at 07:51 AM ----------
Here is output from ssh -vvv -l user <IPaddress>
debug3: packet_send2: adding 64 (len 59 padlen 5... (4 Replies)
Discussion started by: psychocandy
4 Replies
9. UNIX for Dummies Questions & Answers
I'm trying to remotely run an upgrade script (via SSH) that update the SSH script on several hosts, just need to add several flags for the ssh command to look like this:
ssh -Nf -i id_logs -o ExitOnForwardFailure=yes -o StrictHostKeyChecking=no -o ServerAliveInterval=60 -o ServerAliveCountMax=5... (4 Replies)
Discussion started by: OdedOvdat
4 Replies
10. Shell Programming and Scripting
Dear all,
We have a service that we start up remotely with rsh but unfortunately, the rsh never returns to the calling server. This seems to be because the processes of the service we've just started hold the port open.RBATTE1 @ /home/RBATTE1>netstat -na|grep 49.51
tcp4 0 0 ... (1 Reply)
Discussion started by: rbatte1
1 Replies
tels(7) Miscellaneous Information Manual tels(7)
NAME
tels, telm - STREAMS Telnet slave (pseudo-terminal) driver, STREAMS Telnet master driver (used by telnetd only), respectively
SYNOPSIS
DESCRIPTION
A Telnet pseudo-terminal consists of a tightly-coupled pair of character devices, called the master device and slave device. The master
and slave device drivers work together to provide a Telnet connection on the server side where the master provides a connection to and the
slave provides a terminal device special file access for the Telnet application processes, as depicted below:
--------------------------
| Pseudo terminal functions|
Application <--> |--------------------------| <--> telnetd
Processes | Slave | Master |
| (tels) | (telm) |
--------------------------
The slave driver, with (STREAMS pty emulation module) and (STREAMS line discipline module) pushed on top (not shown for simplicity), pro-
vides a terminal interface as described in termio(7). Whereas devices that provide the terminal interface described in termio(7) have a
hardware device behind them; in contrast, the slave device has manipulating it through the master side of the Telnet pseudo terminal.
There are no nodes in the file system for each individual master device. Rather, the master driver is set up as a STREAMS clone(7) driver
with its major device number set to the major for the clone driver and its minor device number set to the major for the driver. The master
driver is opened by telnetd using the open(2) system call with as the device file parameter. The clone open finds the next available minor
number for the master device. The master device is available only if it and its corresponding slave device are not already opened.
In order to use the STREAMS Telnet subsystem, a node for the master driver and N number of Telnet slave devices must be installed.
The number of slave devices is set by a kernel tunable parameter called This can be modified using SAM; its default and minimum value is
60. The value of is the upper limit of the number of telnet sessions that can be opened.
Multiple opens are allowed on the Telnet slave device.
The master and slave drivers pass all STREAMS messages to their adjacent drivers. When the connection is closed from the Telnet client
side, an message is sent to the corresponding slave device which will render that slave device unusable. The process on the slave side
gets the errno when attempting a write(2) system call to the slave device file but it will be able to read any data remaining in the slave
stream. Finally, when all the data has been read, the read(2) system call will return 0, indicating that the slave can no longer be used.
AUTHOR
and were developed by HP.
FILES
Streams Telnet master clone device
Streams slave devices where
N is the minor number of the slave device and 0 < N <
SEE ALSO
insf(1M), open(2), ioctl(2), streamio(7), ldterm(7), telnetd(1M), ptem(7).
tels(7)