Question Locked

Problem to configure Samba Server

0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am having problems configuring Samba server in my Linux machine and I hope you can help me.

I already had this working very well for several year in the Linux box that died recently. In the past, I could connect to the samba server and it worked very well from Windows PC's and Android devices. After getting a new box I installed a newer version of Debian (and I guess also new version of Samba).

Now I started with using the the same old smb.conf, but it didn't work and I already spent many hour reading websites and trying many changes to the config file, but never being able to connect to the Samba server from other devices.

This is my current smb.conf ...

root@jvf:/home/jvf# testparm
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
Weak crypto is allowed
Server role: ROLE_STANDALONE

Press enter to see a dump of your service definitions

# Global parameters
[global]
bind interfaces only = Yes
client min protocol = NT1
dns proxy = No
interfaces = lo eth0
map to guest = Bad User
netbios name = SAMBA
security = USER
server min protocol = NT1
server string = Samba Server %v
wins support = Yes
idmap config * : backend = tdb

[homes]
browseable = No
comment = Home Directories
read only = No

[JVFshare]
comment = JVFshare
create mask = 0660
directory mask = 0770
force group = private
path = /home/vmjosep/MyData/JVFshare
read only = No
valid users = vmjosep
root@jvf:/home/jvf#

3 replies

by rproffitt

I see the valid users to be vmjosep so how are you making sure your devices identify as said user?

by Johnharper2020

Step 1: Install Samba in Linux.
Step 2: Create and Configure Samba Shares.
Step 3: Accessing Samba Share from Windows.
Step 4: Secure Samba Share Directory.
Step 5: Accessing Samba Share from Linux Client.

Regards,
John

by stockmarketmastermind72 edited

It seems like your Samba configuration is encountering issues after migrating to a new Debian version. Here are a few suggestions to troubleshoot:

Check Firewall Settings:
Ensure that the firewall on your new Debian box is not blocking Samba traffic. Adjust firewall rules to allow Samba communication.

Update Samba Configuration:
Samba versions and configurations may vary. Consider updating your smb.conf file to match the syntax and options of the newer Samba version. Check the official Samba documentation for any changes or new parameters.

Review Interfaces and Bindings:
Confirm that the network interfaces specified in your smb.conf file (interfaces = lo eth0 and bind interfaces only = Yes) match the actual network configuration of your new Debian box.

Authentication Issues:
Since you're using security = USER, ensure that the users attempting to connect have valid Samba accounts. Double-check the valid users parameter in your [JVFshare] section.

Protocol Settings:
Your protocol settings (client min protocol, server min protocol, etc.) might be affecting compatibility. Try adjusting these settings to match the capabilities of your Windows PCs and Android devices.

Check Logs:
Examine Samba logs (/var/log/samba/) for any error messages or warnings. They can provide valuable insights into what might be going wrong.

Test Connectivity:
Use tools like smbclient to test connectivity locally on the Debian box. This can help isolate whether the issue is with the Samba server itself or network-related.

Verify Path and Permissions:
Ensure that the path specified in the [JVFshare] section is correct (/home/vmjosep/MyData/JVFshare) and that the Samba process has the necessary permissions to access it.

After making changes, restart the Samba service (sudo service smbd restart) and attempt to connect from a Windows PC or Android device. If issues persist, refer to Samba's official documentation and community forums for additional assistance.

This discussion is closed to new replies.