telnet

[arun_k]

Hi All

I got a strange problem. One of my clients server hp-ux 11.00. I have telnet restriction from ip address using inetd.sec file. All the clients from different locations are able to telnet to my server except one. They are getting host refused to connect.

They can ping my server, their ip range is there in telnet allow part of inetd.sec.I tried even removing inetdsec still not connected.

Then when I asked them to telnet alternate ip of my server they are able to connect to the server. Network people say no change in config and server admin also said not changed any file.

Can any one say what could be the reason. Is there any other file we can specify which ip address the client should connect.

Thanks in advance
arun

[IT_2007]

Few things came to mind. After removing entry from inetd.sec, did you re-read inetd and restarted?

inetd -c

ps -ef |grep inetd

kill -HUP

Also check from client, can you resolve your hostname with corect IP address?

[arun_k]

hi

I have even rebooted the server. Still not worked.

Is it really required to resolve the name to get telnet work. Coz we are using IP to telnet from router.


thanks
arun

[Jim Keeble]

Hi Arun,

I don't think the inetd.sec on the server is the problem. The error for that should be "connection reset by peer".

If the error your clients see is "connection refused", then the device they are reaching doesn't have a listener for port 23. Since it does work going to your server's alternate IP, I think it's possible that another device (one without a telnetd service on port 23) is using your server's IP address.

You might try using traceroute from a failing site and compare it to traceroute from a working site to see if they are arriving at the same place.

Also, try running "inetd -b" on your server to enable very verbose logging. If my theory is correct, you won't even see anything in the syslog.log file about a request from the failing client, because the request is never reaching your server.

Hope this helps.