On Fri, 4 Oct 2002, Brook Humphrey wrote:

> Is there any other besides vim? Well I use gvim but they use the same
> back-end.
>

kate (which was my first suggestion) works fine for me, suiteable if you
use KDE, you can even edit smb.conf files remotely with kio_fish ;-).

> >
> > and
> > $ man smb.conf
> >
> > Also, you might at least want to read
> > http://ranger.dnsalias.com/mandrake/muo/connect/csamba6.html if you want
> > to run a domain controller, or
> > http://ranger.dnsalias.com/mandrake/muo/connect/csamba5.html if you want
> > to run a domain member (also, if you have two samba servers, one of
> > which is a domain controller).
>
> I have read that already to the letter and well it didn't help much. After
> setting it up exactly like stated I get an error on my xp box about not being
> able to join the domain. I can't remember the exact error.
>

Exact error messages help, if you tell me what it is, I can tell you your
problem. 60% chance it was "Credentials supplied conflict with previously
supplied ....", in which case, blame windows for only being able to have
one connection to any machine as a sinlge user, log out, log back in and
join the domain as your first action.


> No worry swat and linuxconf is not tolerated by me either that is why I can't
> for the life of me figure this out. I've been using this conf file for like
> two years now with no problem. I use webmin to do the initial setup of my
> users and turn on the automatic user addition and subtraction if users are
> added or deleted from my linux box. After that it's all by hand.
>

IMHO, the webmin thing is a hack, pam_smbpasswd might be better (we have
considered making it the default, but we can't really). What it does, is
change the password in /etc/samba/smbpasswd every time a pam password
change is done (ie via passwd or something similar) successfully.


> OK looking back through my smb.conf the one O really use I found the problem.
> The new mandrake automaticly sets my ip to 192.168.1 for the server doing the
> connection sharing. I previously had it set to 192.168.0.
>
> I had a host allow in my smb.conf set to 192.168.0. for security. Now I added
> 192.168.1 and 192.168.2 and 127. this fixed it all. Printing is working
> again. and all my users have access again. The next part is to set up domain
> controller.
>

That would have been my next guess. hosts allow is evil (I hope we don't
have an example in smb.conf unless it's well documented), since it almost
certainly will stuff things up if reverse lookups don't work.

> Sorry about the false alarm and thanks for listening.
>
> Still the default install has changed to this from the default in 8.2. Sorry
> for the problems. listed below is still my smb.conf and smbusers so others
> may get use out of it. Domains is next.
>


Glad you came right. Samba set up right (and in conjunction with CUPS)
makes life way too easy ;-).

Now if only I knew enough about amanda ...

Regards,
Buchan

-- 
|----------------Registered Linux User #182071-----------------|
Buchan Milne                Mechanical Engineer, Network Manager
Cellphone * Work            +27 82 472 2231 * +27 21 8828820x121
Stellenbosch Automotive Engineering         http://www.cae.co.za
GPG Key                   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7


Reply via email to