S
Simon Wilton
This one is driving me mad.
I had a process which worked when I was using LAN manager/DOS on an embedded
device where the embedded device could discover a master on the system where
data files where located. Basically it enumerated the servers it could see
(limited to the same workgroup - but that is fine). It then enumerated the
shares on each one until it found one with a "well known name". It then
mapped that share on that server to drive G: on the itself.
When the master moved from being Windows 9x to 2K the only thing I did add a
user account to it with a user name and password that was know to, and used
by, the embedded device in the map command.
I now want to do the same thing with the master as XP or 2K and the embedded
device as XPe.
I've written it as a console app to see what happens. The API calls are 1
for 1 replacements of those used by LAN Manager API. They are
NetServerEnum(), NetShareEnum() and NetUseAdd().
Config 1: a Win2K PC running the test app enumerates all servers on the
system. Some of them receive an "Access Denied" error enumerating the
shares. It finds the named share on itself and maps it to G: It shows as G:
in "My Computer", and I can open it and see inside it. It may or may not be
that it is using the current user rather than the one specified in
NetUseAdd(). This is good.
Config 2: a Win XP PC running the test app enumerates all servers on the
system. Some of them receive an "Access Denied" error enumerating the
shares. It finds the named share on itself and maps it to G: It does not
appear in "My Computer", any attempt to open it and see inside it by any
other means produces an "Access Denied" error - or similar. This is not
good. What's wrong?
Config 3: the same Win XP PC and an XPe node. The XPe node runs the test
app. It successfully enumerates the PC as a server, but enumerating the
shares on the PC fails "Access Denied". The XPe node was running with
minlogon. It now has Winlogon, and an account whose name and password match
one on the PC. Both are in the same workgroup. Again what's wrong?
TIA
Simon
I had a process which worked when I was using LAN manager/DOS on an embedded
device where the embedded device could discover a master on the system where
data files where located. Basically it enumerated the servers it could see
(limited to the same workgroup - but that is fine). It then enumerated the
shares on each one until it found one with a "well known name". It then
mapped that share on that server to drive G: on the itself.
When the master moved from being Windows 9x to 2K the only thing I did add a
user account to it with a user name and password that was know to, and used
by, the embedded device in the map command.
I now want to do the same thing with the master as XP or 2K and the embedded
device as XPe.
I've written it as a console app to see what happens. The API calls are 1
for 1 replacements of those used by LAN Manager API. They are
NetServerEnum(), NetShareEnum() and NetUseAdd().
Config 1: a Win2K PC running the test app enumerates all servers on the
system. Some of them receive an "Access Denied" error enumerating the
shares. It finds the named share on itself and maps it to G: It shows as G:
in "My Computer", and I can open it and see inside it. It may or may not be
that it is using the current user rather than the one specified in
NetUseAdd(). This is good.
Config 2: a Win XP PC running the test app enumerates all servers on the
system. Some of them receive an "Access Denied" error enumerating the
shares. It finds the named share on itself and maps it to G: It does not
appear in "My Computer", any attempt to open it and see inside it by any
other means produces an "Access Denied" error - or similar. This is not
good. What's wrong?
Config 3: the same Win XP PC and an XPe node. The XPe node runs the test
app. It successfully enumerates the PC as a server, but enumerating the
shares on the PC fails "Access Denied". The XPe node was running with
minlogon. It now has Winlogon, and an account whose name and password match
one on the PC. Both are in the same workgroup. Again what's wrong?
TIA
Simon