Samba problems

I may have cause some confusion with my choice of brackets. You have to leave out the brackets everywhere and replace with valid settings. The only place the brackets has to stay is the first line of each share definition which is the share name.
 
I may have cause some confusion with my choice of brackets. You have to leave out the brackets everywhere and replace with valid settings. The only place the brackets has to stay is the first line of each share definition which is the share name.
It's cool ........ I might be taking long to get there but atleast I'm learning why along the way.
 
I may have cause some confusion with my choice of brackets. You have to leave out the brackets everywhere and replace with valid settings. The only place the brackets has to stay is the first line of each share definition which is the share name.
Okay I've done everything as per your notes however I still can't access the NAS server even by just typing in the ip only. I've tried sudo ifconfig and I see the correct ip and subnet as displayed on my router's control center. The native linux firewall is off.

My setup is a HP microserver running the latest Mint connected via cable to the router, a windows 7 home premium laptop connected wirelessly to the router and the router is a TP-Link TL-WR1043ND V2.
 
Okay I've done everything as per your notes however I still can't access the NAS server even by just typing in the ip only. I've tried sudo ifconfig and I see the correct ip and subnet as displayed on my router's control center. The native linux firewall is off.

My setup is a HP microserver running the latest Mint connected via cable to the router, a windows 7 home premium laptop connected wirelessly to the router and the router is a TP-Link TL-WR1043ND V2.

How many network interfaces does the server have? Samba can be set to only use a specific interface which could also be an issue. If it has more than one interface do "ifconfig" and see if eth0 or eth1 is up then look at the samba config in the networking section if the correct interface is named in the quoted setting. If the settings are still commented out with ; then samba will listen to any available interface and you don't need to change anything.

; interfaces = 127.0.0.0/8 eth0
; bind interfaces only = yes

Also try the following command to start samba incase the issue is that the service doesn't auto start at bootup.
sudo service smbd start
If it gives you a success message then you can try browsing again, if it fails post the error message here and also the below logs and your samba config file.

/var/log/samba/log.smbd
/var/log/samba/log.nmbd
/var/log/samba/log.{hostname or ip of your w7 laptop}
/etc/samba/smb.conf
 
How many network interfaces does the server have? Samba can be set to only use a specific interface which could also be an issue. If it has more than one interface do "ifconfig" and see if eth0 or eth1 is up then look at the samba config in the networking section if the correct interface is named in the quoted setting. If the settings are still commented out with ; then samba will listen to any available interface and you don't need to change anything.




Also try the following command to start samba incase the issue is that the service doesn't auto start at bootup.

If it gives you a success message then you can try browsing again, if it fails post the error message here and also the below logs and your samba config file.
It's just got the standard single ethernet plug. Will try the rest and see.
 
Here's some of the screenshots. I will post the logs and conf files when I'm on the computer.uploadfromtaptalk1407566931980.jpguploadfromtaptalk1407566949765.jpguploadfromtaptalk1407566974820.jpguploadfromtaptalk1407566985511.jpg
 
Here's the log files which I've copied and pasted into text files. The forum doesnt allow above 10 000 characters.

The error log are full of the following line so i guess it's save to assume that is the culprit.
Failed to open /var/lib/samba/private/secrets.tdb

The file secrets.tdb should have been created when you did the following command.
sudo smbpasswd -a microserver

Check if this folder exists and if it lists the secrets.tdb file by doing the following.
ls -l /var/lib/samba/private

If a directory does not exists error is returned create it and redo smbpasswd.

sudo mkdir /var/lib/samba/private
sudo smbpasswd -a microserver
sudo service smbd restart

Confirm is the secrets folder has secrets.tdb listed, if so try to browse the server again.
 
The error log are full of the following line so i guess it's save to assume that is the culprit.


The file secrets.tdb should have been created when you did the following command.


Check if this folder exists and if it lists the secrets.tdb file by doing the following.


If a directory does not exists error is returned create it and redo smbpasswd.





Confirm is the secrets folder has secrets.tdb listed, if so try to browse the server again.
Seems to have fixed it partially. I can access the share via ES Explorer on my android but still not on Win 7. That's something to fix some other day. I can now watch movies on my phone from the server.

Thanks guys for all your help helping a noob like me. Much respect!!! :)
 
I've fixed the windows issue. I could ping from windows to linux but not the other way around. So I decided to check the windows firewall log and it was blocking the IP. I have adjusted that and now everything is working.
 
Try the /p (for persistent) option for 'net use'.

I typed in what you said and it said successful and credentials manager says enterprise persistent.

However the mapped drive says network connection has not been restored after a restart but if I type the \\IP\sharename in address bar everything is working 100% again. I haven't figured out why.
 
I typed in what you said and it said successful and credentials manager says enterprise persistent.

However the mapped drive says network connection has not been restored after a restart but if I type the \\IP\sharename in address bar everything is working 100% again. I haven't figured out why.

I had figured out the solution last late night. I looked at the logs again and I saw there was one generated for the Windows 7 pc and in there was the text below. So I Googled it and it referred me to a thread about the wrong path being inserted in the smb.conf file. From there I checked the drive path again and lo and behold I had somehow managed to change the drive name when I was messing around with NFS. So I adjusted the file path in smb.conf and everything works flawlessly :)

Code:
../source3/smbd/service.c:784(make_connection_snum) 
canonicalize_connect_path failed for service WD1, path /media/microserver/WD1

As to why the path was going through successfully when I was entering the path into the explorer address bar I dont know.

Hopefully this thread helps someone on the internets. It was certainly very informative to me :)
 
Top
Sign up to the MyBroadband newsletter
X