[Closed] Setting up Samba

[turboscrew]

I guess I should do the reading.

I also found:

If the hex string is equal to 32 'X' characters then the user's account is marked as disabled
and the user will not be able to log onto the Samba server.

Code: Select all

[jaa@localhost ~]$ sudo smbpasswd -e jaa
Enabled user jaa.
[root@localhost samba]# smbtree
WARNING: The security=share option is deprecated
Enter root's password:
WORKGROUP
...
        \\JAASMB         
cli_start_connection: failed to connect to JAASMB<20> (0.0.0.0). Error NT_STATUS_BAD_NETWORK_NAME
[root@localhost samba]# smbclient -L \\localhost -U jaa
WARNING: The security=share option is deprecated
Enter jaa's password:
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.24]
Server requested LANMAN password (share-level security) but 'client lanman auth = no' or 'client ntlmv2 auth = yes'
tree connect failed: NT_STATUS_ACCESS_DENIED
[root@localhost samba]# pdbedit -L -w
WARNING: The security=share option is deprecated
jaa:500:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:[U          ]:LCT-00000000:


[doktor5000]

For completeness sake about the hostname/name resolution issue, please post the output as root of

Code: Select all

cat /etc/hosts
cat /etc/hostname
cat /etc/sysconfig/network
uname -n
hostname
grep hosts /etc/nsswitch.conf

[turboscrew]

Code: Select all

[root@localhost jaa]# cat /etc/hosts
127.0.0.1               localhost
[root@localhost jaa]#
[root@localhost jaa]# cat /etc/hostname
localhost
[root@localhost jaa]#
[root@localhost jaa]# cat /etc/sysconfig/network
NETWORKING=yes
CRDA_DOMAIN=US
[root@localhost jaa]#
[root@localhost jaa]# uname -n
localhost
[root@localhost jaa]# hostname
localhost
[root@localhost jaa]# grep hosts /etc/nsswitch.conf
hosts:           mdns4_minimal files nis dns myhostname mdns4  wins


Funny, I expected to see 'JAA-MAGEIA' as the machine name (as I set it during install).

Maybe I really should reinstall?

[doktor5000]

Funny, I expected to see 'JAA-MAGEIA' as the machine name (as I set it during install).

Maybe I really should reinstall?

That will probably not fix your samba issue, and as setting the hostname
(where did you set that during installation exactly?
if I read your posts correctly, you mentioned you only set that in smb.conf - that's totally irrelevant to your hostname, only
relevant for your samba configuration - basically this sets the windows hostname for your exports)
didn't work the first time, it will probably not work the second time.

You should simply set your hostname to what you want now. Add a line to /etc/hosts that says

Code: Select all

127.0.0.1    yourhostname

and then, as root set the hostname transiently and permanently (permanent one will end up in /etc/hostname

Code: Select all

hostnamectl set-hostname yourhostname

[turboscrew]

Funny, I could have sworn, but when I looked into some older posts...
Maybe I just put it into Samba...
And took that as setting the machine name as in most other distros I've used - during the installation, before creating the first user.

[turboscrew]

Looks better, immediately, thanks.

Code: Select all

[root@jaa-mageia jaa]#

[turboscrew]

About reinstalling, I just wonder if I've gotten some configs of this machine into such a knot, that Gordion's solution works best.

[turboscrew]

I read the chapter 7 of samba manual, but didn't figure out the problem.
I also read some chapters from the O'railly book, and still no clue.

(I still wonder if wins support should be set... It has usually been...)

Code: Select all

[root@jaa-mageia jaa]# smbclient -U% -L JAA-MAGEIA
WARNING: The security=share option is deprecated
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.24]

        Sharename       Type      Comment
        ---------       ----      -------
        print$          Disk     
        pdf-gen         Printer   PDF Generator (only valid users)
        NewVolume       Disk      NewVolume
        IPC$            IPC       IPC Service (jaa-mageia)
        Canon-MP140-series Printer   Canon MP140 series
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.24]

        Server               Comment
        ---------            -------
        JAASMB               jaa-mageia

        Workgroup            Master
        ---------            -------
        WORKGROUP            JAASMB


