Re: NLB Web Application Server: Access Issues
- From: "Mathieu CHATEAU" <gollum123@xxxxxxx>
- Date: Thu, 6 Sep 2007 16:35:02 +0200
Hello,
dumb question: is the IIS using host header ? if so, does it contains the FQDN or shortname or both ?
Do you enforce ssl connection ?
Can you create an html test page to be sure it's not the application that is rejecting the connection ?
telnet NLB.INTERNAL.EXTERNAL.COM 80 works ? if so:
GET / HTTP/1.0
[two return carriage]
--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com
"Tyler McLaughlin" <TylerMcLaughlin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:DCD1CD19-435F-484E-B032-FACFFB01EB39@xxxxxxxxxxxxxxxx
Do you have an answer to the question...?
thx -
- Tyler
"Rodney R. Fournier [MVP]" wrote:
I didn't answer your question when I replied earlier :)
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Tyler McLaughlin" <TylerMcLaughlin@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:6476E35D-A606-4F1F-897E-3E8BFFEA0602@xxxxxxxxxxxxxxxx
> 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?
>
.
- References:
- Re: NLB Web Application Server: Access Issues
- From: Tyler McLaughlin
- Re: NLB Web Application Server: Access Issues
- Prev by Date: Terminal Server Session Directory
- Next by Date: Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
- Previous by thread: Re: NLB Web Application Server: Access Issues
- Next by thread: Terminal Server Session Directory
- Index(es):
Relevant Pages
|
