Can we setup FILESTREAM on Failover Cluster

I saw following point on Technet article about RBS.
The local FILESTREAM provider is supported only when it is used on local hard disk drives or an attached Internet Small Computer System Interface (iSCSI) device. You cannot use the local RBS FILESTREAM provider on remote storage devices such as network attached storage (NAS).
It looks like that we cannot use FILESTREAM on Failover Cluster because to setup Failover Cluster we need to have NAS. But then the NAS is made available locally for Failover Cluster so FILESTREAM should work right?
Found another article which talks about setting up FILESTREAM on Failover Cluster so I am a bit confused.
https://msdn.microsoft.com/en-us/library/cc645886.aspx

Hi Frank,
As other post, we can set up FILESTREAM on a Failover cluster.
However, FILESTREAM can't live on a network addressable storage (NAS) device unless the NAS device is presented as a local NFS volume via iSCSI. With iSCSI , it is supported by Microsoft
FILESTREAM provider. 
Reference:
Description of support for network database files in SQL Server
Programming with FileStreams in SQL Server 2008
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Similar Messages

  • Can't add VM to Failover Cluster Manager

    I have two VMs: a virtual DC and a virtual SCVMM.  I opened up a Failover Cluster Manager and tried to add both machines.  The DC added successfully but I can't get the SCVMM to add.  
    The error is: 
    "There was a failure configuring the virtual machine role for '<my_machine_name>'
    The RASD '\\<cluster>\\root\virtualization\V2:Msvm_ResourceAllocationSettingData.InstanceID="Microsoft:BBA1664E-07AB-41FA-B3B4-DBA795117449\\663F3FFA-8784-4E92-9A9B-99FC3D705BAC\\0\\0\\D" is not a valid disk type."
    I have no idea what this error is trying to tell me...any help would be greatly appreciated!

    Thank you for your response.
    I double-checked and the VM is located on the shared cluster container.  I went into Hyper-V Manager and looked at the paths and both the virtual machine and virtual hard disks are in the cluster container.
    I have two VM XML files in the cluster container which I've noted with their GUIDs.  For a sanity check, I also went into the specific host and navigated to C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines and found that the same XML files
    there too.  Should those be there?  They are both there so I don't see why I could add the virtual DC but not my virtual SCVMM. 

  • Can't remove Failover Cluster feature on Windows 2008 R2

    Hello
    When remove the Failover Cluster feature has following message:
    Cannot remove Failover Clusting
    This server is an active node in a failover cluster. Uninstalling the Failover CVlustering feature on thos node may impact the availabilty of clustered service and applications. It is recommended that you first evict the server from cluster membership. This
    can be done through the Failover Cluster Management snap-in by expanding the console tree under Nodes, selecting the node, clicking More Actions, and then clicking Evict.
    I'm sure there no cluster formed, so how can I remove it?
    Thanks !

    Hey I have the same problem,
    Somehow cluster got installed on one node on windows 2008 R2 but it was not showing anything in cluster fail over manager wizard and cluster service is
    not running
    when I am trying to remove the fail over cluster it says
    "This
    server is an active node in a failover cluster. Uninstalling the Failover CVlustering feature on those node may impact the availability of clustered service and applications. It is recommended that you first evict the server from cluster membership. This can
    be done through the Failover Cluster Management snap-in by expanding the console tree under Nodes, selecting the node, clicking More Actions, and then clicking Evict."
    But there
    is no cluster at all, I am not sure how remove it
    So let
    me know will that  power shell command "clear-clusternode" fixes my problem?
    and please
    let me know do I need to run it in normal Power shell command line or Power shell failover cluster manager command line?

  • SSAS 2012 (SP2) - Connecting to a Named Instance in a Failover Cluster

    I posted this question some months ago and never got a resolution...still having the same problem. (http://social.msdn.microsoft.com/Forums/sqlserver/en-US/4178ba62-87e2-4672-a4ef-acd970ac1011/ssas-2012-sp1-connecting-to-a-named-instance-in-a-failover-cluster?forum=sqlanalysisservices)
    I have a 3 node failover cluster installation (active-passive-passive) configured as follows:
    Node1: DB Engine 1 (named instance DB01)
    Node2: DB Engine 2 (named instance DB02)
    Node3: Analysis Services (named instance DBAS)
    Obviously, the node indicated is merely the default active node for each service, with each service able to fail from node to node as required.
    Strangely, when I attempt to connect to the SSAS node using the cluster netbios "alias" (dunno, what else it would be called, so I apologize if I am mixing terminology or somesuch), I am only able to do so by specifying the the alias _without_ the
    required named instance. If I issue a connection request using an external program or even SSMS using Node3\DBAS or Node3.domain\DBAS, it appears that the SQL Server Browser is offering up a bogus TCP port for the named instance (in my case TCP/58554), when
    in reality, the SSAS service is running on TCP/2383 (confirmed with netstat) -- which if I understand correctly after much, much reading on the subject is the only port that can be used in a failover cluster. In any case, I'm puzzled beyond words. As I think
    through it, I believe I've seen this issue in the past, but never worried about it since it wasn't necessary to specify the named instance when I had SSAS requirements... It's only a showstopper now because I'm finalizing my implementation of SCVMM/SCOM 2012
    R2, and for some strange reason the PRO configuration in VMM gets all butthurt if you don't offer up a named instance...
    Thank you much for reading. I appreciate any help to get this resolved.
    POSSIBLY NOT RELEVANT...?
    I've properly configured the SPNs for the SSAS service (MSOLAPSvc.3) and the SQL Browser (MSOLAPDisco.3), with the former mapped to the SSAS service account and the latter to the cluster "alias" (since it runs as "NT AUTHORITY\LOCALSERVICE"
    as is customary) and have permitted delegation on the service and machine accounts as required. So, I'm not getting any kerberos issues with the service...any more, that is... ;) I'm not sure that's important, but I wanted to be forthcoming with details to
    help solve the issue.

    When connecting to SSAS in a cluster, you do not specify an instance name.  In your case, you would use the name of the SSAS IP address to connect.
    See:
    http://msdn.microsoft.com/en-us/library/dn141153.aspx
    For servers deployed in a failover cluster, connect using the network name of the SSAS cluster. This name is specified during SQL Server setup, as
    SQL Server Network Name. Note that if you installed SSAS as a named instance onto a Windows Server Failover Cluster (WSFC), you never add the instance name on the connection. This practice is unique to SSAS; in contrast, a named
    instance of a clustered relational database engine does include the instance name. For example, if you installed both SSAS and the database engine as named instance (Contoso-Accounting) with a SQL Server Network Name of SQL-CLU, you would connect to SSAS using
    "SQL-CLU" and to the database engine as "SQL-CLU\Contoso-Accounting". See
    How to Cluster SQL Server Analysis Services for more information and examples.

  • Missing guest in Failover Cluster

    I have a 3 node Server 2012R2 Hyper-V failover cluster with 18 guests. Today, I migrated a guest from VMWare using my normal method to one of the nodes in the cluster. Upon completion I added a role to the cluster, the guest appeared in the list of available
    Virtual Machines and completed successfully. However, I cannot locate the guest on the list of roles within the cluster.
    If I connect to the individual node that I know the guest is on, using Hyper-V Manager, I can see the guest, but Failover Cluster Manager refuses to see it.
    I have tried this on several workstations, no success.
    Any ideas?  I have used this same technique for all of the hosted guests without issue until now.
    Thanks
    Mike

    Start with this, substituting names as necessary:
    (Get-VM -ComputerName VMHOSTNAME -Name VMNAME).IsClustered
    If that's false, then you'll have to re-add it as a cluster resource. I've never seen a clustered VM uncluster on its own, but that would appear to be what happened to you.
    If it's true, then run this, again substituting as necessary:
    Get-ClusterResource -Cluster CLUSTERNAME
    What you're looking for is any mismatch of "Virtual Machine" types against "Virtual Machine Configuration" types. There should be a 1:1 ratio and you should be able to identify which VM goes with which VM Config. Again, I've never seen these become disjointed,
    but it could happen.
    Eric Siron Altaro Hyper-V Blog
    I am an independent blog contributor, not an Altaro employee. I am solely responsible for the content of my posts.
    "Every relationship you have is in worse shape than you think."

  • Can make a DHCP VM in cluster role

    hi
    i have created fail over cluster with windows server 2012
    i have a DHCP vm 
    when i choose roles>> dhcp role to configure that DHCP vm it says no dhcp server found!!
    so my question is isnt it possibel to make a DHCP vm as DHCP fail over role ??
    but if i install DHCP role in physical machine then it shows availabel in cluster role
    istiaq

    Hi,
    You can use the guest vm failover cluster to deploy the DHCP server, you can refer the following similar thread for the future plan.
    The similar thread:
    DHCP with hyperv failover cluster
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/48d24470-61f3-4ed4-bc09-81e6ee9f38c9/dhcp-with-hyperv-failover-cluster?forum=winserverClustering
    Hope this helps.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Failover Cluster Network Name Failed and Can't be Repaired

    I have an issue that seem to be a different problem than any others have encountered.
    I've scoured everything I can find and nothing has fixed my problem.
    The problem starts with the common problem of the cluster network name failing on my 2 node server 2012 file server cluster.  The computer object was still in AD and appeared to be fine so it was not the common problem of the object
    getting deleted somehow.  At the time, there was no other object with that name in the recycling bin, so I don't think it was mistakenly deleted and quickly recreated to cover any tracks, so to speak.
    Following one guide, I tried to find the registry key that corresponded with the GUID of the object, but neither node in the cluster had it in its registry (which may be part of the problem).
    Since it was in the failed state, I tried to do the repair on the object to no avail.
    We run a "locked down" DC environment so all computer objects have to be pre-provisioned.  They were all pre-provisioned successfully and successfully assigned during cluster creation.  The cluster was running with no issues for a month
    or so before this problem came up.
    When I do a repair on the object while taking diagnostic logs the following 4609 error appears:
    The action 'Repair' did not complete. - System.ApplicationException: An error occurred resetting the password for 'Cluster Name'. ---> System.ComponentModel.Win32Exception: Unknown error (0x80005000)
    There appears to be a corresponding 4771 error with a failure code 0x18 that comes from the security log of the DC that states there was a Kerberos pre-authentication failure for the cluster network name object (Domain\Clustername$)
    I believe this is what is causing the repair failure.  All the information I found related to security error 4771 was either a bad credentials given for a user account or the fix was to reconnect the computer to the domain.  I can't seem to find
    a way to do this with the cluster network name.  If there's a way please let me know.
    I've tried a number of things, like resetting the object, disabling it, deleting and creating a new object with the same name, deleting that new object and recovering the original, etc...
    Can anyone shed some light on what is going on and hopefully how to fix it other than rebuilding the cluster?  I'm quite close to just tearing it down and building it back up but am hesitant because this cluster in currently in production...
    Any help would be appreciated

    Hi,
    I don’t find out the similar issue with yours, base on my experience, the 4096 error
     often caused by the CSV disk issue, and the 0x80005000 error some time caused by the repetitive computer object in OU. Please check the above related part or run the validate test then post the error information.
    Although I do have a CSV, there doesn't seem to be any problems with it and it was running just fine for a month or so before the problem started.  I double checked and there is no duplicate computer objects, maybe I don't understand what you mean by
    repetitive, could you explain further?
    The cluster validates successfully with a few warnings:
    Validating cluster resource Name: DT-FileCluster.
    This resource is marked with a state of 'Failed' instead of
    'Online'. This failed state indicates that the resource had a problem either
    coming online or had a failure while it was online. The event logs and cluster
    logs may have information that is helpful in identifying the cause of the
    failure.
    - This is because the cluster name is in the failed state
    Validating the service principal names for Name:
    DT-FileCluster.
    The network name Name: DT-FileCluster does not have a valid
    value for the read-only property 'ObjectGUID'. To validate the service principal
    name the read-only private property 'ObjectGuid' must have a valid value. To
    correct this issue make sure that the network name has been brought online at
    least once. If this does not correct this issue you will need to delete the
    network name and re-create it.
    - This is definitely related to the problem and the GUID probably got removed when we attempted a fix by resetting the object and trying the repair from the failover cluster manager.
    The user running validate, does not have permissions to create
    computer objects in the 'ad.unlv.edu' domain.
    - This is correct, we run a restricted domain.  I have a delegated OU that I can pre-provision accounts in.  The account was pro-provisioned successfully and was at one point setup and working just fine.
    There are no other errors nor warnings.

  • In a Sharepoint 2013 Server farm how far away can the backup of failover cluster servers be located away from the primary servers

    Hello Community
        When you setup a Sharepoint 2013 Server farm
    if you want to provide failover clustering, can
    the servers that the Sharepoint 2013 Server farm
    failover to be located off-site in a different
    location (i.e. how far away can the servers the
    the primary server in the Sharepoint 2013 Server
    farm be away from the failover cluster of backup
    Sharepoint 2013 Server farm servers in distance?
        Thank you
        Shabeaut

    Hiya,
    this article describes in detail the different aspects of creating a highly available SharePoint 2013 server farm.
    Create a high availability architecture and strategy for SharePoint 2013
    http://technet.microsoft.com/en-us/library/cc748824%28v=office.15%29.aspx

  • Can we setup two sets different 7912 logos in one CCM cluster?

    Hi,
    CCM 4.1(3) cluster within head office. We created the 7912 logo for system default image. However, the remote site 7912 phones, need to use a different logo other than the head office.
    as per http://forum.cisco.com/eforum/servlet/NetProf?page=netprof&forum=Unified%20Communications%20and%20Video&topic=IP%20Telephony&CommCmd=MB%3Fcmd%3Dpass_through%26location%3Doutline%40%5E1%40%40.1ddc5d3d/0#selected_message
    We can create the 7912 logo, but how can we setup two or more different 7912 logos for different sites?
    We noticed on CCM4.1(3), there is idle URL for 7912 phone, what is the callmanager default link for this URL? I am thinking to use different logo file names, and put the related URL on this parameters for remote site 7912 phones.
    Could someone let me know or any other better way to do?
    Thanks,
    JJ

    Hi JJ,
    This should work just the way you have described. Have a look;
    Idle
    Enter the URL that displays on the Cisco IP Phone display when the phone has not been used for the time that is specified in Idle Timer field. For example, you can display a logo on the LCD when the phone has not been used for 5 minutes.
    Leave this field blank to accept the default setting.
    Idle Timer (seconds)
    Enter the time (in seconds) that you want to elapse before the URL that is specified in the Idle field displays.
    Leave this field blank to accept the value of the Idle URL Timer enterprise parameter.
    http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_administration_guide_chapter09186a00801ecfc7.html#1121361
    Here how on CCM;
    Method 1:
    Choose System > Enterprise Parameters so that the change is propagated to all of the phones from the Cisco CallManager Administration page.
    In the URL Idle field, enter http://IP_address_of_CallManager/CCMCIP/filename.xml.
    In the URL Idle Time field, enter any positive value in seconds.
    Method 2:
    Choose Device > Phone under the Cisco IP Phone configuration so that only this phone displays the graphics from the Cisco CallManager Administrator page.
    Choose the phone/phones on which you want to put the display.
    In the Idle field, enter the path http://IP_address_of_CallManager/CCMCIP/filename.xml.
    In the Idle Timer field, enter any positive value in seconds.
    From this good doc;
    http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00801c0764.shtml#topic4
    Hope this helps!
    Rob

  • Cannot migrate VM in VMM but can in Failover Cluster Manager network adapters network optimization warning

    I have a 4 node Server 2012 R2 Hyper-V Cluster and manage it with VMM 2012 R2.  I just upgraded the cluster from 2012 RTM to 2012 R2 last week which meant pulling 2 nodes out of the existing cluster, creating the new R2 cluster, running the copy
    cluster roles wizard since the VHDs are stored on CSVs, and then added the other 2 nodes after installing R2 on them, back into the cluster.  After upgrading the cluster I am unable to migrate some VMs from one node to another.  When trying to do
    a live migration, I get the following notifications under the Rating Explanation tab:
    Warning: There currently are not network adapters with network optimization available on host Node7. 
    Error: Configuration issues related to the virtual machine VM1 prevent deployment and must be resolved before deployment can continue. 
    I get this error for 3 out of the 4 nodes in the cluster.  I do not get this error for Node10 and I can live migrate to that node in VMM.  It has a green check for Network optimization.  The others do not.  These errors only affect
    VMM. In the Failover Cluster Manager, I can live migrate any VM to any node in the cluster without any issues.  In the old 2012 RTM cluster I used to get the warning but I could still migrate the VMs anywhere I wanted to.  I've checked the network
    adapter settings in VMM on VM1 and they are the same as VM2 which can migrate to any host in VMM.  I then checked the network adapter settings of the VMs from the Failover Cluster Manager and VM1 under Hardware Acceleration has "Enable virtual machine
    queue" and Enable IPsec task offloading" checked.  I unchecked those 2 boxes refreshed the VMs, refreshed the cluster, rebooted the VM and refreshed again but I still could not live migrate VM1.  Why is this an issue now but it wasn't before
    running on the new cluster?  How do I resolve the issue?  VMM is useless if I can't migrate all my VMs with it.

    I checked the settings on the physical nics on each node and here is what I found:
    Node7: Virtual machine queue is not listed (Cannot live migrate problem VM's to this node in VMM)
    Node8: Virtual machine queue is not listed (Cannot live migrate problem VM's to this node in VMM)
    Node9: Virtual machine queue is listed and enabled (Cannot live migrate problem VM's to this node in VMM)Node10: Virtual machine queue is listed and enabled (Live Migration works on all VMs in VMM)
    From Hyper-V or the Failover Cluster manager I can see in the network adapter settings of the VMs under Hardware Acceleration that these two settings are checked "Enable virtual machine queue" and Enable IPsec task offloading".  I unchecked those
    2 boxes, refreshed the VMs, refreshed the cluster, rebooted the VM and refreshed again but I still cannot live migrate the problem VMs.
    It seems to me that if I could adjust those VM settings from VMM that it might fix the problem.  Why isn't that an option to do so in VMM? 
    Do I have to rebuild the VMM server with a new DB and then before adding the Hyper-V cluster uncheck those two settings on the VM's from Hyper-V manager?  That would be a lot of unnecessary work but I don't know what else to do at this point.

  • Service Accounts for Reporting Service in SQL Server Failover Cluster setup

    I am setting up 2 Report Services (SSRS) in SQL Failover Clustering (Version: 2012SP1) on Windows 2012, as part of scale out architecture.
    There are 2 options to configure the service account for SSRS:
    Option 1) Using domain accounts, as what I have done for DB Engine and SQL Agent.
    Option 2) accept the default, which is virtual account for SSRS. Per documentation URL:
    http://msdn.microsoft.com/en-us/library/ms143504.aspx
    which is the recommended one? is it option 2?
    There is security note on above URL as well, but does not clearly mention that option 1 is not recommended.
    Security Note:  Always run SQL Server services by using the lowest possible user rights. Use a MSA or  virtual account when possible. When MSA and virtual accounts are not possible, use a specific low-privilege user account or domain account instead
    of a shared account for SQL Server services. Use separate accounts for different SQL Server services. Do not grant additional permissions to the SQL Server service account or the service groups. Permissions will be granted through group membership or granted
    directly to a service SID, where a service SID is supported.
    Thanks very much for your help!

    Hi Luo Donghua,
    In SQL Server Failover Cluster Instance, personally two options can run well. If you use the virtual account for SQL Server Reporting Service. Virtual accounts in Windows Server 2008 R2 and Windows 7 are managed local accounts that provide the features to
    simplify service administration. The virtual account is auto-managed, and the virtual account can access the network in a domain environment.
    Of cause, you can also use domain accounts in your clustering. 
    Just make sure your service account is set up here, or that it is using a proper built-in account.For more information, see:http://ermahblerg.com/2012/11/08/cluster-ssrs-in-2008/
    Thanks,
    Sofiya Li
    Sofiya Li
    TechNet Community Support

  • SQL Server 2012 Failover Cluster Setup

    I have to set up a Lab Test environment for SQL Server 2012 with failover clustering. What are the most cost effective specifications for H\W & S\W.  AFAIK Apart of Enterprise edition, Standard edition can support failover clustering for upto
    2 nodes with one node in passive mode. Somewhere (Here) I got that it is possible to configure SQL Server failover clustering On SQL
    Server 2012 Developer edition. Also Is it possible to use Windows 7 Platform with SQL Server 2012 Developer Edition for configuring Always on Failover Clustering. Although I have researched alot, but puzzled. Seeking for experts advise. Thanks in advance.
    Pranshul Gupta

    Yes you can configure and install in windows 7.. but make sure you have made all the proper updates as per the microsoft suggestion..
    Software  and hardware requirments for sql 2012
    http://msdn.microsoft.com/en-us/library/ms143506%28SQL.110%29.aspx
    http://www.yourdba.com/?p=123
    http://resources.arcgis.com/en/help/system-requirements/10.2/index.html#//015100000070000000
    Developer Edition..
    SQL Server 2012 Developer Edition will continue to be part of the SQL Server 2012 family. The Developer edition provides the same feature set as the Enterprise edition. However, it's licensed per developer and can't be used for production work.
    Clustering FAQ's
    http://www.brentozar.com/archive/2012/02/introduction-sql-server-clusters/
    SQL Server licensing :
    http://www.microsoft.com/sqlserver/en/us/future-editions/sql2012-licensing.aspx
    http://www.microsoft.com/sqlserver/en/us/get-sql-server/how-to-buy.aspx
    Overview  and support :
    http://msdn.microsoft.com/en-us/library/cc645993.aspx
    FCI Failover Cluster Instances (SQL Server)
    http://technet.microsoft.com/en-us/library/ms189134.aspx
    AlwaysOn Availability Groups (SQL Server) -- AG's
    http://technet.microsoft.com/en-us/library/hh510230.aspx
    Raju Rasagounder Sr MSSQL DBA

  • I can't find failover cluster management after creating hyper-v cluster on SCVMM 2012 R2

    I've created a hyper-v cluster on scvmm 2012 r2 but I can't find the failover cluster manager to move storage resources. all hosts are showing to have hyperv role and failover clustering feature installed. disk Witness in Quorum is good, same as for the
    other CSV lun. Please help me Microsoft. Thank you. 

    The management consoles are not getting installed while building the cluster through SCVMM. However, its not mandatory to have the management tools on the server. You can have it on a different machine with this management tools installed and connect to
    this cluster remotely.
    Optimism is the faith that leads to achievement. Nothing can be done without hope and confidence.
    InsideVirtualization.com

  • Can a SQL Server Failover Cluster Instance (FCI) be Implemented Between Two Hyper-V Hosted Virtual Machines?

    I haven't had the opportunity to implement a SQL Server Failover Cluster Instance (FCI) for over 10 years and that was done with two physical, identical database servers way back in the day of Windows Server 2003 and SQL Server 2000 (old school).
    Can a SQL Server 2008 R2 Failover Cluster Instance (FCI) be implemented between two Hyper-V hosted virtual machines? The environment in question already has Windows Server 2012 R2 Hyper-V hosts in place, so I'm just looking to see if this is even
    possible and/or supported when utilizing virtual machines.
    The client in question is currently using SQL Server 2008 R2 instances running on Win2008R2, Win2012, and Win2012R2, but I'd also be interested how this can be done or not with SQL Server 2012 or 2014 as well. Thanks in advance.
    Bill Thacker

    Yes, it can be done with Hyper-V guests. In fact, with Windows Server 2012 R2 Hyper-V, guests can use the Shared VHDX feature for shared storage used by Windows clusters. The guests can run Windows Server 2008 and higher provided that the Hyper-V Integration
    Services are installed to support Shared VHDX. The only challenge here is making the Hyper-V hosts highly available as well, running it on WSFC.
    Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
    Blog |
    Twitter | LinkedIn
    SQL Server High Availability and Disaster Recover Deep Dive Course

  • Mac10.x client can't connect to File Server on Windows2008 Failover Cluster

    Installation of a cluster was made according to the document "Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster " http://technet.microsoft.com/en-us/library/cc731844.aspx.
    My Mac OS X 10.5.2 and Mac OS X 10.4.11 clients be able to connect to a non-cluster file server on a Windows 2008 (the File Services role) and also to old file cluster on a Windows 2003.
    Why Mac clients can't connect to Windows 2008 Failover Cluster?

    Are you running a firewall on the Macs. If yes does it work with out the firewall? If it works with out the firewall that means you will have to create a custom ipf rule which includes the both the physical an virtual IP addresses of your cluster.

Maybe you are looking for