Linux Lite Forums
Hardware - Support => Network => Topic started by: Phobos84 on March 02, 2019, 06:27:48 PM
-
Hello,
I really need some help. For whatever reason I struggle with samba every time I have to do anything with it. This time though I am totally lost. So I had an old P4 PC with an older version of Linux Lite that was set up as a media server. After about 40 hours of messing with samba I got it to be visible and accessible by any computer on my network. All was well until I upgraded to a new computer and installed the new version of Lite. I can't get the network to work at all. It can be seen by other computers but not accessed. I have two hard drives in the computer. On has the operating system and the other has the files I need to share on the network. This is my smb.conf file
#======================= Global Settings ====================================
[global]
workgroup = WORKGROUP
server string = Linux Lite Shares
netbios name = Server
security = user
encrypt passwords = true
username map = /etc/samba/smbusers
map to guest = bad user
guest account = nobody
dns proxy = no
#======================= Share Definitions ===================================
[Server]
path = /media/chad2/backup/shares
available = yes
valid users = %U %G
write list = %U
browsable = yes
public = yes
writable = yes
guest ok = yes
read only = no
printable = yes
locking = no
strict locking = no
I'm clueless, any ideas?
-
Hello Phobos84,
https://www.tldp.org/HOWTO/SMB-HOWTO-6.html (https://www.tldp.org/HOWTO/SMB-HOWTO-6.html)
"You can test the correctness of a smb.conf file , using the 'testparm' utility (man page: testparm); if testparm reports no problems, smbd will correctly load the configuration file."
Does testparm utility report any problems, or using it enabled you to solve it ?
There are some samples of conf here, it may help notice a difference
https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Standalone_Server (https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Standalone_Server)
-
Ok this is what it came back with
chad2 ~ testparm
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[Server]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
# Global parameters
[global]
dns proxy = No
map to guest = Bad User
security = USER
server string = Linux Lite Shares
username map = /etc/samba/smbusers
idmap config * : backend = tdb
[Server]
guest ok = Yes
locking = No
path = /media/chad2/backup/shares
printable = Yes
read only = No
strict locking = No
valid users = %U %G
write list = %U
chad2 ~
I don't know what any of this means
-
The thing that bugs me the most about this is I used the same settings from the old smb.conf file. I just changed the directory name to match the new computer. It worked like a charm last time but this time nothing. I would love to see a better way to do this. I really don't like dealing with samba.
-
I haven't used Samba so I am not sure either, I am looking around online for likely things to try.
On this link have a look at the step number 6 restart Samba (did you do this after changing the directory name ? plus it was for the previous machine.)
sudo service smbd restart
and number 8, compare the method of #8 to how you set up the network to see if this area is also good.
https://help.ubuntu.com/community/How%20to%20Create%20a%20Network%20Share%20Via%20Samba%20Via%20CLI%20%28Command-line%20interface/Linux%20Terminal%29%20-%20Uncomplicated%2C%20Simple%20and%20Brief%20Way%21 (https://help.ubuntu.com/community/How%20to%20Create%20a%20Network%20Share%20Via%20Samba%20Via%20CLI%20%28Command-line%20interface/Linux%20Terminal%29%20-%20Uncomplicated%2C%20Simple%20and%20Brief%20Way%21)
Another thing I thought maybe is to check if you have made a rule in UFW to allow Samba, you will have had that on the previous machine, and if it was not added as a rule on the new machine, then it would deny incoming connections.
As I have said I am not familiar with Samba, the conf file looks odd to me it seems to contradict itself.
It says map guests as a bad user in global settings.
But it says %G are valid users in server settings.
It could be Samba needs to define the guest so it can map it as a bad user, it would seem more that if it is not a valid user then it doesnt need to be mapped as a bad user.
Or it can not be in the valid user group and do map guests as a bad user, in case guests try to access it.
Otherwise they look like it could conflict, or at the least slow the code down.
Its just an idea.
-
I followed step 6 and restarted samba. I don't understand step 8. The # List all shares:
smbclient -L //<HOST_IP_OR_NAME>/<folder_name> -U <user>. I don't know how to change this line to make it fit my application. What do I put in for host, folder name, and user?
-
Ok a few tings. I just noticed that in the smb.conf that it has printable = yes. This was making other computers see the server as a printer. So I changed that to "no". This didn't fix the connection problem but now my windows computer sees it as another computer and not a printer. I still can't access anything.
I did verify that the firewall does in fact allow samba
-
For host it needs the Ip address, folder name is the name of the directory of the shared files, user is the username , as the conf file specifies %U, so the username of admin user on the machine running Samba.
During the searches I noticed about the Ip, dns it says on a multiple machine shares then it needs to be different for each one so they can be uniquely identified as which machine they are. I'll look for which link explained it. https://wiki.samba.org/index.php/Multiple_Server_Instances (https://wiki.samba.org/index.php/Multiple_Server_Instances)
Explains for multiple servers but looking at the adresses format is what I meant.
-
If you're not too far into it... The help manual has an easy set up...
https://www.linuxliteos.com/manual/network.html#shares (https://www.linuxliteos.com/manual/network.html#shares)
-
I used the help manual to get me here. It didn't work.
-
For host it needs the Ip address, folder name is the name of the directory of the shared files, user is the username , as the conf file specifies %U, so the username of admin user on the machine running Samba.
During the searches I noticed about the Ip, dns it says on a multiple machine shares then it needs to be different for each one so they can be uniquely identified as which machine they are. I'll look for which link explained it. https://wiki.samba.org/index.php/Multiple_Server_Instances (https://wiki.samba.org/index.php/Multiple_Server_Instances)
Explains for multiple servers but looking at the adresses format is what I meant.
sorry but your talking over my head. What ip address?
-
The systems each need to know the other system exists, and where to find it to connect to it, the route to it.
See this preparing the installing, it explains - https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller#Preparing_the_Installation (https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller#Preparing_the_Installation)
About using the LL Manual as @firenice03 wrote, you had said you are reusing the conf file from a previous install.
Have you tried the manual from the start on this new computer, without using the conf from the previous machine ?
The link in this post also shows how to clean the environment to do a new install.
-
OMG I finally got it. I have seriously put 18 hours into getting this to work today. I HATE SAMBA. Anyway the problem was that I never set the second hard drive to auto mount. Once I did that the directory info changes. You just have to change smb.conf to match. This is what it looks like now.
#======================= Global Settings ====================================
[global]
workgroup = WORKGROUP
server string = Linux Lite Shares
netbios name = Server
security = user
encrypt passwords = true
username map = /etc/samba/smbusers
map to guest = bad user
guest account = nobody
dns proxy = no
#======================= Share Definitions ===================================
[liteshare]
path = /home/%U/linux_share
available = yes
valid users = %U %G
write list = %U
browsable = yes
public = yes
writable = yes
guest ok = yes
read only = no
printable = no
locking = no
strict locking = no
[Gunroom]
path = /mnt/11390a57-b9fd-4fbb-849a-a1006275139d/shares/
available = yes
valid users = %U %G
write list = %U
browsable = yes
public = yes
writable = yes
guest ok = yes
read only = no
printable = no
locking = no
strict locking = no
Thanks everyone for giving me pointers. If nothing else I learned a lot about samba today.
-
Great work @Phobos84 for sticking at it :)
-
OMG I finally got it. I have seriously put 18 hours into getting this to work today. I HATE SAMBA. Anyway the problem was that I never set the second hard drive to auto mount. Once I did that the directory info changes. You just have to change smb.conf to match. This is what it looks like now.
#======================= Global Settings ====================================
[global]
workgroup = WORKGROUP
server string = Linux Lite Shares
netbios name = Server
security = user
encrypt passwords = true
username map = /etc/samba/smbusers
map to guest = bad user
guest account = nobody
dns proxy = no
#======================= Share Definitions ===================================
[liteshare]
path = /home/%U/linux_share
available = yes
valid users = %U %G
write list = %U
browsable = yes
public = yes
writable = yes
guest ok = yes
read only = no
printable = no
locking = no
strict locking = no
[Gunroom]
path = /mnt/11390a57-b9fd-4fbb-849a-a1006275139d/shares/
available = yes
valid users = %U %G
write list = %U
browsable = yes
public = yes
writable = yes
guest ok = yes
read only = no
printable = no
locking = no
strict locking = no
Thanks everyone for giving me pointers. If nothing else I learned a lot about samba today.
Hello and sorry for the bump on this old topic, but I am having major issues with my USB-drive connected to my router.
I can't seem to edit the smb.conf file. I don't have the permissions :(
-
Starting a fresh thread is fine - but you need to provide more information.
The post reads like you are trying to access a drive connected to a router. If that is correct, then you may need to review the router's resource sharing documentation/setup before looking at the client.