Hi all,
I posted this problem to the list several days ago but got no response.
Turns, out I've found a workaround to the problem - see transcript between
myself and colleague who had the problem below. Might be useful for some of
you working on clustered intranet/extranet scenarios with sites connecting
via proxies, not wishing to utilise DNS for whatever reasons.
*********************************
The proxy servers/hosts file was the key!!!
Problem: To connect to our web servers we are going through a proxy server.
We were connecting to the server from the client using IP addresses.
Everything works fine. However if the server dies and clustercats kicks in,
the secondary server will take control. However the browser will be told to
request information from the secondary server but instead of using its IP it
uses its machine name instead which cannot be resolved. The problem lies in
that the browser routes all requests to the proxy server which tries to
resolve address. Because we are using an IP address for the primary server
this is not a problem, but for the secondary we are using a machine name
which cannot be resolved so it fails.
Solution: stick the ip/machine name into the hosts file for the proxy
server.
We are trying this out on the customers site next week, so hopefully all
will go well.
Simple when you know how. Thanks for the help, bang on the nose..
Gary.
-----Original Message-----
From: Dave Wilson [mailto:[EMAIL PROTECTED]]
Sent: Thursday, May 25, 2000 12:35 PM
To: Gary Campbell
Subject: Re:
Gary,
Does the system have a fully qualified internet domain name
associated with
it? If so, then what you will need to do is use static IP's
for each of the
web servers, then have host entries in (Internet) DNS for
each machine.
e.g. you have two webservers in a cluster called
ww1.dartuk.com and
ww2.dartuk.com
When the client connects to ww1.dartuk.com and it fails,
they will be
redirected to ww2.dartuk.com. You cluster would be known as
dartuk.com. The
internet DNS zone file will handle the IP resolution (Use
Round Robin DNS to
add a second tier to your load balancing solution). As a
safeguard, you
could also, perhaps edit the hosts files found in
winnt/system32/drivers/etc/ folder on each of the proxy
servers at client
locations to include records pointing to each host of the
system similar to
this:
123.45.67.8 ww1.dartuk.com
123.45.67.9 ww2.dartuk.com
This helps because NT queries it's local hosts file before
carrying out DNS
queries.
Hope some of these ideas help you out, I'm just thinking out
loud and some
may be inapplicable to your specific setup.
Dave Wilson
Internet Technology Manager,
BizNet Solutions
<Allaire Premier Partner>
Co-Founder CFUG Ireland
http://www.cfug.ie
224, Lisburn Road
Belfast BT9 6GE
Tel: 02890 225 776
Fax: 02890 223 223
web: http://www.biznet-solutions.com
email: [EMAIL PROTECTED]
----- Original Message -----
From: Dave Wilson <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 24, 2000 3:09 PM
Subject: ClusterCats through proxy
> Hi all,
>
> I have a colleague who is looking advice for implementing ClusterCats
whilst
> behind a proxy server. They have no problems getting the failover to work,
> but what happens is that the failover resolves to an internal IP which is
> (obviously) inaccessible to the public users.
>
> Quote from colleague
> ***************************************************
> As described previously we are using two Enterprise servers, in a standard
> primary/secondary configuration. If the primary fails then the secondary
> will take over processing.
>
> Can you give me an indication if you help us with the following
>
> 1) I want to be able to connect a client to the server through a proxy
> server.
> 2) Then I want to "crash" the primary so that the secondary will take
> over processing
> 3) The secondary will proceed to server live pages as normal
>
> We have tried it over here, but we run into problems of DNS names. The
live
> customers site is worldwide so we were going to use IP address to connect
to
> the system. I know this is not the best solution but I'm open to another
> other ideas, which do not entail a re-configuration of the network. When
we
> connect to the primary with an IP - no problems, however on failure, we do
> get rolled over to the secondary but because the client is given a DNS
name
> it can't resolve it so it fails.
> ***************************************************
> MY colleague is also running SQL server database, so I have suggested that
> he simply move the two web servers to the public side of the proxy and
> maintain the db connection through the proxy via dedicated switch, hence
> protecting the data, which in essence is pretty much all that needs
> protecting.
>
>
> Does anyone have any better ideas for this?
>
> TIA
>
> Dave
>
> Dave Wilson
> Internet Technology Manager,
> BizNet Solutions
>
> <Allaire Premier Partner>
> Co-Founder CFUG Ireland
> http://www.cfug.ie
>
> 224, Lisburn Road
> Belfast BT9 6GE
>
> Tel: 02890 225 776
> Fax: 02890 223 223
> web: http://www.biznet-solutions.com
>
> email: [EMAIL PROTECTED]
>
> --------------------------------------------------------------------------
----
> Archives: http://www.eGroups.com/list/cf-talk
> To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
>
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
