The machine refuses the connection when called as virtual IP

[Enrico Venturi]

Hi all,
one node of my HP MC/SG cluster doesn't work properly anymore!
When I telnet on it by using the physical IP, it's OK!
When I ping it by using the physical IP, it's OK!
When I ping it by using the virtual IP it's OK!
When I telnet on it by using the virtual IP the answer is: telnet: Unable to connect to remote host: Connection refused.

What is the reason???

Thanks a lot!
Enrico

[Claude Fortin]

Is your virtual IP is on the same network?

[Enrico Venturi]

Yes,
the really strange topic is that this cluster properly worked since a long time (1 year) ....

the physical address is 139.54.19.17; the virtual IP is 139.54.19.34

I kindly remind that *the ping works fine*

[Sanjay_6]

Hi,

Your virtual ip may be sitting behind a firewall. If there is a firewall it may allow ping but will block telnet is not allowed.

Hope this helps.

Regds

[Enrico Venturi]

Unfortunately there isn't any firewall .......

[Christopher Caldwell · Accepted solution]

-Try to telnet to the virtual on host A from host A - see what you get.

-Try removing the virtual IP (cmmodnet or ifconfig) and re-adding it.

-Look at the arp table on hosts on the same network (routers and servers) to verify that an arp entry maps to the virtual IP

router (cisco) > show arp

server (hp) > arp -a

Let us know your results.

[Steven Gillard_2]

You will get the connection refused message if you try to telnet to a machine that does not run the telnet server, for example an NT system or if inetd was down. Given that the "real" ip responds to telnet its very strange that the "virtual" ip doesn't. So I have to ask - are you sure that the virtual IP definitely refers to the same system you are able to telnet to?

What do the following report (you'll need to run these on a machine on the same subnet):

# arp
# arp

Are the physical addresses returned the same?

Regards,
Steve

[Mark van Hassel]

Hi,

Did you create/change /var/adm/inetd.sec ?

Are you sure that inetd is running ?

[George_Dodds]

Where are you telneting from is it a pc?
If it is from an terminal emulation s/w, the problem could be that it has not closed an old telnet connection properly from the emulation s/w itself.

I've had this once or twice, just restart the t/e software usually does the trick.

Regs

George

[Enrico Venturi]

On a node being able to telnet on the physical IP but not on the virtual IP:

#arp phy_IP --> OK (a result is provided)
#arp virt_IP --> -- no entry

concerning another MC/SG node on the same network:

#arp phy_IP_1 --> OK (a result is provided)
#arp virt_IP_1 --> -- no entry

but in this second case the telnet on the virt_IP_1 works fine!!

It seems to NOT be any relations between the arp and the capability to telnet on a virtual IP