Re: Longhorn active node shared folder not seen on virtual server - UR
- From: "Chuck [MSFT]" <ctimon@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 16 Oct 2007 12:40:26 -0400
Do not see this behavior on my clusters....sorry.....no repro here.
In the attached snapshot...I have a local share called 'users' and an HA
share called 'users' online on LH-Node1 at the same time.
--
Chuck Timon, Jr.
Microsoft Corporation
Windows Server 2008 Readiness Team
This posting is provided 'AS IS" with no warranties, and confers no rights.
"Edwin vMierlo [MVP]" <EdwinvMierlo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:eizQYi8DIHA.5980@xxxxxxxxxxxxxxxxxxxxxxx
"Chuck [MSFT]" <ctimon@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:OEHfg$zDIHA.3980@xxxxxxxxxxxxxxxxxxxxxxx
Not true...you can create another share with the same name in W2K8
becasue
of the 'scoping' functionality.
Well, it is in a grey area here,
1) configure a share x:\test called "test" in cluster (so this is in the
scope of your virtual server name)
2) ensure this virtual server/ scope is online on your node you are
working
3) create a folder called c:\test
4) share this (automatically calls it test2 as the share name)
5) goto this c:\test folder, right click, goto properties, choose sharing,
choose advanced sharing
6) add a sharename "test" (this is on the physical node)
error msg: "You are already sharing x:\test using the name test. Do you
want
to share c:\test using the name test instead ?
So the GUI, even when you are working outside the scope where x:\test is
shared as test, it WILL throw you a warning !
(which was not what I expected the first time I saw this, I would have
expected it would allow me to drive on.)
Also, the error message is actually scary... it implies it will
"un-share"... by the usage of the word "instead"... but it actually
doesn't
unshare your cluster configured share.
The "instead" will imply that your x:\test share in your cluster scope is
now suddenly gone... thank god it isn't... but the message should be
changed.
now at the error/warning message, you specifically click yes to make this
share happen... and now you are sharing c:\test as test on the node, and
x:\test as test on the scope in your cluster.
So in that aspect, yes, you can share with the same share name under
different scopes.
lets go back to the OP's problem :
And is this then the case with the API the OP is using ?
I have not checked this with the API's the original poster is using, but I
suspect that it will return first.
Maybe someone with access to some API details on NetShareAdd can help out
here.
as using the GUI comes back with a warning, does NetShareAdd return a
0x80070846 NERR_DuplicateShare because of the "duplicate share, even
outside
of scoping" ?
and if so, then the question is, how does the OP proceed to add this share
?
Attachment:
fc_share.jpg
Description: JPEG image
- References:
- Longhorn active node shared folder not seen on virtual server - URGENT - please help
- From: win_cpp
- Re: Longhorn active node shared folder not seen on virtual server - UR
- From: John Toner [MVP]
- Re: Longhorn active node shared folder not seen on virtual server - UR
- From: Rodney R. Fournier
- Re: Longhorn active node shared folder not seen on virtual server - UR
- From: win_cpp
- Re: Longhorn active node shared folder not seen on virtual server - UR
- From: Edwin vMierlo [MVP]
- Re: Longhorn active node shared folder not seen on virtual server - UR
- From: Chuck [MSFT]
- Re: Longhorn active node shared folder not seen on virtual server - UR
- From: Edwin vMierlo [MVP]
- Longhorn active node shared folder not seen on virtual server - URGENT - please help
- Prev by Date: Re: Clustering DHCP
- Next by Date: Re: Clustering DHCP
- Previous by thread: Re: Longhorn active node shared folder not seen on virtual server - UR
- Next by thread: Re: Longhorn active node shared folder not seen on virtual server - UR
- Index(es):
Relevant Pages
|