1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

Load Balance Problem

Discussion in 'Windows Home Server' started by brian_altman@hotmail.com, Apr 16, 2009.

  1. I am setting up Network Load Balancing and everything appears to be
    working except I am having one issue. I have 2 hosts set up for load
    balancing and IIS set up on each. I tried various client machines and
    verified that they were alternating which host they were connecting
    to.
    I then had a client connect to a web page on host 1, and then stopped
    host 1 in NLB Manager. What I expected to happen was that the client
    would then connect to host 2 for web requests. What I found though is
    that it must still be trying to connect to host 1 (now offline)
    because I was getting a page not found error.

    Is this the downfall of using NLB, that a client that is currently
    connected to a host that fails will still try to connect to the failed
    host?
     
  2. Hello Brian,

    Your post will be well suited for the clustering forum
    microsoft.public.windows.server.clustering,

    --
    Isaac Oben [MCTIP:EA, MCSE]
    <brian_altman@hotmail.com> wrote in message
    news:8a27e587-6056-43d9-8c6d-f04e04426ffc@e23g2000vbe.googlegroups.com...
    >I am setting up Network Load Balancing and everything appears to be
    > working except I am having one issue. I have 2 hosts set up for load
    > balancing and IIS set up on each. I tried various client machines and
    > verified that they were alternating which host they were connecting
    > to.
    > I then had a client connect to a web page on host 1, and then stopped
    > host 1 in NLB Manager. What I expected to happen was that the client
    > would then connect to host 2 for web requests. What I found though is
    > that it must still be trying to connect to host 1 (now offline)
    > because I was getting a page not found error.
    >
    > Is this the downfall of using NLB, that a client that is currently
    > connected to a host that fails will still try to connect to the failed
    > host?
    >
     

Share This Page