Re: Connection refused

["Lorn Kay" <lorn_kay@xxxxxxxxxxx>]

Yes, you should be able to do this.

Check /etc/services for port 23 and /etc/inetd.conf for the sanity of the in.telnetd line, also check /etc/hosts.deny (or for that matter /etc/hosts.allow), maybe /etc/securetty does not have "pts" entries. (Can you telnet locally from the Real Server to the Real Server?)

--K

>From: "Justin M. Mahoney"

>Reply-To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx

>To:

>Subject: Connection refused

>Date: Tue, 9 Jan 2001 13:34:04 -0800

>

>Should I be able to telnet:80 to my virtual server locally on the load

>balancer? I always get an immediate "connection refused."

>I have a fresh 2.2.18 kernel with the following patch:

>

>Virtual Server patch for Linux 2.2.18 - Version 1.0.3 - December 30, 2000

>

>HTTP services are definitely running on the real servers. In fact, I can

>telnet:80 to them just fine from the load balancer.

>

>17$ipvsadm

>IP Virtual Server version 1.0.3 (size=4096)

>Prot LocalAddress:Port Scheduler Flags

> -> RemoteAddress:Port Forward Weight ActiveConn InActConn

>TCP vs0:www wlc

> -> rs1:www Masq 1000 0 0

> -> SAS03:www Masq 1000 0 0

>

>18$more /etc/hosts

>127.0.0.1 localhost.localdomain localhost

>

>63.192.253.170 vs0

>

>192.168.0.33 vs1

>

>192.168.0.34 lnx02.codeworksusa.com lnx02 localhost

>192.168.0.133 SAS03

>192.168.0.134 rs1

>192.168.0.135 rs2

>

>192.168.0.254 def_gateway

>

>19$ipchains -L -n

>Chain input (policy ACCEPT):

>Chain forward (policy ACCEPT):

>target prot opt source destination ports

>MASQ all ------ 192.168.0.133 0.0.0.0/0 n/a

>MASQ all ------ 192.168.0.134 0.0.0.0/0 n/a

>MASQ all ------ 192.168.0.135 0.0.0.0/0 n/a

>Chain output (policy ACCEPT):

>

>Thanks for any help!

>Justin

>

>

>

> Click here to get your FREE card at www peopleiknow.com

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

>

---

Get your FREE download of MSN Explorer at http://explorer.msn.com