Re: Longhorn active node shared folder not seen on virtual server - UR
- From: "Chuck [MSFT]" <ctimon@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 15 Oct 2007 11:27:18 -0400
Not true...you can create another share with the same name in W2K8 becasue of the 'scoping' functionality.
--
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:uvOE4gwDIHA.1184@xxxxxxxxxxxxxxxxxxxxxxx
"win_cpp" <mandards@xxxxxxxxx> wrote in message
news:1192025234.033078.247740@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Elden,
I understand the rational behind the changes.
However then it seems that the APIs are not responding as they should
be. NetShareGetInfo and NetShareAdd seem to be conflicting with each
other. I have a shared folder 'abc' on the virtual server 'vs' which I
can access using \\vs\abc. This share maps to a physical folder on the
shared drive in the cluster, the path being K:\Application\Data. Now
when I query the physcial machine i.e. the active node, machine name -
'MC1' for the share 'abc', NetShareGetInfo returns an error code
0x00000906 which is not documented anywhere. I have checked that share
'abc' does not exist on physical machine. This verification was done
by accessing machine MC1 using UNC .. \\MC1. However when I try to add
a share with name 'abc' on physical active node MC1 using API
NetShareAdd, I get error 0x80070846 i.e. NERR_DuplicateShare.
I am wondering now why should these two APIs behave in such a weird
way. If one cannot access shares on virtual server using physical
machine name in UNC and vice versa, then why does NetShareAdd return
NERR_DuplicateShare while creating a shared folder on physical active
node, with same name as that on virtual server and that also maps onto
same physical folder on the shared resource drive? Also I am confused
by the error code returned by NetShareGetInfo.
I guess this is the new behaviour in 2008... you have created share "abc" on
your virtual server "vs", which is on-line on node MC1.
Therefore node MC1 is already "hosting" a share "abc", but in the scope of
"vs"... so, you cannot create another share called "abc" on this node....
.
- Follow-Ups:
- 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
- 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]
- Longhorn active node shared folder not seen on virtual server - URGENT - please help
- Prev by Date: Re: Upgrade from WIN2K to WIN2K3
- Next by Date: Re: Longhorn active node shared folder not seen on virtual server - UR
- 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
|