I have a stable Windows 2003 domain. I refuse to install services for UNIX, although from what I can gather that wouldn't help much anyway.

I have a Fedora Core 5 Terminal Server, that works fine. I have achieved this before, but not sure how, I managed to get Fedora Core 5 logging onto the Windows 2003 domain using the AD usernames and passwords. This is what I want in the long run, is for the Terminal Server users, to login with their AS usernames and passwords.

During the usual process of configuring everything I noticed that winbind was not working correctly. When checked winbind gives the status of "... dead but PID file exsits" or something similar.

Premium support from Red Hat told me this was to do with SELinux, but refused to believe I don't have this enabled.

Someone else told me this was because pam/smb configuartion files were broken, fixed them and got the same problem still.

I really don't want to have to run the network with NT mode enabled for security reasons (any anon user can go poking around). Besides this means pulling down the Active Directory, Reinstalling it, and reconnecting all the clients - I'M NOT DOING IT!

Does anyone have any ideas at all? I really am at a loss.

I have the company domain controller in my study here at home, and it is getting dangerously close to bieng thrown out the window. PLEASE HELP!

This means that Samba crashed and left a file behind. If the file is still in /var/run/ then the service probably won't restart until it is removed. It's safe to just remove PID files left by crashed services.

The Samba log files will probably have error messages that will help to diagnose why the service crashed - if you don't understand them, try pasting them into Google.

FWIW, you can check your Samba configuration by running the "testparm" utility. This simply ensures that the configuration files look valid, so invalid hostnames etc. won't be picked up.

If you are still stuck, please post your smb.conf file here (with important names changed!) and any likely looking error messages. Reading the config file really helps when trying to understand what someone else's system is doing.

I think I got it working now.... I just moved to 2000 server and all was solved ... I think 2003 has some extra jiggery to make it hard... To be honest... I think it was a conf file error... thanks for your help anyway.