First off, I would like to apologize for missing the last meeting and ignoring the
list for this past week and a bit.  Our second child, a little girl was stillborn
on October 1st and I have been busy planning the funeral, and spending time with my
wife.  I only started work up yesterday, I've been off since the 1st.

Anyways, I've been having an issue with one of the servers I admin.  Samba needs to
be restarted once in a while or it won't allow anyone to log into the domain,
however people already logged in work just fine.  I think this problem has to do
with the motherboard chipset (It's VIA, yes I know VIA is crap but this is the
hardware I was given to work with :(  The server was throwing DMA errors which I
couldn't fix without disabling DMA on the harddrives.  I had a feeling that DMA was
causing file system corruption so I disabled DMA and reinstalled Samba.  The
problem seemed to have gone away for a bit but it's happening again.  Besides
having to restart samba to allow people to log in, Samba also shares out / as
whatever user is set as the guest account in samba.  So anyone can go
to //servername/nobody and browse the root of the server.  This for lack of a
better word is annoying.  I've already tried all the obvious things to fix it and
probably most of the not so obvious things.  I have about 25 linux servers out
there, about half of them running Samba with the exact same basic config and I've
never had this problem.  I was just wondering if anyone else has seen this type of
issue before?  It's an AMD processor with a VIA chipset, I think it's the VIA
chipset that is the problem here because I can use the exact same config files for
samba on a Intel processor using a SiS or Intel chipset and it works just fine.
Any ideas?

Thanks,

Trevor

Reply via email to