Automating telnet checking for success/failure


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Automating telnet checking for success/failure
# 1  
Old 05-14-2010
Automating telnet checking for success/failure

Hi

I wanna automate the telnet process for port connection..

Code:
# telnet 0 port_number
Trying 0.0.0.0...
Connected to 0.
Escape character is '^]'.


If its connected how to make it disconnect automatically..
And how to check for success or failure..

Last edited by Scott; 05-14-2010 at 08:33 PM.. Reason: Code tags, please...
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Shell script to execute Oracle procedure and trigerring email on success and failure

Here is the shell script which need to trigger a stored procedure and when the record count is 0 then it should capture in the log that 0 duplicate records are found and if it's more than 0 then log with no of records. Also if there is any sqlerror then it should write the same in the log file and... (17 Replies)
Discussion started by: senmng
17 Replies

2. Red Hat

Fedora 19 "useradd" failure, GUI success

Hey guys/gals, I have a Fedora 19 box with a 26TB RAID set mounted as my home directory # mount|grep home /dev/md0 on /home type xfs (rw,relatime,seclabel,attr2,inode64,logbsize=128k,sunit=256,swidth=3584,noquota) I have been able to add/modify user accounts using VNC +... (4 Replies)
Discussion started by: jjinno
4 Replies

3. Shell Programming and Scripting

How to write SCP success or failure to a file

Does anyone know how to write the results (success and failure) to a file. I am using TCSH on a Solaris machine. I have the following code for a successful SCP...could someone help me add to this so it caputres failures also? CODE SO FAR (received from a previous post): scp sourcefile.txt... (3 Replies)
Discussion started by: thibodc
3 Replies

4. Shell Programming and Scripting

Success/failure status of telnet connection

Hi, I am running a shell script which will spawn the telnet and login. But sometimes, the telnet session itself is not getting spawned. My requirement is, if the telnet session is not spawned, the user must be notified that it failed. Is there any command to capture the status of telnet... (2 Replies)
Discussion started by: merin
2 Replies

5. Solaris

Failure to telnet in new install Sun5.10

Hi, I telnet to the localost in new install Sun 5.10 I get below error I also telnet from other to this mahcine but get "access deny" after input root password. The password is correct as I can login in console "Not on system console connection to unknown cloase by foregin host" Why ,... (25 Replies)
Discussion started by: chuikingman
25 Replies

6. Shell Programming and Scripting

Automating mailing via telnet to smtp

Hi, I am trying to write a ksh script to send an attachment via telnet to an SMTP server. I'm using MKS Toolkit. mail, mailx, sendmail, nc are not working on the server where I have MKS Toolkit installed. If I type the following from the command prompt I receive an email: telnet x.com... (0 Replies)
Discussion started by: dukeEarth
0 Replies

7. AIX

telnet failure

My hardware is a JS21 IBM server with AIX 5.3L. I can console into the blade but at times I am able to telnet to a LDAP server on port 389, but then there are times I can not telnet to the port. I can't ping the server when I experience this issues. My application I support goes down in flames and... (3 Replies)
Discussion started by: billet75
3 Replies

8. Shell Programming and Scripting

Automating telnet and ftp

Hi, I want to automate FTP. I have a fair idea that this can be done using expect scripting. But I dont how to do it. Please, can anyone give me an example of how to do it in Unix. Thanks in advance (2 Replies)
Discussion started by: sendhilmani123
2 Replies

9. UNIX for Advanced & Expert Users

Capturing sendmail success/failure?

I am working on a project that will use sendmail to send reports form a shell script. Since these reports are very important and go out at all times of the day, I need to be able to capture if sendmail is unsuccessful or errors out. The emails may have multiple recipients with multiple attachments.... (2 Replies)
Discussion started by: ssracer
2 Replies

10. Shell Programming and Scripting

Determining the failure or success of FTP

Hi there, I am in the process of writing a shell script to transfer files to a remote directory. Is there a method to determine the success or the failure of the ftp process. Regards Jim (4 Replies)
Discussion started by: JimJim
4 Replies
Login or Register to Ask a Question
telnetd(8)						      System Manager's Manual							telnetd(8)

NAME
telnetd - The DARPA telnet protocol server SYNOPSIS
telnetd [-debug [port]] [-D modifier ...] FLAGS
Starts telnetd manually, rather than through inetd, on alternate TCP port number port (if specified). Prints out debugging information. modifiers are: Prints information about negotiation of telnet options Same as options with additional processing information Displays the data stream received by telnetd Displays data written to the pty Not yet implemented DESCRIPTION
The telnetd daemon is a server that supports the DARPA (Defense Advanced Research Projects Agency) standard telnet virtual terminal proto- col. telnetd is invoked by the Internet server (see inetd(8)) normally for requests to connect to the telnet port as indicated by the /etc/services file (see services(4)). The -debug flag may be used, to start up telnetd manually. If started up this way, port may be specified to run telnetd on an alternate TCP port number. The -D options may be used for debugging purposes. This allows telnetd to print out debugging information to the connection, allowing the user to see what telnetd is doing. The telnetd daemon operates by allocating a pseudoterminal device (see pty(7)) for a client, then creating a login process that has the slave side of the pseudoterminal as stdin, stdout, and stderr. telnetd manipulates the master side of the pseudo-terminal, implementing the telnet protocol and passing characters between the remote client and the login process. When a telnet session is started up, telnetd sends telnet options to the client side, indicating a willingness to do remote echo of charac- ters, to suppress go ahead, to do remote flow control, and to receive terminal type information, terminal speed information, and window size information from the remote client. If the remote client is willing, the remote terminal type is propagated in the environment of the created login process. The pseudoterminal allocated to the client is configured to operate in cooked mode, and with XTABS and CRMOD enabled (see tty(7)). The telnetd daemon is willing to do: echo, binary, suppress go ahead, and timing mark. telnetd is willing to have the remote client do: line mode, binary, terminal type, terminal speed, window size, toggle flow control, environment, X display location, and suppress go ahead. The telnetd daemon never sends telnet go ahead commands. Note that binary mode has no common interpretation except between similar operating systems (Unix compatible systems in this case). Note also that the terminal type name received from the remote client is converted to lowercase. The telnet command uses the default Type-of-Service value recommended by RFC1060, which is as follows: Low delay You can configure this value by specifying it in the /etc/iptos file. For more information, see iptos(4). By default, the telnetd daemon starts the login dialog using the login string specified in the message field of the /etc/gettydefs file. If you want to use a customized banner, create an /etc/issue.net or /etc/issue file. The telnetd daemon reads the file that exists and writes its contents over a new telnet connection prior to starting the login dialog. If both files exist, only the /etc/issue.net file is used. CAUTIONS
Some telnet commands are only partially implemented. Because of bugs in the original 4.2BSD telnet(1), telnetd performs some dubious protocol exchanges to try to discover if the remote client is, in fact, a 4.2BSD telnet(1). FILES
Specifies the command path. Specifies the path name for the network issue identification file. Specifies the path name for the issue identification file. RELATED INFORMATION
Commands: telnet(1). Files: iptos(4), issue(4), issue.net(4). delim off telnetd(8)