Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MSCS Disk Resource Issue

Status
Not open for further replies.

jhp1

Technical User
Nov 20, 2002
3
US
This is a new active\passive Server 2003 Ent 2 node cluster. The storage is on a SAN and consists of 6 LUNS one of which is the Q:\ Quorum. The remaining 5 LUNS are set up as disk resources J: K: L: M: and N.
I've set up a clustered print server on N:\ and installed 7 printers which are working fine-IP 172.16.84.152;netname-adminprtsvr.
I've been trying to set up the remaining disk resources as available disks (using 'configure Application-New Virtual server')that can be mapped from our network without any success.
Currently I set up disk K: in group CDRom (same network name) IP 172.16.87.103. It is pingable and resolves with both IP and name. However when accessed it shows the content of disk N: the print server.
How can I resolve this issue and set up the remaining disk resources so that they would be able to be mapped.

Thanks In Advance,

Joe
 
Have you setup a network share with the new resource group?

In Windows 2003 when the virtual names are on the same node you can see all the resources on all the virtual names on that host.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog
 
Denny,

Thanks, no I didn't set up a network share, I deleted all 4 of the non functioning disk resources and groups, shut down the second node, then reconfigured (as virtual servers) all of the groups and disk resources {except for the print server which was OK} on the primary node. I then brought up the second node to test their failover capability. They are all OK and are now able to be mapped properly.

Thanks Again

Joe
 
Hello All

However, relating to your suggestion I did set up a clustered share according to: .
These instructions assign the root share (IS) "Everyone group Full Control share level permissions in cluster administrator."
This being the case how can I restrict access to all of the susequent user folders below the root share?
All of my attempts at setting NTFS restrictions on user folders\files beneath the root share have FAILED.
The Everyone share access appears to be inherited from the root share and it overides the NTFS permissions.
Any help would be appreciated.

Thanks

Joe
 
Once you set the Everyone having full control through the network share, you set the permissions via NTFS. The two are a combination of the two, taking the most restrictive of the two.

Denny
MVP
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / SQL 2005 BI / SQL 2008 DBA / SQL 2008 DBD / SQL 2008 BI / MWSS 3.0: Configuration / MOSS 2007: Configuration)
MCITP (SQL 2005 DBA / SQL 2008 DBA / SQL 2005 DBD / SQL 2008 DBD / SQL 2005 BI / SQL 2008 BI)

My Blog
 
You could use abe to filter out stuff you dont want people to see.

2003 uses just alias's so anything on a server is going to show up regardless. 2008 actually masks resources to network names which i think is what you are asking to be able to do.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top