Ubuntu Server 14.04 LTS - domain controller configuration (SAMBA) Post: 302940734

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers Ubuntu Server 14.04 LTS - domain controller configuration (SAMBA) Post 302940734 by AQwert on Wednesday 8th of April 2015 03:31:07 PM

04-08-2015

Registered User

Ubuntu Server 14.04 LTS - domain controller configuration (SAMBA)

Hello!
Never configured a Linux server from a scratch.
Reviewed the official documentation and dozens of different "how to", but now one of them helped me to solve the issue.

The need:

Quote:

1. Ubuntu Server (already installed)
2. Connect to it 1 Linux Mint computer (already installed) + 1 computer with Windows 7 (already installed).

Need to create 3 groups with permissions:
1. AdminUsers(with full admin access).
2. SimpleUsers (with limited access and interdiction of applicatoin install on Linux Mint and Windows 7
3. AdvancedUsers (with moderated access: permissions to install apps)

Need to create users inside each of those groups (User: Adm1 inside AdminUsers group, user: Simple1 inside SimpleUseres group, user:Advus inside AdvancedUsers group).
Need to connect with specific user from Linux Mint and Windows 7.
Need to have redirected Desktop to specific folder on the Server (for SimpleUsers - they share same Desktop, for AdminUsers and AdvancedUsers - they have their own Desktop, but still under folders inside Server and not on their local machines.

My final goal is to install a small network (later with around 10 stations) where I can controle the stations OS from the Server (example: limiting different apps installation on Win7-8, Linux Mint 17, MacOS with the users restrictions)
And also add a personalized and group file sharing.

Ubuntu Server 14.04 LTS.
Installed Samba by following this video: _youtube.com/watch?v=Rf7Hk8qWt1Q
_ubuntuforums.org/showthread.php?t=2146198

But receiving errors:

Receiving error in the authentication step verification:
# smbclient //localhost/netlogon -U 'administrator'
Enter administrator's password:
Domain=[USERVER] OS=[Unix] Server=[Samba 4.1.6-Ubuntu]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME

==

And next also receiving error:
kinit administrator@MYDOMAIN.LOCAL
kinit: Cannot contact any KDC for realm 'MYDOMAIN.LOCAL' while getting initial credentials
--

On the side of Win7 I applied two registrie fixes (found this on the web).
But cannot connect the station to the domain.
Cannot even ping the domain: not the host and not the full domain host.mydomain.local
But, when placing the DNS in Win7 with IP of my server can ping the host, but still not the domain: not host.mydomain.local and not mydomain.local, only host unswering pings.

Dont really understand if this is an authomated task: thus mean, that by adding from the side of win7 station to the domain it will create the station name authomaticaly on the side of Ubuntu Server. Or, I need first write this station name somwhere on the side of Ubuntu Server, give the permissions to this specific station and only than add it from the side of Win7.
But all this should be the next steps, presently, as I understand the problem is in correct Samba configuration

Can someone suggest the correction?

Thank you in advance!

AQwert

View Public Profile for AQwert

Find all posts by AQwert

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Samba / FreeBSD member server in MSFT 2003 AD domain

By following the Samba.org how-to's and various finds on groups.google.com I've succeeded in getting a FreeBSD (5.2.1-RELEASE) / Samb-3.0.0,1 server in to my MSFT 2003 Active Directory domain as a member server, but there is a little problem I'm having trouble resolving. Newly created user...

2. UNIX for Dummies Questions & Answers

Samba change domain controller

Hello people i have a samba and they changed domain controller from a windows 2003 to a windows 2008, there is a problem with the version of samba maybe incompatibilities i dont know what show me this domain_client_validate: unable to validate password for user xxxx in domain xxxx to Domain...

3. Debian

Testing a SAMBA Domain Controller

Hello,,, We have an existing(working) MS PDC in our office. I have already installed SAMBA with LDAP Authentication on a TEST machine (on same LAN). But, am unable to join a WinXP machine to this domain. in smb.conf i have: WORKGROUP = mydomain and tried to join the XP machine to...

4. UNIX for Dummies Questions & Answers

how to fix these preoblems in samba in order to act as domain controller

Dear all I now working on samba in order to act as domain controller, but I have some problems in the configuration file that I don't how to solve it, so I hope you able to give me some help: the warnings and the configuration I made : dos charset = 850 unix charset = ISO8859-1 ...

5. Ubuntu

Ubuntu Server 10.04 LTS - Regular crontab "caches old scripts"

Hi, I'm using a Ubuntu Server 10.04 LTS and it works like a charm, except for the regular crontab. Onde day a user had some problems with crontab, i analyse it and i see no problemns, all my stuff is working right. Cron is running smoth... I only noticed it when i altered a script already...

6. Solaris

Solaris 11 server as Primary Domain Controller

Hi, All of our servers run Solaris (currently 10, but looking to upgrade to 11). In each of our offices we have a server configured as a Primary Domain Controller via Samba to provide naming services to our Windoze users. I would like to continue with that arrangement, but I would also like...

7. Ubuntu

Logging samba share in Ubuntu 12.04 LTS

Hi guys I am trying to log full_audit on my samba shares so I know who is creating, deleting, renaming, moving etc. files and directories in the samba/windows share. In my etc/samba/smb.conf file, under I have: # Audit settings full_audit: prefix = %u|%I|%S full_audit:failure =...

LEARN ABOUT SUNOS

asadmin-restart-instance

asadmin-restart-instance(1AS)					   User Commands				     asadmin-restart-instance(1AS)

NAME

       asadmin-restart-instance, restart-instance - restarts the specified server instance and all the services associated with it

SYNOPSIS

       restart-instance  [--user  admin_user]  [--password admin_password] [--host localhost] [--port 4848] [--local=false] [--domain domain_name]
       [--passwordfile filename] [--secure|-s]instance_name

       Use the restart-instance to restart the instance with the instance name specified. The restart-instance command can be run both locally and
       remotely.  To restart remotely, the administration server must be running on the hostname and port number specified. The user authenticates
       using the password identified for the administration server. Additionally, the instance must already exist within the domain served by  the
       administration server, and the instance must be running.  The restart-instance command is not supported on Windows.

OPTIONS

       --user		       administrative user associated for the instance.

       --password	       administrative password corresponding to the administrative user.

       --host		       host name of the machine hosting the administrative instance.

       --port		       administrative port number associated with the administrative host.

       --local		       determines if the command should delegate the request to administrative instance or run locally.

       --domain 	       name of the domain.

       --passwordfile	       file containing passwords appropriate for the command (e.g., administrative instance).

       --secure 	       if true, uses SSL/TLS to communicate with the administrative instance.

OPERANDS

       instance_name	       name of the instance to be restarted.

       Example 1: Using restart-instance in local mode

       asadmin> restart-instance --local --domain domain1 server1
       Instance server1 started

       Where: server1 is the name of the instance restarted on the domain1 domain.

       Example 2: Using restart-instance in remote mode

       asadmin> restart-instance --user admin --password adminadmin --host bluestar --port 4848 server1
       Instance server1 started

       Where:  server1	is the name of the instance restarted. The restarted instance is associated with the user, password, host, and port number
       specified.

EXIT STATUS

       0		       command executed successfully

       1		       error in executing the command

INTERFACE EQUIVALENT

       Server Instance page

       asadmin-delete-instance(1AS),   asadmin-start-instance(1AS),   asadmin-create-instance(1AS),   asadmin-stop-instance(1AS),   asadmin-start-
       appserv(1AS), asadmin-stop-appserv(1AS), asadmin-start-domain(1AS), asadmin-stop-domain(1AS)

J2EE 1.4 SDK							    March 2004					     asadmin-restart-instance(1AS)