Re: Inconsistent behavior with NLB
- From: "Rodney R. Fournier [MVP]" <rod@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 30 Aug 2007 09:45:44 -0500
I know now as much about the topic as I did that day in June :). I fully
understand everything you doing and what you are trying to do, why it does
not work is beyond me though.
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:9632D9C9-575A-4AFD-9A40-21F8AD4E259A@xxxxxxxxxxxxxxxx
"both DNS name as well as with virtual IP address". I think what Bill was
saying is that it worked both ways... via IP and or DNS resolution.
I'm having this same issue with my NLB hosted web application.
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?
- Tyler
------------------------------
"Rodney R. Fournier" wrote:
What do you mean both DNS names? The web site should have one name in
DNS.
Users should not be going to the node names for IIS either.
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
"Billu" <Billu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B3A6ADE7-0BDD-4E40-A3EA-5FDDC7C4B5BF@xxxxxxxxxxxxxxxx
I have configured Windows 2003 Network Load Balancing for my IIS
application
(intranet). One Cluster Virtual IP address and two physical nodes. In
each
node there is one Network adapter. The NLB cluster configured with
multi
cast
and filtering is set to one. There are no port restrictions. The
Cluster
IP
has also a hostname configured in DNS.
Requests are reaching to my IISs (on both servers) fine from some of
the
PCs
in the network with both DNS name as well as with virtual IP address.
The issue is from other PCs request is not going. Also from some PCs
behavior is not consistent (i.e this will work some time good and
suddenly
will not work).
Any idea why this is working.
Thanks,
Billu.
.
- References:
- Re: Inconsistent behavior with NLB
- From: Tyler McLaughlin
- Re: Inconsistent behavior with NLB
- Prev by Date: Re: Cluster Ressource not Fail
- Next by Date: Re: NLB Web Application Server: Access Issues
- Previous by thread: Re: Inconsistent behavior with NLB
- Next by thread: NLB Web Application Server: Access Issues
- Index(es):
Relevant Pages
|
