Re: Load balancing strange issue

Hi Rod, thanks for the quick response.

Yes NLB does converge. When adding the server to the NLB cluster I see that
the server having problems is converged. But after that, it can not connect
to the other member.
There are no errors or warnings in the eventlogs only information about the
configuration changes:

Configuration update 12 completed with status 0x0 on adapter
{13EF3CB7-705B-417B-B5D7-C2A5860B49D5}. Information log contains:
Processing update 12 from "NLB Manager on OWA1.domain.com"
Starting update...
Going to bind NLB...
Bind operation succeeded.
Cluster configuration stabilized.
Going to modify cluster configuration...
Modification succeeded.
Going to modify the IP address list...
The IP addresses list modified successfully.
Update completed successfully

Both the servers have the same Certificate installed. Both servers work fine
if I connect to them individually.

Thanks


--
___________________
MCSA 2003
MCSE 2000 / 2003
MCSA Messaging 2003
MCSE Messaging 2000 / 2003
___________________


"Rodney R. Fournier [MVP]" wrote:

> Does NLB converge? Any messages in either servers event log? Are the port
> rules the same on each? Are you using SSL? Is the cert published on both
> servers?
>
> Cheers,
>
> Rod
>
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://www.msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
>
>
> "Bikkelbink" <Bikkelbink@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:56A9581E-6DAB-474E-B74E-C7860FEE6A2B@xxxxxxxxxxxxxxxx
> > Hi everybody,
> >
> >
> > At this moment I'm trying to set up a load balanced OWA solution.
> > The back-end servers are set up as a cluster and that all works fine.
> > When I try to set up the front-end servers, all works fine till I add a
> > specific server.
> > The situation:
> >
> > I got 2 exact the same HP servers.
> > The both have 2 NIC's and exactly the same OS and Exchange installations.
> > At this moment only OWA1 is beeing used for all webmail. When I configure
> > NLB on OWA2 everything works fine. When I add OWA1 to the NLB all goes
> > wrong.
> > On OWA1 I can't ping a single server after adding it to the NLB.
> > The NLB is set up in Unicast mode.
> > Does anybody has a suggestion what this problem might be?
> > Thanks in advance.
> >
> >
> > --
> > ___________________
> > MCSA 2003
> > MCSE 2000 / 2003
> > MCSA Messaging 2003
> > MCSE Messaging 2000 / 2003
> > ___________________
>
>
>
.

Relevant Pages

  • Re: Load Balanced TS Servers and Unicast Flooding
    ... Remove each on of your tse servers from the cluster, ... Start adding them back to the NLB Cluster. ... > NICs. ...
    (microsoft.public.windows.terminal_services)
  • Unable to add second node with NLB
    ... >I'm running two Win2K3 SUS servers and I wish to cluster ... them using NLB. ... issue with the communication between the two servers. ... NLB configuration, I have verified that each machine is ...
    (microsoft.public.windows.server.clustering)
  • Re: Clustering Exchange
    ... As your application is Exchange and you have A/A/P configuration, ... actively block any node hosting two Exchange virtual servers. ... are you done creating the three node cluster? ...
    (microsoft.public.windows.server.clustering)
  • NLB & separate RDP connection for network adapters
    ... We have two terminal servers configured as members of a NLB cluster. ... one for management and one bound to NLB. ...
    (microsoft.public.windows.server.clustering)
  • NLB & separate RDP connections for network adapters
    ... We have two terminal servers configured as members of a NLB cluster. ... one for management and one bound to NLB. ...
    (microsoft.public.windows.terminal_services)
Loading