I'd a search on HyperV NLB - there's a bunch of stuff you have to do to make this work.
Thanks, Brian Desmond [email protected]<mailto:[email protected]> w - 312.625.1438 | c - 312.731.3132 From: [email protected] [mailto:[email protected]] On Behalf Of James Rankin Sent: Friday, February 7, 2014 2:51 AM To: [email protected] Subject: Re: [NTSysADM] NLB on Server 2012 R2 It's on Hyper-V, I believe. I read that you need two NICs for unicast, so I've got the server admins to add a second NIC which I am now going to configure. I was stopping IIS and expecting it to failover, but that appears to be out of scope for NLB, as far as I can tell from this discourse. I will try disabling it in NLB Manager, as rebooting brings it back too quickly to tell if it's failed over or not, and I don't have access to Hyper-V to shut it down. I am assuming that although it can't do intelligent failover, it does do intelligent load balancing - i.e. it will route connections to the server with the least load? Cheers, JR On 6 February 2014 23:54, Ken Schaefer <[email protected]<mailto:[email protected]>> wrote: How are you "stopping the server"? If you're turning it off, or disabling in NLB manager, and everything stops working, then I don't think your cluster's working properly. Everything's just going to node 1 Are you running this in VMs? If so, you may need to do some extra steps to get multicast to work. Cheers Ken From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of James Rankin Sent: Friday, 7 February 2014 1:54 AM To: [email protected]<mailto:[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 -- James Rankin --------------------- RCL - Senior Technical Consultant (ACA, CCA, MCTS) | The Virtualization Practice Analyst - Desktop Virtualization http://appsensebigot.blogspot.co.uk
