Skip to main content

How to setup SAMBA in Linux

How to setup SAMBA in Linux


In this post I am going to share steps to configure Samba in Linux.

For this I have created 2 virtual machines out of which once will act as client and other will act as server.

1) Centos1home.lab--Server Machine for Samba
2) Centos2home.lab--Client Machine which will access Samba Shared file system.


Setup on Server Machine:


• Install samba packages
# Become root user
# yum install samba samba-client samba-common

Samba Server

• Enable samba to be allowed through firewall (Only if you have firewall running)
# firewall-cmd --permanent --zone=public --add-service=samba

[root@centos1home ~]# firewall-cmd --permanent --zone=public --add-service=samba
success

# firewall-cmd --reload

[root@centos1home ~]# firewall-cmd --reload
success


• To stop and disable firewall or iptables(Optional)
# systemctl stop firewalld
# systemctl stop iptables
# systemctl disable firewalld
# systemctl disable iptables

• Create Samba share directory and assign permissions
# mkdir -p /funoracleapps/samba
# chmod a+rwx /funoracleapps/samba
# chown -R nobody:nobody /funoracleapps

[root@centos1home ~]# ls -ld /funoracleapps/samba
drwxrwxrwx. 2 nobody nobody 6 Jun  1 13:18 /funoracleapps/samba

• We need to change the SELinux security context for the samba shared
directory as follows: (Only if you have SELinux enabled)
# chcon -t samba_share_t /funoracleapps/samba

• If you want to disable SELinux, follow these instructions(Optional)
# sestatus (To check the SELinux status)

# vi /etc/selinux/config
Change
SELINUX=enforcing
To
SELINUX=disabled

# reboot

• Modify /etc/samba/smb.conf file to add new shared filesystem (Make sure to
create a copy of smb.conf file)
Delete everything from smb.conf file and add the following parameters
[global]
workgroup = WORKGROUP
netbios name = centos
security = user
map to guest = bad user
dns proxy = no
[Anonymous]
path = /funoracleapps/samba
browsable = yes
writable = yes
guest ok = yes
guest only = yes
read only = no

• Verify the Samba Configuration setting
# testparm

[root@centos1home ~]# testparm
Load smb config files from /etc/samba/smb.conf
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
	netbios name = CENTOS
	security = USER
	idmap config * : backend = tdb


[Anonymous]
	guest ok = Yes
	guest only = Yes
	path = /funoracleapps/samba
	read only = No

• Once the packages are installed, enable and start Samba services
# systemctl enable smb
# systemctl enable nmb
# systemctl start smb
# systemctl start nmb




Server is configured successfully

Mount on Windows client

  • Go to start
  • Go to search bar
  • Type \\192.168.56.101 (This is my server IP, you can check in CentOS IP by running the command ifconfig)

Mount on Linux client

Become root
# yum -y install cifs-utils samba-client

Samba Client


Create a mount point directory

# mkdir -p /him/funsambashare/

Mount the samba share
# mount -t cifs //192.168.56.101/Anonymous /him/funsambashare/
# Enter root  password

Samba Filesystem

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...