telnet to port other than 23 1

[mariab4]

I need to set up a telnet session on port 3700. I've enter this in the /etc/services file and restarted the inetd daemon. I cannot telnet to it nor ping it. What am I missing here?

 

[PHV]

On the server, can you do

 telnet localhost 3700

?
Anyway, if client side you can't ping the server you have network problem like firewall, route, ...

Hope This Help
PH.

 

[mariab4]

well now here's the stupid question. I get a "connected" just like I do from a foreign host but I guess I'm expecting a login prompt or something. What AM I looking for?

 

[PHV]

Tested on my box (SCO OSR 5.0.7).
/etc/services:

mytelnet         3700/tcp
mytelnet         3700/udp

/etc/inetd.conf:

mytelnet stream tcp nowait NOLUID /etc/telnetd telnetd

After sending a SIGHUP signal to inetd, that's worked.

Hope This Help
PH.

 

[mariab4]

Well...I have an AIX production box and a Linux crash-and-burn test box both of which I've tried what you did. I even rebooted the Linux box. When I edit the inetd files I yanked-and-put the telnet line and renamed it to the service. Still nothing.

I was instructed to edit the /etc/services file to set up port 3700 for tcp for DB2. I followed the instructions which were to add the line to /etc/services and refresh the inetd daemon. The DBA's can't get to that port and are asking me if I can telnet to it. If the only thing I was supposed to do was add line 3700 to /etc/services and bounce the daemon, that's not setting it up for telnet.

 

[aixmurderer]

Telnetting to port 3700 (the DB2 listener in your case) will only give you a partial connection, not a telnet login prompt. Typically you will see a message that you can use <CTRL> ] to escape.

If you get this far then it means that the DB2 listener is &quot;listening&quot; correctly on the port, so your bit is done.

Using telnet in this way is a sure way of determining if your services and inetd.conf files are set up correctly and connections are possible. If a DB2 client connection doesn't work correctly the it possibly points to an incorrect config line in the inetd.conf file.

IBM Certified Confused - MQSeries
IBM Certified Flabbergasted - AIX 5 pSeries System Administration
MS Certified Windblows Rebooter