Tyler McLaughlin
2007-08-29 20:18:02 UTC
I'm having an issue with my NLB hosted web application. The application
works correcly on both web servers, whether accessing it locally from the IIS
servers themselves, or via a client computer. It worked sporadically (a few
times) when trying to access it from the NLB hostname. It no longer works.
Now when attempting to access the NLB URL, I get one of the two following
errors:
HTTP 400 Bad Request
This error (HTTP 400 Bad Request) means that Internet Explorer was able to
connect to the web server, but the webpage could not be found because of a
problem with the address.
OR
Internet Explorer cannot display the webpage
This problem can be caused by a variety of issues, including:
Internet connectivity has been lost.
The website is temporarily unavailable.
The Domain Name Server (DNS) is not reachable.
The Domain Name Server (DNS) does not have a listing for the website's
domain.
If this is an HTTPS (secure) address, click Tools, click Internet Options,
click Advanced, and check to be sure the SSL and TLS protocols are enabled
under the security section.
Configuration: (this is not accessed externally. Intranet domain
application access only)
----------------------------------------------------------
\\NODE1.INTERNAL.EXTERNAL.COM
ETH0 = PUBLIC 192.168.1.1
NLB = VIRTUAL 192.168.1.3
ETH1 = PRIVATE 1.1.1.1
---------------------------------------------------------
\\NODE2.INTERNAL.EXTERNAL.COM
ETH0 = PUBLIC 192.168.1.2
NLB = VIRTUAL 192.168.1.3
ETH1 = PRIVATE 1.1.1.2
---------------------------------------------------------
\\NLB.INTERNAL.EXTERNAL.COM (Static (A) Record exists @ 192.168.1.3)
---------------------------------------------------------
NLB SETUP
OPERATION MODE = MULTICAST (ARP entry exists on router)
PORT RULES = PORT 80, FILTERING = MULTIPLE HOST, SINLGE AFFINITY, EQUAL
(application is session based)
---------------------------------------------------------
I’ve read the following KB Article http://support.microsoft.com/kb/929650
and followed the applicable scenario rule:
Scenario 3: Access an IIS application in a clustered or load-balanced
environment
When you run IIS in a clustered environment or in a load-balanced
environment, you access applications by using the cluster name instead of by
using a node name. This scenario includes network load balancing. In cluster
technology, a node refers to one computer that is a member of the cluster. To
use Kerberos as the authentication protocol in this scenario, the application
pool identity on each IIS node must be configured to use the same domain user
account. To configure each IIS node to use the same domain user account, use
the following command:
Setspn –A HTTP/CLUSTER_NAME domain\username
---------------------------------------------------------------------------
What is wrong?
works correcly on both web servers, whether accessing it locally from the IIS
servers themselves, or via a client computer. It worked sporadically (a few
times) when trying to access it from the NLB hostname. It no longer works.
Now when attempting to access the NLB URL, I get one of the two following
errors:
HTTP 400 Bad Request
This error (HTTP 400 Bad Request) means that Internet Explorer was able to
connect to the web server, but the webpage could not be found because of a
problem with the address.
OR
Internet Explorer cannot display the webpage
This problem can be caused by a variety of issues, including:
Internet connectivity has been lost.
The website is temporarily unavailable.
The Domain Name Server (DNS) is not reachable.
The Domain Name Server (DNS) does not have a listing for the website's
domain.
If this is an HTTPS (secure) address, click Tools, click Internet Options,
click Advanced, and check to be sure the SSL and TLS protocols are enabled
under the security section.
Configuration: (this is not accessed externally. Intranet domain
application access only)
----------------------------------------------------------
\\NODE1.INTERNAL.EXTERNAL.COM
ETH0 = PUBLIC 192.168.1.1
NLB = VIRTUAL 192.168.1.3
ETH1 = PRIVATE 1.1.1.1
---------------------------------------------------------
\\NODE2.INTERNAL.EXTERNAL.COM
ETH0 = PUBLIC 192.168.1.2
NLB = VIRTUAL 192.168.1.3
ETH1 = PRIVATE 1.1.1.2
---------------------------------------------------------
\\NLB.INTERNAL.EXTERNAL.COM (Static (A) Record exists @ 192.168.1.3)
---------------------------------------------------------
NLB SETUP
OPERATION MODE = MULTICAST (ARP entry exists on router)
PORT RULES = PORT 80, FILTERING = MULTIPLE HOST, SINLGE AFFINITY, EQUAL
(application is session based)
---------------------------------------------------------
I’ve read the following KB Article http://support.microsoft.com/kb/929650
and followed the applicable scenario rule:
Scenario 3: Access an IIS application in a clustered or load-balanced
environment
When you run IIS in a clustered environment or in a load-balanced
environment, you access applications by using the cluster name instead of by
using a node name. This scenario includes network load balancing. In cluster
technology, a node refers to one computer that is a member of the cluster. To
use Kerberos as the authentication protocol in this scenario, the application
pool identity on each IIS node must be configured to use the same domain user
account. To configure each IIS node to use the same domain user account, use
the following command:
Setspn –A HTTP/CLUSTER_NAME domain\username
---------------------------------------------------------------------------
What is wrong?