Prev: Fedora 8?
Next: USB WiFi woes (was Re: Wap doldrums)
From: Bernard Peek on 7 Jan 2008 14:28
I had a working Samba domain controller at home before using gsambad to
look at the Samba configuration. After I removed the "available = no"
entry it added to each of the service entries I don't have a working
Samba system. My Vista laptop can no longer find the server, and
smbclient on the server itself won't work either.

From the workstation I either get "Path not found" or "The account is
not authorized to log in from this station". Which message I get appears
to be random, it changes without any changes being made to either
system. Smbclient on the server fails with "session setup failed:
NT_STATUS_CANT_ACCESS_DOMAIN_INFO"

After trying a number of things which may have made things worse I tried
deleting the machine account from the server, which succeeded. But I
can't now add a new machine account, smbpasswd fails when I use the -m
option saying it can't modify the password entry.

Any ideas for what I should try next?


--
bap(a)shrdlu.com
From: Will Kemp on 8 Jan 2008 15:26
On Mon, 07 Jan 2008 19:28:53 +0000, Bernard Peek wrote:

> After trying a number of things which may have made things worse I tried
> deleting the machine account from the server, which succeeded. But I
> can't now add a new machine account, smbpasswd fails when I use the -m
> option saying it can't modify the password entry.

I haven't had to configure samba for a few years now, but i always found
'swat' the easiest way to do it. Try the config wizard first. Run swat
using a web browser:

http://localhost:901/

(or replace "localhost" with the name of the computer with samba running
on it.)
From: Bernard Peek on 8 Jan 2008 21:14
Bruce Richardson wrote:
> Bernard Peek <bap(a)shrdlu.com> wrote:
>> Any ideas for what I should try next?
>
> Using a revision control system to manage your configuration files or
> taking regular backups of them or both, for the win. If you had been
> doing that, reverting to a working version would be easy; if you start
> doing it now, it will still make finding a solution easier (because you
> can then make experimental changes and roll them back with confidence)
> and will protect you in the future.

Yes, I've started archiving /etc with a cron job. I'm planning on
uninstalling and rebuilding my Samba configuration, luckily it's a small
network.



--
bap(a)shrdlu.com
From: Martin Gregorie on 9 Jan 2008 17:30
Bruce Richardson wrote:
>
> Then a rebuild from scratch, as you plan, is much better than trying to
> reverse your way through an accumulated set of changes.
>
Yes, agreed.

I've been there too: had a configuration, built from a HOWTO, that more
or less worked though I didn't understand how or why. I bought the
O'Reilly Samba book, read it and then rebuilt the configuration from
scratch. It worked exactly how I wanted and has continued to do so
through several upgrades. I'd definitely recommend you to get that book.

Also, don't forget to use the testparm utility, which validates and
displays the configuration. Run testparm after every change and don't
restart or reload Samba before you've dealt with any problems found by it.


--
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |
 | 
Pages: 1
Prev: Fedora 8?
Next: USB WiFi woes (was Re: Wap doldrums)