I have a Windows 2008 R2 File Server/SQL Cluster on 2 node active/passive setup. One of the developers at my work was trying to access a hidden share for a partition that is on the iSCSI drive. She was using the clustered name. It would come up with Network
Name Cannot Be Found. I could browse to the share using the ip and the hostname of the node that was active.
I noticed that all shares were still up and nothing looked wrong from the clustering part. I deleted the share and restarted the Server Service. Once I did that all shares that were located on the iSCSI drives that were clustered disappeared.
Now at this point the file sharing cluster is failing because of the missing shares. Now when I try to recreate the shares in Cluster Management it won't let me because it says Network Name Cannot Be Found.
At this point the following has been checked
-Ping the DNS name of the cluster and it translates fine
-Did an nbtstat and everything resolves fine
-The SQL Server Cluster is still up and has no errors
From all I have read one thing that could be wrong is the provider ordering. I checked it and at this point lanmanworkstation is the last in the order after symantec backup, rdp and one other provider.
But if that is the issue why would it start just not working? Why would I still be able to browse by the name of the active node originally?
Any other ideas would be appreciated.