Differences between version 20 and predecessor to the previous major change of ActiveDirectorySamba.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 20 | Last edited on Wednesday, June 2, 2004 8:33:29 am | by DougGoldstein | Revert |
| Older page: | version 13 | Last edited on Friday, February 20, 2004 8:05:33 am | by ErikCostlow | Revert |
@@ -30,8 +30,12 @@
192.168.0.1 test1 test1.thinclient.test.org
192.168.0.209 mail mail.thinclient.test.org
''Surely it would be better to put the FQDN first, and not alias localhost to a name other than localhost?'' -- PerryLorier
+
+The proper name of the machine in FQDN should be first then alias(s) after IE 127.0.0.1 mail.thinclient.test.org aliaswhatever1 aliaswhatever2 . Then when you resolve any alias, they point
+to the first textual alias. IE if you ping say mail it should point to mail.thinclient.test.org. In the example it would point to 'mail'. localhost.localdomain is useful for any program that looked at this but they will all point to 'mail' and the corresponding IP in the example.
+Dean
Windows Active Directory server%%%
''%Systemroot%\System32\drivers\etc\hosts''[1]
@@ -184,8 +188,12 @@
session required pam_stack.so service=system-auth
session optional pam_console.so
After we save this file, we should now be able to login to our linux machine with the username THINCLIENT+Administrator, and get ourself a login prompt. Now the system may complain if you do not have the specified home directory created (in this case /home/THINCLIENT/Administrator)
+
+! SSH Support
+
+ Do the same additions that you made to /etc/pam.d/login to /etc/pam.d/sshd to support logins via SSH.
! Have fun
And congrats it works, if you want to configure further items such as mail and other things you may need to modify the apropriate PAM modules, and isn't covered here.
