Hello Geeks,

Consider the following architecture:

------------------------------------ (Firewall)
Web Server (IIS)
------------------------------------ (Firewall)
.NET Listener Process
------------------------------------ (Firewall)
Internal network

IIS is hosting my ASP.NET application, .NET Listener Process is a Windows
Service that is hosting pass through objects that simply call my COM+
components in the Internal network. I am using .NET remoting (TCP:3434) in
order to invoke .NET objects which are hosted by .NET Listener Process.

Everything in this architecture is clustered except the .NET Listener
Process machine, so it becomes a single point of failure for the
application.

Now my question is:
How to cluster .NET Listener Process so that if my ASP.NET application tries
to call .NET Process on MACHINE-A and if that machine is down, it gracefully
tries to call .NET Listener process on MACHINE-B (much like the way we can
change the web service connection url in the web service client proxy
class).

How to achieve the same with .NET objects exposed by custom .NET process
running on a separate box separated by a firewall???

Any thoughts? Please note that it is very urgent.

Thanks,
Hidden Desi