svn commit: samba r4440 - inbranches/SAMBA_4_0/source/rpc_server: common srvsvc

[Stefan (metze) Metzmacher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Christopher R. Hertel schrieb:
| On Sun, Jan 02, 2005 at 11:23:54AM +0100, Stefan (metze) Metzmacher wrote:
|
|>>On Sun, Jan 02, 2005 at 11:01:29AM +0100, Stefan (metze) Metzmacher wrote:
|>>
|>>>Hi Chris,
|>>>
|>>>yep I mean this '$' shares which have the 0x80000000 flag set on the
|>>>share
|>>>type
|>>>
|>>>please read the full changeset for details, I use the "browseable = no"
|>>>option for this in samba4, I don't know if samba3 does it the same
|>>>way...
|>>
|>>browseable = no has a different meaning.
|>>
|>>The '$' names are supposed to be handled on the client side.  They work
|>>sort of like the .files in Unix.  The server side shouldn't be filtering
|>>them out.
|>
|>the server should do that, that's the difference between
|>
|>NetShareEnum and NetShareEnumAll in our server code,
|>
|>run the RPC-SRVSVC smbtorture test against a w2k3 box, to see the difference
|
|
| Keeping in mind that I'm a little out of sync with the code...
|
| I'm thinking in terms of what I see on the wire.
|
| On the wire, NetShareEnum call is a RAP call (the RPC version is
| NetrShareEnum)... and it provides the $ names.

there are two rpc calls one returns all shares and one which only return
non hidden shares.

I think windows clients are using the call that returns all shares,
and filter them out on the client




- --
metze

Stefan Metzmacher <metze at samba.org> www.samba.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3-nr1 (Windows XP)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB1/2Hm70gjA5TCD8RAjQqAJwOVT1UVy6ji4QH9jm9/Mxa1KvW9ACfcqRs
ZT60BOTVsMcGSoIKXqssOIw=
=10PO
-----END PGP SIGNATURE-----