05-20-2005
Active Directory is Windows (as you know), and doesn't run on UNIX. Samba can provide 'similar' functionality from a UNIX server, but does not support the replication "feature" of Active Directory, AFAIK.
However, you could set up Kerberos, BIND, and Samba, and use the server as a Domain Controller for a Windows [NT] Domain. There are countless how-tos on the web, Google is your friend.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello - I have a very vague question, which will probably result in vague answers because I don't have a lot of detailed information and I don't know a whole lot about active directory.
Our Windows/NT admin has been rolling out Active Directory over the past several weeks and as time goes on,... (1 Reply)
Discussion started by: rm -r *
1 Replies
2. UNIX for Advanced & Expert Users
Hi all,
I experienced a problem when making a LDAP search from Unix Netscape or Unix Mozilla adressbooks into my Active Directory LDAP db for email addresses.
I add my Domain Controller hostname and the LDAP root dir to search in.
For example:
Name: AD
LDAP server: gullvi
Search Root:... (0 Replies)
Discussion started by: tonlu
0 Replies
3. UNIX for Dummies Questions & Answers
Hi all,
If Windows server have an active directory and active folder/mapping(maybe in unix NFS).
Is there any similiar fuctions in unix. Actually if we have a hundred client in unix/linux with unix server, I want to manage user client and access control easier as in windows.
Thank you in... (5 Replies)
Discussion started by: blesets
5 Replies
4. Shell Programming and Scripting
Automated Unix to Windows Active Directory FTP
I have done many automated FTP scripts using the following logic:
===============================
echo "Starting the FTP transfer..."
{ echo "
open 192.168.1.100
user username password
ascii
put... (1 Reply)
Discussion started by: Cbish68
1 Replies
5. UNIX for Advanced & Expert Users
Hey guys.
Maybe this should go in Security, I'm not sure...
At my work we make websites. Our development servers for these websites are run on a central Debian linux server which we can SSH into, which also contains all the files for these websites. These files are served to the entire... (1 Reply)
Discussion started by: nottrobin
1 Replies
6. Shell Programming and Scripting
Hi folks
I need to write UNIX script (with ldapsearch) to query Active Directory. Input is NT login name and output is Email address.
Attached a screenshot of Sysinternals "AD Explorer". I need to do the same in CLI.
http://i.imgur.com/4s6FB.png
I am absolute LDAP/ldapsearch noob. (0 Replies)
Discussion started by: slashdotweenie
0 Replies
7. Solaris
At the moment we are integrating LDAP in our environment.
Compared to Windows this process is much complicated and time consuming.
With Windows you had Active Directory and if you create a new server, you just add it to the domain and your finished.
Yes, I know Unix is not Windows.
Are there... (1 Reply)
Discussion started by: misterx12345
1 Replies
8. Solaris
Gentleman,
i am trying to setup Authentication for my Solaris 11 Server through Active Directory (Server 2012 R2).
At least some things are already working, for example a getent passwd mydomainuser and ldapsearch command comes back with a correct result. So not everything i did was wrong.
... (1 Reply)
Discussion started by: bahnhasser83
1 Replies
LEARN ABOUT DEBIAN
xpamethod
xpamethod(7) SAORD Documentation xpamethod(7)
NAME
XPAMethod - XPA Communication Methods
SYNOPSIS
XPA supports both inet and unix (local) socket communication.
DESCRIPTION
XPA uses sockets for communication between processes. It supports three methods of socket communication: inet, localhost, and unix. In gen-
eral, the same method should be employed for all XPA processes in a session and the global environment variable XPA_METHOD should be used
to set up the desired method. By default, the preferred method is "inet", which is appropriate for most users. You can set up a different
method by typing something like:
setenv XPA_METHOD local # unix csh
XPA_METHOD=local; export XPA_METHOD # unix sh, bash, windows/cygwin
set XPA_METHOD=localhost # dos/windows
The options for XPA_METHOD are: inet, unix (or local), and localhost. On Unix machines, this environment setup command can be placed in
your shell init file (.cshrc, .profile, .bashrc, etc.) On Windows platforms, it can be placed in your AUTOEXEC.BAT file (I think!).
By default, inet sockets are used by XPA. These are the standard Internet sockets that are used by programs such as Netscape, ftp. etc.
Inet sockets utilize the IP address of the given machine and a (usually random) port number to communicate between processes on the same
machine or between different machines on the Internet. (Note that XPA has an Access Control mechanism to prevent unauthorized access of XPA
access points by other computers on the Net). For users connected to the Internet, this usually is the appropriate communication method.
For more information about setting up XPA communication between machines, see Communication Between Machines.
In you are using XPA on a machine without an Internet connection, then inet sockets are not appropriate. In fact, an XPA process often will
hang for many seconds while waiting for a response from the Domain Name Service (DNS) when using inet sockets. Instead of inet sockets,
users on Unix platforms can also use unix sockets (also known as local sockets). These sockets are based on the local file system and do
not make use of the DNS. They generally are considered to be faster than inet sockets, but they are not implemented under Windows. Use
local sockets as a first resort if you are on a Unix machine that is not connected to the Internet.
Users not connected to the Internet also can use localhost sockets. These are also inet-type sockets but the IP address used for the local
machine is the localhost address, 0x7F000001, instead of the real IP of the machine. Depending on how sockets are set up for a given plat-
form, communication with the DNS usually is not required in this case (though of course, XPA cannot interact with other machines). The
localhost method will generally work on both Unix and Windows platforms, but whether the DNS is required or not is subject to individual
configurations.
A final warning/reminder: if your XPA-enabled server hangs at startup time and your XPA_METHOD is inet, the problem probably is related to
an incorrect Internet configuration. This can be confirmed by using the unix method or (usually) the localhost method. You can use these
alternate methods if other hosts do not need access to the XPA server.
SEE ALSO
See xpa(7) for a list of XPA help pages
version 2.1.14 June 7, 2012 xpamethod(7)