libsmbclient: Browsing and a URI spec?

[Steve Langasek]

On Wed, 3 Jan 2001, Allen, Michael B (RSCH) wrote:

>>> Yes but what if your domain is different from your workgroup as is the case
>>> for me.

> > Well, the 'workgroup' string from smb.conf is used for both the workgroup and
> > the domain.  AFAIK, under NT you can't be a member of a different workgroup
> > than the one associated with your NT domain

> What do you man by "associated with"? I am on a network where the domain
> with which I authenticate is different (meaning the actually name of it is
> different) from the workgroup name my machine registers with WINS.

By 'associated with', I mean 'bearing the same name as'.  If you have an NT
domain called 'FOO', members of that domain will appear in the workgroup 'FOO'
on the network.  Win9x machines may also appear in the workgroup 'FOO', but
they are not part of the domain.

Do you have an NT box where this workgroup/domain split is evident, or is it
only Win9x boxes?  I've only ever seen this on Win9x, where 'domain logons'
really mean 'password server ='.

> Apparently this is a rare arrangement but I believe the reasoning is to break up
> groups by workgroup and then authenticate all users centrally under a
> common domain. Presumably this domain information is retrieved from the
> domain controller when I log in but I don't know the details.

I actually have a similar situation at work.  We wanted to start moving our
Win9x boxes over to do NT domain logon when users log in, so that
authenticating to network resources (all of which were part of the domain by
now) worked more smoothly.  At the same time, users wanted to be able to share
files between one another in their existing workgroup, and this was just fine
with me, because I rather preferred that their netbios names didn't show up
when querying browse lists of machines that had public IPs. :)

> > how is a setting for the default domain useful, other than
> > to specify the credentials of the default username?

>It's not. True. It would only be usefull for smbclient(and perhaps smbclient.so).
>But in at least my case a domain parameter would be applicable to all users
>on a system as they too would all authenticate under the same domain. Might
>be a little confusing for people setting up servers but you might call it
>something else.

Hmm.  I can see where this would have some value.  I'm just not sure how to
integrate it into the structure of smb.conf. Hmm. :/  Anyone else have a good
idea for how to do this? :)

Steve Langasek
postmodern programmer