It's an SMB share that I created with webmin... I can see the share and all I just can't add permissions for users from our AD as I can't see them in a list of allowed users. All I see is the linux users on the local box. It's cool that I am on the domain and all but i need to use it now haha

Any idea how to allow domain users access to the share or to even see them?

In the original post, AnRKey was describing the results of attempting to join a domain using Yast2. I too, am having this issue, and I WANT the YAST2 functionality to work: I want SuSE to authenticate its users from the domain controller.

I had 9.2 working in this fashion, but it quit working. I had already installed SuSE 10.0 when we discovered what was wrong (and it was a problem with an update to the W2K3 server that acts as the domain controller).

SuSE 10 will authenticate and join a domain from the command line. However, Yast will not write the config file changes necessary to authenticate logins to the OS from the domain server, because it still gets the ERROR with no description dialog box when trying to set it up through the Samba Client Configurator (ditto for the Samba Server).

I know if I perservere, I can set it all up the hard way and make it function. Anyone with any information about any "tweaks" that can be performed that would bypass the error in Yast, or knowledge about how Yast attempts to perform the JOIN so that some troubleshooting can occur would be appreciated.

It's an SMB share on a linux box...

Hi,

I installed FC4 in one of my office computer. I have one wk3 server as system name qlc-server and domain name quantumleap.co.in . I want to connect my fc4 linux system to authenticate through 2k3 ads.

i have installed samba in fc4 and is running correctly

There are settings in W2K3 domain/ads that will booger up Samba, regardless of distribution. In fact, unknown to me at the time of MY original posting to this thread, we also have an NT4 and W98 that are also tossed out of the domain. The VPN settings on the W2K3 server have something to do with it.

We have adjusted the settings on the server to the point that we can gain individual access to shares in the domain (net use) with NT4, W98, and Linux/Samba, but still can't seem to get ANY of the machines to properly join the domain.

SO......While this thread is NOT an W2K3 Admin primer, let THIS posting be a warning that there are ADS conditions and settings that can ruin your day. A good test to whether you're having Samba problems or W2K3 server issues is to test with NT4 or W98.

I know this is off-topic, but thanks for mentioning "Eventum". It looks like a great package to add to the try-out list.

Ok,...back to you regularly scheduled programming...

Linux share that I want windows accounts on the DC to be able to access...

I know this is a very late answer but i had the same problem on suse.

if smb says: i cannot open the secrets.tdb file because permissions denied

resolution = disable apparmor (or configure it properly )