[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Server not reachable via GUI after putting it behind a Loadbalancer
- Subject: Re: [cobalt-users] Server not reachable via GUI after putting it behind a Loadbalancer
- From: David Thurman <dthurman@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed Apr 24 16:48:37 2002
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
on 4-24-02 10:58 AM, Torsten Ewald / ISC Berlin HCC at
te@xxxxxxxxxxxxxxxxxxx was reported to have made a statement that said this:
> Hi folks,
> I have a strange problem. We want to host some webservers (RaQ4's) in one
> dedicated network. For a better performance we want to implement an Load
> Balancer into this network, which uses NAT to translate the IP's to private
> IP's.
> On the servers we used private IP's (192.168 .....), so when someone wants
> to connect to the machine via the public ip (for example 123.456.789) the IP
> is translated to 192.168.0.1 and vice versa.
> It seems, that there are no problems first (FTP and SSH works super) but
> when I try to connect the Server via a browser, I got no answer, just the
> default Browser Screen, that the server hadn't been found.
> Can someone help me, where to edit some conf'S that the machine is Serving
> the HTTP Requests ?
> We use no accesslists on the Loadbalancer and ussing telnet on the public ip
> port 80 gives fine results.
>
> Best regards
> Torsten Ewald
Just a thought, but what about port 81 an the SSL port for the GUI admin?
--
Thank you,
David E Thurman
The Web Presence Group
309.676.5688
dthurman@xxxxxxxxxxxxxxxxxxxx
http://www.webpresencegroup.net