Sponsored Content
Full Discussion: fail to telnet localhost 106
Operating Systems Linux Ubuntu fail to telnet localhost 106 Post 302151605 by porter on Sunday 16th of December 2007 02:46:22 PM
Old 12-16-2007
Quote:
Originally Posted by satimis
Code:
$ telnet localhost 106
Trying 127.0.0.1...
Connected to localhost.localdomain.
Escape character is '^]'.
Connection closed by foreign host.

Note that it said "Connection closed" not "Connection refused".

Does netstat say anyone is listening on 106?

Code:
netstat -an | grep LISTEN

 

3 More Discussions You Might Find Interesting

1. Linux

Telnet fail

Hi, I try to telnet to server: # telnet xx.xxx.1.72 1521 Trying xx.xxx.1.72... telnet: connect to address xx.xxx.1.72: Connection refused telnet: Unable to connect to remote host: Connection refused iptables is off: # service iptables status Firewall is stopped. # And I have edit... (4 Replies)
Discussion started by: mehrdad68
4 Replies

2. Shell Programming and Scripting

If Telnet fail abort other command..??

Hi Team, I my script i telent my node ip and after loging i run some commands...But some time login fail so i want to stop script at that time.. CONFIG_CHNG.sh printf 'Please Input Node ID : ' read node node="$node" #exec > node_log_$node.log 2>&1 #set -x >... (2 Replies)
Discussion started by: Ganesh Mankar
2 Replies

3. UNIX for Beginners Questions & Answers

Telnet failed to localhost.

Hi, I am trying telnet to localhost 514. But the connection is refusing. Port does not appear in netstat. IP table service is also off. (5 Replies)
Discussion started by: Nishit
5 Replies
dat_rsp_free(3DAT)				     Direct Access Transport Library Functions					dat_rsp_free(3DAT)

NAME
dat_rsp_free - destroy an instance of the Reserved Service Point SYNOPSIS
cc [ flag... ] file... -ldat [ library... ] #include <dat/udat.h> DAT_RETURN dat_rsp_free ( IN DAT_RSP_HANDLE rsp_handle ) PARAMETERS
rsp_handle Handle for an instance of the Reserved Service Point. DESCRIPTION
The dat_rsp_free() function destroys a specified instance of the Reserved Service Point. Any incoming Connection Requests for the Connection Qualifier on the destroyed Service Point was listening on are automatically rejected by the Provider with the return analogous to the no listening Service Point. The behavior of the Connection Requests in progress is undefined and left to an implementation, but it must be consistent. This means that either a Connection Requested Event was generated for the Event Dispatcher associated with the Service Point, including the creation of the Connection Request instance, or the Connection Request is rejected by the Provider without any local notification. This operation has no effect on previously generated Connection Request Event and Connection Request. The behavior of this operation with creation of a Service Point on the same Connection Qualifier at the same time is not defined. Consumers are advised to avoid this scenario. For the Reserved Service Point, the Consumer-provided Endpoint reverts to Consumer control. Consumers shall be aware that due to a race condition, this Reserved Service Point might have generated a Connection Request Event and passed the associated Endpoint to a Consumer in it. Use of the handle of the destroyed Service Point in any consequent operation fails. RETURN VALUES
DAT_SUCCESS The operation was successful. DAT_INVALID_HANDLE The rsp_handle parameter is invalid. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard: uDAPL, 1.1, 1.2 | +-----------------------------+-----------------------------+ |MT-Level |Unsafe | +-----------------------------+-----------------------------+ SEE ALSO
libdat(3LIB), attributes(5) SunOS 5.10 16 Jul 2004 dat_rsp_free(3DAT)
All times are GMT -4. The time now is 05:51 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy