Changes

From Amahi Wiki
Jump to: navigation, search
4,379 bytes added ,  02:19, 1 February 2019
open == Please read this page carefully ==Since we are getting several users with problems using "wrong" versions, please be aware that:* Only the following versions of Windows will support connecting to a terminal on your hdadomain: Windows 2000 Professional Windows XP Professional Windows XP 64bit Professional Windows Vista business Windows Vista Ultimate Windows 7 Professional Windows 7 Enterprise Windows 7 Ultimate* Any Version of windows NOT listed is NOT supported* Mac OSX does support joining a windows network* Linux supports samba shares* Windows 7 needs tweaking:Open Notepad Copy the following code into notepad:<pre>Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters]"DNSNameResolutionRequired"<nowiki>=</nowiki>dword:00000000"DomainCompatibilityMode"<nowiki>=</nowiki>dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Netlogon\Parameters]"Update"<nowiki>=</nowiki>"no""DisablePasswordChange"<nowiki>=</nowiki>dword:00000000"MaximumPasswordAge"<nowiki>=</nowiki>dword:0000001e"RequireSignOrSeal"<nowiki>=</nowiki>dword:00000001"RequireStrongKey"<nowiki>=</nowiki>dword:00000001"SealSecureChannel"<nowiki>=</nowiki>dword:00000001"SignSecureChannel"<nowiki>=</nowiki>dword:00000001</pre> *Save the file as a .reg NOT a .txt, and double-click it, select Run if asked to run orcancel, if then windows will warn that you use puttyare adding things to the registry click yes as it is safe, then click ok, open it will get entered into the registry.* Windows 7 issues / change log:** There is a warning kicked up that can be ignored. it complains about DNS not beeing set correctly. reboot and you are there** as of 06/02/2010 roaming profiles work under windows 7 == Making Amahi a connection PDC - Primary Domain Controller == *First you need to your hdaenable PDC options for the amahi server.Firstto do this go to your dashboard, then select Setup, backup your smb.conf filethen Settings, in case then tick the box that says '''Advanched Features''' After you run into problems 've done this go to '''Shares''' then '''Settings'''now you can easily revert back'll see the option called '''PDC''' enable it for Amahi to act as a windows PDC Server.  * cp /etc/To '''join''' a machine to the domain, it has to be done by logging in once as [[Open_Terminal_as_root|root]]. Unfortunately, Amahi does not currently automatically create a root sambauser. Type the following into terminal: <pre>smbpasswd -a rootsmbpasswd -e rootservice smb restartservice nmb restart</pre> *This creates a user named root then it enables it, if your running Ubuntu 12.04 you will get a error saying smb: unrecogized service or nmb: unrecogized service, you can restart samba through the dashboard then Setup, then servers, click on Samba and click restart.conf /etc/samba/smb_old ==Complete Domain Setup with A Windows Box==Thanks to obnox for explaining all this to robbiet480 who got his PDC working with the same directions<br>1.confOn the Windows Boxnext we * Windows 7 users need to modify use the registry script above* Go to network connections* Double click your main network connection * Open the TCP/IP properties window* Click advanced* go to the WINS tab* Add your Amahi IP to the smb filelist* force enable NetBIOS Name, i use nano 2. On the Amahi box* If you havent ran this already* Open a terminal (set the samba password for the root user. You need to remember thisfor later!):<pre>smbpasswd -a rootsmbpasswd -e rootservice smb restartservice nmb restart</pre>* if your running Ubuntu 12.04 you will get a error saying smb: unrecogized service or nmb: unrecogized service, you may use any editor you feel confortable withcan restart samba through the dashboard then Setup, then servers, click on Samba and click restart.3. Back to windows!* Open the System window by right clicking on My Computer in the Start Menu* Go to the "Computer Name" tab* Note down the Computer Name4. Back to Amahi!* nano Open a terminal sudo useradd -s /bin/etcfalse -d /sambadev/smbnull ComputerNameNotedEarlier$ sudo smbpasswd -a -m ComputerNameNotedEarlier* Remember the $ on the first line but not the second!* This code authorizes your computer to connect5.confBack to windows again!change * Open the apropriate parts System window by right clicking on My Computer in the smb.confStart Menu* Go to the "Computer Name" tab* Click Changefor convienence i* Type in the domain IN ALL CAPS (default domain name is 'WORKGROUP'll post my complete smbthis may not work but can be changed in your HDA dashboard, under Setup > Shares > Settings then click on the domain name )* Enter root username and password that you setup above / earlier.conf as a sample for you* Restart the computer* Login w/ your user or root from the Windows login screen.* You are done! ==How to Join a Domain with a Non-root User ==    ===============================================================Old Development Notes ====[global]workgroup = {YOUR_DOMAIN}'''WARNING: These settings apply to the beta test only!!'''server string = PDC (%v)'''Other users see the old directives'''netbios name = hdaprinting = cupsBrowse to your HDA dashboard.printcap name = cupsSelect setup, then shares, then settings, then check PDC.load printers = yesnow your new smb.conf is beeing generated!cups options = rawcreate the following file:log file = nano /var/loghda/domain-settings/sambanetlogon/%mlogon.logbatmax log size = 150and add the following to it:socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192<pre>;Sync Windows clock with Samba clockos level = 65preferred master = net time /set /yesdomain master = yes;Mount a samba share into x:local master = yesnet use u: \\hda\BACKUP /persistent:nodomain logons = yes net use v: \\hda\AFBEELDINGEN /persistent:nologon path = net use w: \\hda\profilesDOCUMENTEN /persistent:nologon drive = qnet use x: \\hda\SOFTWARE /persistent:nologon home = net use y: \\hda\%uVIDEOS /persistent:notime server = yesnet use z: \\hda\MUZIEK /persistent:no</pre>unix extensions = yesveto files = /*save the file.eml/*next go to the workstation that you want to add to the domain.nws/riched20Select start, control panel, system, and click computer name.dll/*then select network-id and follow the wizard.{*}/security = userwhen it asks you for a username map script = /usrpassword, supply the root username/share/hda-platform/hda-usermap password you created on the PDC.large readwrite = yesThis is needed because Windows will otherwise be unable to join the Domain.encrypt passwords = yesdos charset = CP850unix charset = UTF8once windows welcomes you to the new domain, you can restart your computer, and login with any user you created through the hda tab!display charset = LOCALEguest account = nobodymap to guest = Bad Userwins support = yesprinter admin = root, @ntadmin, administrator---------
[homes]read only = nobrowseable = no[netlogon]comment = Network Logon Servicepath = /var/hda/domain-settings/netlogonguest ok = yeswritable = noshare modes = no[Profiles]comment = Roaming Profile Sharepath = /var/hda/domain-settings/profiles/%uread only = Noprofile acls = Yes[print$]path = /var/lib/samba/driversread only = yesforce group = rootwrite list = @ntadmin rootforce group = rootcreate mask = 0664directory mask = 0775guest ok = yes[printers]path = /var/spool/sambawriteable = yesbrowseable = yesprintable = yespublic = yes===================================================================Old Directions ====
Open a terminal on your hda, or, if you use putty, open a connection to your hda.<br>
Login as root:
su -
First, backup your smb.conf file, in case you run into problems you can easily revert back.<br>
cp /etc/samba/smb.conf /etc/samba/smb_old.conf
next we need to modify the smb file, i use nano for this, you may use any editor you feel confortable with
nano /etc/samba/smb.conf
change the apropriate parts in the smb.conf.<br>
Save your smb.conf
So at this point we need to create the corresponding directories:
- <pre>mkdir /var/hda/domain-settings- mkdir /var/hda/domain-settings/netlogon* mkdir /var/hda/domain-settings/profiles</pre>
Each time you want a user to join the domain, a user needs to be added, this can be done through the users tab on the amahi dashboard.<br>aditionally, a profile directory needs to be created.<br>* mkdir /var/hda/domain-settings/profiles/nolJanJacobsnol JanJacobs is the user i created through the users tab of the amahi dashboard.<br>
Since we are logging in as root, we need to change the ownership of the previously created directory to the corresponding owner:
chown -R nol JanJacobs /var/hda/domain-settings/profiles/nolJanJacobsNow, this still doesnt allow us to login, because in samba, machines need to be added too!<br>
this can be done automaticly, but for the time beeing we do it manually, amahi may facilitate this for you in the future.
* useradd -s /bin/false -d /dev/null computername$* smbpasswd -a -m computernameNow as you can see there are some differences, when we added the Windows pc to Linux, we added the name computernamecomputer name$, this tells Linux that it is a machine, not a name. <br>Next when we added the Samba password, we invoked the -m, this again tells Samba that we are adding a pc, not a person. <br> Also, you probably noticed that it did not prompt for a password, it just added computername$. <br>When you logon to the domain, Samba will read the password from your Windows password.<br>
Now that this done, all what is left to do is restart Samba,
this also has to be done for each computer you intend to login with.<br>no we dont add the $ sign, since all we do is adding an existing linux user to the samba password file.<br>we tell samba its a machine simply by adding the -m switch to the command.<br>At this point i have network logins working, using roaming profiles.<br>
now its time to restart samba.
* /etc/init.d/smb restart
Now you need to setup your Windows pc for domain logins. <br>(Note the first time that you join a Samba domain from Windows, you will need to join the domain by using root as the name, and your root password for the password. <br>
After rebooting, any valid user will be able to access the domain.)
12,424

edits