FC2 AD authentication, membership

[blunte]

Howdy.

I'm having difficulty integrating this FC2 machine with my Windows network. My web searching has turned up some guides, but they all reference some tool called "kinit", which I don't have (and I see other FC users of the past asking about that as well).

Can someone point me to some guide from the FC2 point of view on how to integrate with an existing MS AD network?

Thanks much.

[skennedy]

I don't have a guide, but I can help you get that setup if you like.

Some questions:

What kind of windows network?
How integrated do you want the FC2 box to be?
What have you tried so far?

[stefan_tech]

That's amusing I came here trying to do that with this very box right now ;-)

I had FC1 on this box and I wanted to have it authenticate users against my AD... From what I've found you want to use winbind (part of samba) which hooks up with PAM. I got close in FC1 but got a strange authentication failed in gdm when logging in (/var/log/messages reported that PAM did query the AD and did approve the user...)

I blew off the machine and reloaded it with FC2 and to my delight has winbind now as an option in system-config-authentication. Still don't have it working though.

I'll post my problem in another topic. But I hope my migraine eases yours ;-)

[blunte]

Ok, first off, since I don't know much about what I'm doing, I have two choices: use the GUI-based admin tools and hope they work for my situation, or follow one of the several guides I found on the internet (but as stated before, they depend on "kinit", which I don't have).

My goal is to be able to log into the Linux machine and be authenticated by the AD server. That way I could browse to network (Windows) resources such as \\winserver3\someshare and be allowed access because my user is a member of a group that has access. In other words, I'd like to have the same unhindered access to network resourced that I have from my Windows machine.

That was phase 1. If I get that working, then I'll want to try providing some file and print services to the network (again, still permissions managed by AD). But that's a secondary goal.

Network Details

DB1 (10.1.72.169) is our AD master
MTSRV1 (10.1.72.210) is our AD secondary and our DNS server

I can provide lots more details about what I've done to this FC2 machine so far, if necessary. Or I can scrap it all and start fresh if that will help.

Thanks much.

[stefan_tech]

To get kinit you need krb5-workstation. Try a yum/apt-get install krb5-workstation.

As for beautiful integration with windows servers and other clients... good luck

I've had good interoperability between operating systems myself... But NEVER easy, usually cryptic to the common user command line commands...

It's getting there... But not yet, IMHO.