Actually no, I was just stopping the web site. Is NLB that dumb, or does it depend on the port rules? I'm used to NetScalers and F5s, so maybe I'm expecting too much
Sent from my (new!) BlackBerry, which may make me an antiques dealer, but it's reliable as hell for email delivery :-) -----Original Message----- From: Miller Bonnie L. <[email protected]> Sender: [email protected]: Thu, 6 Feb 2014 18:23:09 To: [email protected]<[email protected]> Reply-to: [email protected] Subject: RE: [NTSysADM] NLB on Server 2012 R2 This may be a silly question, but are you also stopping that cluster node using the NLB manager MMC? If you don't, then just stopping IIS doesn't tell the cluster that the server is down-it's not that smart. It also will try to reconnect you to the same node, unless one is down, so I would expect that behavior. I would be more concerned about your comment that shutting down server1 stops all of the traffic-at that point, it should recognize the node is offline and send people over to server2. IME, with a web app, you do generally have to restart your session on the client (depending on how it's written). -Bonnie From: [email protected] [mailto:[email protected]] On Behalf Of James Rankin Sent: Thursday, February 06, 2014 6:53 AM To: [email protected] Subject: [NTSysADM] NLB on Server 2012 R2 Anyone had any luck with configuring this? Must admit, I am an NLB-noob, so I've probably done something wrong.... Trying to configure an NLB cluster for an IIS-based app on Server 2012 R2. Got two servers with the IIS app, Server1 and Server2 Configured an NLB cluster to load balance these called Cluster1 When both servers are up, everything seems to work fine. However, when I stop IIS on Server1, connecting to the Cluster1 DNS name just returns "page cannot be found". It's as if it always tries to connect to the original one it connected to. I can connect to http://Server1/app and http://Server2/app just fine. I can connect to http://Cluster1/app fine as long as both servers are up. If I shut down Server1, I can no longer connect to http://Cluster1/app What obvious thing should I be checking? There's not an awful lot of options to try with NLB - switching to Multicast seems to stop it working altogether :-( I've also messed with various bits of IIS but given that both servers accept connections I don't really think it's related to that. Give me a NetScaler any day over NLB! TIA, JRR -- James Rankin --------------------- RCL - Senior Technical Consultant (ACA, CCA, MCTS) | The Virtualization Practice Analyst - Desktop Virtualization http://appsensebigot.blogspot.co.uk
