Here's a wild guess: when an app opens a port, it gives two pieces of info: the port number and the IP address. The app then listens to that port only on that IP address. I suspect that the telnet daemon is listening on the host's IP address (192.x.x.2), and not on 0.0.0.0 (which means listen on all IP addresses) or 127.0.0.1.
Its my Java application which has webservice port 9922 deployed on Websphere 6.1
I used to check whether the port is accepting or not by telnet to tat port. In my deployed application config file i mentioned localhost as agenthostname and webserviceport as 9922 so all calls goes like localhost:9922/blah format.
I'm using localhost instead of hostname because if i use localhost then i can copy paste the same config file to different machines in case of cluster rnv. once config file gets generated.
it was a regular practice for us till RHEL 4.x.x but i dont know why the same is not working in ver.5.
My question is if I'm getting the port and hostname listening then why i cant connect through localhost and the same port number.(min localhost should redirect to actual hostname as this all was working in previous RHEL versions)
Now the 2 work arounds are: ( Both works but i dont recomend): 1st one :I have to give hostname instead of localhost in my Apps config file. (Machine dependent config file cant do a copy paste to all machines) 2nd one: I have to edit the etc/hosts file and put hostname entry just before the localhost entry like
1. Use netstat -ln to determine whether the port is accessible. Normally localhost references would route through the loopback device.
2. Check iptables to make sure it isn't blocking. Out of the box, the stock RHEL iptables firewall setup should allow unlimited access from localhost, but if someone deleted that rule, you'd have a problem.
Customer surveys are for companies who didn't pay proper attention to begin with.