Re: Load balancing strange issue

I tried it several times from the Machine that has this particular problem
(OWA1)
And a couple of times from the other machine (OWA2) that is allready member
(and the only member) of the NLB.
Remote control is not turned on, so I did not try it from an external machine.
I often made a NLB cluster but never had this much problems configuring it.
Is there maybe an issue with HP and/or Broadcom NetXtreme Gigabit Ethernet
NIC's?
Or maybe a windows update / hotfix or another program that is known to cause
problems with NLB?
I updated the NIC drivers to the newest version today on both servers.
But unfortunately it still doesn't work.
I'm out of suggestions.... I hope you are not :-)

Greets


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


"Rodney R. Fournier [MVP]" wrote:

> Are you trying from one of the nodes or a client/external machine? NLB has
> issues using another NLBed node.
>
> 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:4EF675FF-D09F-41C7-BF56-14CAE3F2BD0F@xxxxxxxxxxxxxxxx
> > 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: Windows 2003 Network Load Balancing Problem
    ... Sadly my servers websites were configured with specific IPs and host ... I find it very strange why the NLB driver can receive on a virtual IP ... he set his IIS website to use ALL UNASSIGNED addresses rather than ... specifically pointing it at the single virtual cluster address. ...
    (microsoft.public.windows.server.clustering)
  • 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)
  • 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)