I've already read a few articles that may be related (see below) but I'm still not sure what is going on in my 2-node failover cluster. This is just a test cluster and the deployed version will be different but I have 2 nodes and quorum access is on a file share. That share can be accessed and is working.
However, each node has our software installed on it and that software creates its own local share (C:\Program Files (x86)\blah) with a share name of 'blah'. I can access that share by the node name (\\machine) but not as the virtual IP (\\192.168.71.101). We access the folders within this share by IP. This local storage access may be moved to shared storage later but for now ignore that. Any ideas why? The domain and AD have the failover computer names, pointers, etc although the reverse zone does not. If that is the issue, I need them to be created automatically by the cluster as our customer likely won't be willing to do that.
Thanks.
----
Apparently I can't post links. Just put http://blogs.technet.com/ before and .aspx behind the links.
b/clustering/archive/2012/04/08/10291792
b/askcore/archive/2009/01/09/file-share-scoping-in-windows-server-2008-failover-clusters