samba - Sep 2022 - Unable to join domain I think.

On 15/09/2022 22:11, Rob Campbell wrote:
> 
> 
> 
>      >
>      > This the other workstation.
>      >
>      >
>      > [Thu Sep 15 07:19:49] [root at D01~$] vim /etc/resolv.conf 
>     (NetworkManager
>      > is updating this)
> 
>     It might be another workstation, but it appears to using the same
>     hostname and IP
> 
>     Rowland
> 
> Currently I'm only working with 3. DC01 (DC), DC02 (not really a DC but
> it was going to be originally) and D01.? Once I get these joining and 
> dns working right I plan to try to join a Fedora workstation.
Then why did you say 'This the other workstation' ?
> 
> Is that script looking for smb.conf to be somewhere other than where it 
> is?? Maybe that's why it says it doesn't exist?
> 
No, the script relies on Samba running to find the smb.conf path, this 
probably wasn't a good idea, but you are the first person that has had 
this problem.

Rowland

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In all things, Be Intentional.


On Fri, Sep 16, 2022 at 3:25 AM Rowland Penny via samba <
samba at lists.samba.org> wrote:
>
>
> On 15/09/2022 22:11, Rob Campbell wrote:
> >
> >
> >
> >      >
> >      > This the other workstation.
> >      >
> >      >
> >      > [Thu Sep 15 07:19:49] [root at D01~$] vim /etc/resolv.conf
> >     (NetworkManager
> >      > is updating this)
> >
> >     It might be another workstation, but it appears to using the same
> >     hostname and IP
> >
> >     Rowland
> >
> > Currently I'm only working with 3. DC01 (DC), DC02 (not really a
DC but
> > it was going to be originally) and D01.  Once I get these joining and
> > dns working right I plan to try to join a Fedora workstation.
>
> Then why did you say 'This the other workstation' ?
>
> >
> > Is that script looking for smb.conf to be somewhere other than where
it
> > is?  Maybe that's why it says it doesn't exist?
> >
>
> No, the script relies on Samba running to find the smb.conf path, this
> probably wasn't a good idea, but you are the first person that has had
> this problem.
>
> Samba isn't actually running.
I'm confused.  This is from the wiki.

i

You must not start the samba service on a domain member. This service is
required only on Active Directory (AD) domain controllers (DC).

then it says:
Samba does not provide System V init scripts, systemd, upstart, or service
files for other init services.

   - If you installed Samba using packages, use the script or service
   configuration file provided by the package to start Samba.
   - If you built Samba, see your distribution's documentation for how to
   create a script or configuration to start services.


Is this referring only to the 'samba' program or does it mean smbd and
nmbd
also?
Do I manually start it or not?  Should I use 'systemctl unmask smbd
nmbd;systemctl enable smbd nmbd;systemctl start nmbd smbd?'

Once I start all the services, I'm able to join and run wbinfo --ping-dc
which I wasn't able to do until I started the services.

> Rowland
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>