How to Unite Redhat 9 Linux with Windows 2003 Active Directory authentication


 
Thread Tools Search this Thread
Operating Systems Linux How to Unite Redhat 9 Linux with Windows 2003 Active Directory authentication
# 1  
Old 11-28-2005
How to Unite Redhat 9 Linux with Windows 2003 Active Directory authentication

Dear All,


How to configure a Redhat 9 client to windows 2003 server. I have windows 2003 server which act has domain controller in my office. I have been asked to use redhat 9 has client. how to configure so that redhat 9 can authenticate with windows 2003 server .I have username created in windows 2003 domain sever ,so when my client redhat 9 boot up ask for username and password, i should put username and password and get authenticated with windows 2003 server.if someone can tell me how to configure this in detail will be greatful.

Thanks in advance

Regads
Alex Smilie
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. AIX

Samba 3.6 on AIX 7.1 - Windows 10 Access to AIX file shares using Active Directory authentication

I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users. The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 Replies

2. UNIX for Dummies Questions & Answers

Connect via ssh using active directory authentication

I want to connect via SSH that will authenticate via active directory (domain controller). For example my network login in my workstation is user123/123user under a domain. I wanted to use this details to login via ssh. In this way I don't have to add and create username everytime in the server... (1 Reply)
Discussion started by: lhareigh890
1 Replies

3. Red Hat

Active directory authentication in Linux client?

Hi All, I am a newb in this forums. I am a Linux admin and I hope I will get the solution here. In my company I have setup AD and I can authenticate the windows machines using this AD, also able to apply policy. Now I have installed some Linux machines but I can't able to authenticate via... (6 Replies)
Discussion started by: sahabcse
6 Replies

4. SCO

Authentication problems with Active Directory/Samba/Winbind/Pam

Hi all. I'm having real trouble authenticating users against active directory for my SCO UnixWare 7.1.4 box running samba 3.0.24 (installed via Maintenance pack 4). I can list AD users/groups (after overcoming several hiccups) with wbinfo -g / wbinfo -u. I can use id to get a view an ad user ie:... (0 Replies)
Discussion started by: silk600
0 Replies

5. Solaris

Connect smbclient to an windows server 2003 with active directory

Hello everybody .. i want connect with smbclient to an windows server 2003 with active directory. Exist a version of samba that can do this? Thank you very much for your time. Good Luck :b: (3 Replies)
Discussion started by: enkei17
3 Replies

6. Solaris

Benefit for authentication with Active Directory?

Hello all, I heard that we can use Solaris to authenticate user with Active Directory. However, I do not see the point why we need to do that?? what's the benefit to authenticate user with Active Directory??? Example, I have Solaris and I limited only 10 users can access Solaris production... (1 Reply)
Discussion started by: Smith
1 Replies
Login or Register to Ask a Question
sasl_server_start(3SASL)		      Simple Authentication Security Layer Library Functions			  sasl_server_start(3SASL)

NAME
sasl_server_start - create a new server authentication object SYNOPSIS
cc [ flag ... ] file ... -lsasl [ library ... ] #include <sasl/sasl.h> int sasl_server_start(sasl_conn_t *conn, const char *mech, const char *clientin, unsigned *clientinlen, const char **serverout, unsigned *serveroutlen); DESCRIPTION
The sasl_server_start() interface begins the authentication with the mechanism specified by the mech parameter. sasl_server_start() fails if the mechanism is not supported. PARAMETERS
conn The SASL context for this connection. mech The mechanism name that the client requested. clientin The initial response from the client. The value of clientin is NULL if the protocol lacks support for the client-send-first or if the other end did not have an initial send. No initial client send is distinct from an initial send of a null string. The protocol must account for this difference. clientinlen The length of the initial response. serverout Created by the plugin library. The value of serverout is the initial server response to send to the client. serverout is allocated or freed by the library. It is the job of the client to send it over the network to the server. Protocol specific encoding, for example base64 encoding, must be done by the server. serveroutlen The length of the initial server challenge. RETURN VALUES
sasl_server_start() returns an integer that corresponds to a SASL error code. ERRORS
SASL_OK Authentication completed successfully. SASL_CONTINUE The call to sasl_server_start() was successful, and more steps are needed in the authentication. All other error codes indicate an error situation that must be handled, or the authentication session should be quit. See sasl_errors(3SASL) for information on SASL error codes. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWlibsasl | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ SEE ALSO
gethostname(3C), sasl_errors(3SASL), attributes(5) SunOS 5.10 1 Oct 2003 sasl_server_start(3SASL)