mjwestkamper at weiinc.com
Fri Jun 16 18:03:24 GMT 2000
Each day I get closer.
I successfully joined the domain, to wit...
[root at auxfs bin]# smbpasswd -j WEIOSB -r weidomosb
2000/06/16 12:20:16 : change_trust_account_password: Changed password for domain
Joined domain WEIOSB.
The big problem remains. None of the windows boxes seem able to browse the
Linux/SAMBA box. The HOSTNAME and NETBIOS names are auxfs. The NT PDC apparently
"sees" auxfs since the Server Administration program reports "Specified Network
Any suggestions will be appreciated.
With this seemingly my last hurdle I offer a couple of observations...
The assistance here is great! SAMBA is a better SMB system than any windows variant.
I appreciate its evolution and the tremendous effort by those here. When the PDC
support is on-line a lot of NT systems will go.
Some things I learned that may help others...
The UNIX permissions must be set since SAMBA relies on the underlying system. This
mentioned on the HOWTO for SWAT but with little detail. I blundered through it,
however still do not know a preferred way to do it. I am still a bit fuzzy about the
permissions and groups as it relates to SAMBA using NT as a PDC. Perhaps a
dissertation on this would be applicable in the HOWTO.
SWAT is a good tool, however it allows you to make some pretty obvious, conflicting
entries. If I knew more about the parameters I would write a JAVA script to help
make it a bit more forgiving. Of course if I knew more about it I wouldn't be asking
all these dumb questions.
Somehow SWAT creates a configuration other than /etc/smb.conf. Or least it appears
so. If I look at /etc/smb.conf I see one thing, if I view the configuration with
SWAT I get another.
Mike Brodbelt wrote:
> Juergen Nagler wrote:
> > > They should when WINS is working properly. I can't see your message from
> > > here, but make sure you have all of the
> > >
> > > local master
> > > domain master
> > > preferred master
> > >
> > > options set to yes in smb.conf, as well as the os level=65 line
> > I don't remember if you have an NT as PDC but if so it isn't a good idea
> > to make samba the domain master (IIRC BROWSING.txt of 2.0.6). The same
> > for local and preferred master if the Samba is on the same subnet as the
> > NT-PDC.
> Indeed. I originally sent this to the wrong list (oops), so here it is
> > Mike Westkamper wrote:
> > >
> > >
> > > None of the connected systems seem to browse the Linux box. I have '95, '98,
> > > NT4, and NT5(2k) systems connected.
> > They should when WINS is working properly. I can't see your message from
> > here, but make sure you have all of the
> > local master
> > domain master
> > preferred master
> > options set to yes in smb.conf, as well as the os level=65 line
> Danger!!! If you set the options as above, then your Samba box will
> become a domain master browser for its domain. I'll register the NetBIOS
> name for that domain, and your NT PDC will lose the election. PDC's
> don;t expect this to happen, and are caught unprepared by it. From the
> Samba docs:-
> Note that you should NOT set Samba to be the domain master for a
> workgroup that has the same name as an NT Domain: on each wide area
> network, you must only ever have one domain master browser per
> regardless of whether it is NT, Samba or any other type of domain master
> that is providing this service.
> Your PDC may well fall over quite spectacularly if you do this.
> If you have an NT WINS server on your network, set wins support to no,
> and set the wins server option to be the IP address of that box.
> If you have no WINS server, either simply set wins support to no, and
> live with broadcast based resolution, or set up a WINS server. If you
> want to use Samba as your WINS server, oyu need these parameters set:-
> wins support = yes
> name resolve order = wins lmhosts hosts bcast
> You can also set dns proxy =yes, and it's probabaly a good idea.
More information about the samba-ntdom