Sponsored Content
Full Discussion: Listen given port
Operating Systems Solaris Listen given port Post 302686697 by rbatte1 on Wednesday 15th of August 2012 09:09:12 AM
Old 08-15-2012
You can adjust /etc/services and /etc/inetd.conf to also offer telnet on the port. Then you can open telnet from a client to that port are see if it open.

If you add a line to /etc/services such as:-
Code:
mytelnet 1099/tcp

and add a line to /etc/inetd.conf such as:-
Code:
mytelnet  stream  tcp6    nowait  root    /usr/sbin/telnetd      telnetd -a

... and then signal inetd to re-read it's config, that should be enough. Check you man page for inetd or inetd.conf. It will probably suggest you send a kill -2, kill -HUP or something similar to the inetd process. Check you man page before issuing either of these in case they cause inetd to terminate and drop all network connections/services leaving just the console to get back in.

Then, from an appropriate client (suitable source address to test your firewall) issue:-
Code:
telnet put.ip.address.here  1099

You should get an instant response. If you get a login prompt, then on the server, you can run:-
Code:
netstat -na|grep 1099

... and see what is connected.


I hope that this helps.

Robin
Liverpool/Blackburn
UK
This User Gave Thanks to rbatte1 For This Post:
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

listen to ports...

Hi all, How can I log all requests on ports for programs like ftp, telnet, rsh, xdmcp etc... I want to see if anyone uses these programs/protocols and how often. Is it difficult to setup a log for these ports and listen on all requests? /combat (4 Replies)
Discussion started by: tonlu
4 Replies

2. UNIX for Advanced & Expert Users

Let NTP listen only on one interface

Hallo, I have a machine which serves as NTP server. This machine has more (3) Network interfaces (+ loopback). By default NTP "binds" itself to all available interfaces, i.e. it listens on port 123 on all interfaces: netstat -an|grep 123 udp 0 0 127.0.0.1.123 *.* udp... (0 Replies)
Discussion started by: one71
0 Replies

3. Shell Programming and Scripting

Program to listen a port

I need to launch a script as soon as a file comes via a specified port on my system from another system. Program should work as a dameon and should invoke only when port start/stop accepting file. Any idea how to program/script it... Please no suggestions for cron. Thanks in advance. (1 Reply)
Discussion started by: sumitwa
1 Replies

4. Solaris

socket in listen state disappears/closes automatically

Hi, I am using solaris 10. I have opened a socket connection using java in solaris 10 operating system, the port went to LISTEN state and able to create new socket connection and the new connections went to ESTABLISHED state. If I issue the command "netstat -an | grep <<portnumber>>", I... (10 Replies)
Discussion started by: kumar3k
10 Replies

5. IP Networking

Configure squid to listen on any IP address with port 80

Hi, I am trying to configure a transparent squid cache. When I try to use the below option in squid.conf, squid listens on port 80 only for the IP address configured on the system's interface. http_port 80 transparent But I want squid to accept connections for any IP address on port 80.... (3 Replies)
Discussion started by: Learner32
3 Replies

6. HP-UX

What is the Listen Address of my process ?

Hi, We cant set the listen address of my java process to the IP address or any of the DNS names listen in the hosts file of the server. We can access the resources of the pid in the web browser through http://<IP / DNS>:port/console Based on the pid, how can we find what is the listen... (6 Replies)
Discussion started by: mohtashims
6 Replies

7. Solaris

How to find port number wwn of particular port on dual port HBA,?

please find the below o/p for your reference bash-3.00# fcinfo hba-port HBA Port WWN: 21000024ff295a34 OS Device Name: /dev/cfg/c2 Manufacturer: QLogic Corp. Model: 375-3356-02 Firmware Version: 05.03.02 FCode/BIOS Version: BIOS: 2.02; fcode: 2.01;... (3 Replies)
Discussion started by: sb200
3 Replies
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)
All times are GMT -4. The time now is 09:35 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy