Removing one of the host is just what I did to discover that it's the NLB
cluster setup interfering with RIP. I had no intention of breaking the
cluster. In fact, I have already add the host back. What I really wish to
know if it's a known situation (RIP and NLB), or could it have been something
I did wrong while setting things up.
Dan
"Todd J Heron" wrote:
> I don't understand the point of un-joining the NLB cluster and leaving it
> like that after you purposefully joined it in the first place.
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>
> "Dan" <(E-Mail Removed)> wrote in message
> news:F33186D3-BAE9-46F5-B5CE-(E-Mail Removed)...
> Recently, I was playing around with a single NIC multicast NLB cluster. So
> far, the cluster has only 2 hosts. It was intended to service VPN access.
> The
> cluster is behind NAT and use different off-subnet IP address ranges for
> each
> host in the cluster, so the NAT device needs to be aware of the routing for
> the off-subnet ranges. The problem I am experiencing is that only one of the
> two hosts can bhave the NAT device as RIP neighbors. If I remove one of the
> host from the NLB cluster, then both machines will have the NAT device as
> RIP
> neighbors.
>
> Is it caused by the current setup I have? Is there anyway to work around it?
>
>
> Thanks.
>
> Dan
>
>
|