I noticed: if I use -U% it works, if I use -U jaa it doesn't.

Code: Select all

[root@jaa-mageia jaa]# smbclient -U jaa -L JAA-MAGEIA
WARNING: The security=share option is deprecated
Enter jaa's password:
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.24]
Server requested LANMAN password (share-level security) but 'client lanman auth = no' or 'client ntlmv2 auth = yes'
tree connect failed: NT_STATUS_ACCESS_DENIED


I guess it's the account Samba doesn't accept.

[turboscrew]

Funny, now MCC doesn't open. Did I use up the MCC usage quota?
Settings open and terminal opens, but MCC doesn't...
Sudoing works...

[doktor5000]

What do you mean by "sudoing works" - how do you run it exactly? What happens when you run

Code: Select all

drakconf

as normal user from a terminal?
Please show the complete output, and also the output of

Code: Select all

ps -ef | grep -v grep | grep -i polkit

[turboscrew]

What do you mean by "sudoing works"

I mean that I still can make myself root - the privileges are there.
Reboot corrected the MCC-thing. Just wondered what might put MCC is such a state that it doesn't start while everything else does.
I'm getting more and more suspicious about that maybe my installation is not all fine.

Maybe I really should reinstall? It doesn't take long, and at least my system would be in a known state.
Any good advice - just to be on the safe side?

Some background (just in case):
I have 5 machines. This one attached to an ADSL-box (ASUS DSL-N12U, because I didn't know better) via ethernet cable.
Another ethernet cable is connected to a wifi-hotspot (the Buffalo-box), and the rest of the machines connect to my home networh via wifi.
This machine is supposed to act as the "central" machine used for sharing the printer and disks (partitions really), and as the "family-machine".
The terminal use would be mostly web-surfing, bill paying and the like. This machine has no Windows, but 3 of the machines do
(1 Vista/Sabayon dual boot, 1 Vista-only, 1 Windows 7 only and 1 Slackware only).

The idea is that the printer and the disks are available to all machines that can connect to my LAN without any logging (except into the wifi) in, because I'd like
my children to be able to "plug in" with their laptops when they visit us. My machines have no firewall - the firewall is in the ADSL-box,
and the wifi is ciphered (WEP, TKIP, WPA), even if I really don't have to worry - there are max. 6 neighbours within the wifi reach (in very good radio-weather).

All my installation selections aim to that kind of usage.
I used to have that with the predecessor of this machine (first Debian/Windows 2000, then Mint / Windows 2000 then Lucid-Puppy (that still run on the old MoBo).
Then the MoBo went BOOM, and I had to get a new one (current). Since then I've been trying to find a distro that works fine on this MoBo and supports my printer.
(Debian 7.x and Mint 17 did not, and I wanted a "family-kind" of Linux that even my grandchildren could use, not a bitdiddler's distro.)

[doktor5000]

What do you mean by "sudoing works"

I mean that I still can make myself root - the privileges are there.
Reboot corrected the MCC-thing. Just wondered what might put MCC is such a state that it doesn't start while everything else does.

If you don't provide anything to help others diagnose this as asked in previous post, nobody can tell.

I'm getting more and more suspicious about that maybe my installation is not all fine.

Maybe I really should reinstall? It doesn't take long, and at least my system would be in a known state.
Any good advice - just to be on the safe side?

Well, then simply do it - backup your important files. Then use the free DVD, format the partitions
and just do a default installation without changing anything else and without installing updates,
that can be done later in installed system so that you minimise downtime.

And document what you change!

[turboscrew]

I'm downloading a new image.
I will reinstall and try to get things up before updating anything.

Thanks, doctor5000, for all the help and especially for your patience with me.
(I may need to turn back to these postings in my next round too.)