telnet: Unable to connect to remote host: Connection refused

[Sanjay Shinde]

Hi Guys,
Follwing is error message while trying to

--------
telnet Trying...
telnet: Unable to connect to remote host: Connection refused
--------
but I can able to ping that server, as this is remote server, I could not do more, but I can instrct site Engineer by phone.

Also reboot server, still same error message,
what could be possible problems ?

Thanks in advance,
Sanjay

[Michael Tully]

Hi,

Make sure that your NIC and the switch are configured the same, i.e. the duplexing has a mis-match

# lanadmin -x 0
or
# lanadmin -x lan0

You change this to 100 Full-duplex by doing this:

# lanadmin -X 100FD 0

Can you telnet to another server from your console?

Michael

[Mark Fenton]

Sanjay,

Ping establishes that the remote system can communicate with yours so a lan problem is probably not the issue.

1) Firewall? Because Berkley R-tools are inherantly unsecure, most firewall configurations block them.
2) Services simply not enabled/installed? Many Linux distributions disable telnet and the other r-tools by default (indeed, RedHat has just about everything turned off, out of the box) and these must be specifically enabled.
[ have the engineer on the other end look at /etc/xinetd.d files for the services you want to use ]
3) PAM settings not allowing the connection?
4) /etc/securetty limits remote logins also -- check out that file too.

HTH
Mark

[Mark Fenton]

Sanjay -- oops! I thought I was in the Linux forum and my remarks were more apropriate for that context.

Still, I don't think LAN is the issue, probably more to do with firewall and other settings.

/var/adm/inetd.sec is another file to have your engineer look at to ensure that your address is allowed to telnet/rsh.

hth
Mark

[Ian Kidd_1]

the /usr/sbin/inetd process on the remote server may have dropped. You would still be able to ping it, but telnet wouldn't be possible.

Hopefully you have have remote console access?

[Ian Kidd_1]

Maybe if I read your WHOLE message, I'd be more help. have your onsite engineer issue ps -ef | grep inetd.

Is it there?

If it is, you might be dealing with a router issue. Can your onsite engineer telnet to you?

[Sanjay Shinde]

Thanks for reply guys,
when onsite engineer change with new IP address of that LAN interface I can able to telnet, so all services working fine, but with old IP address (when revert back) not able to telnet, Actually Remote site Network Admin people has changed some Fire Wall configuration and blocked telnet service from other location, so Remote site network guys are working on this issue.

Once again thank Michael, Mark, Ian.

Sanjay

[John Dvorchak]

This is a classic case of LAN/Network engineers trying config settings on routers and not knowing what they are doing. I'll bet that the Network engineers have the router closest to that server set to never dump the ARP cache. A lot of new/inexperienced network guys think that letting the default ARP cache retention of 180 seconds is a bad idea so they set it to never dump the cache thinking that it will cut down on network traffic. The hint was that when you change the IP address it worked. That tells me that either the router on that end is still looking for the MAC address of what ever system had that IP Address or you could have a duplicate IP address. Which would let a ping work but not a service, especially if that duplicate address system is something that doesn't support telnet, like Windows.