quinta-feira, 24 de maio de 2012 21:08
Okay, 2008 clustering is so different from 2003 it is as if I'm feeling my way in the dark. The latest issue is figuring out how to get a share working properly. I read the rational behind the change from 2003 but I can't quite wrap my head around the logic of only allowing accessibility using the network name instead of the IP address assigned to the CAP. So, while the network name \\MYCAP is accessible without issue from the members of the cluster on network 1.1.1.x and I can see the created MYSHARE and its contents, accessing \\MYCAP from the 2.2.2.x network is an exercise in futility.
I went ahead and had networking put in a CNAME DNS entry, but that simply resolves the \\MYCAP address to the CAP IP which is worthless since the share MUST be accessed using the network name.
So, my question is how does one make it so that I can access the \\MYCAP fileserver network name properly?
Windows Genuine DISAdvantage
Todas as Respostas
quinta-feira, 28 de junho de 2012 09:19
Have you seen the checklist and walkthrough? http://technet.microsoft.com/en-us/library/cc753969
You'll need to add an IP for both subnets if you want to achieve HA, read point 4 here http://blogs.technet.com/b/josebda/archive/2010/09/03/using-the-multiple-nics-of-your-file-server-running-windows-server-2008-and-2008-r2.aspx which will explain how it works.
So in your case you'll need to add an IP on the 2.2.2.x network too, so your fileserver has two IP's.
Member of Microsoft Extended Experts Team (MEET)
- Sugerido como Resposta Martin G Evans domingo, 1 de julho de 2012 15:07