sudo install samba 
service smbd restart

#########################
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# – When such options are commented with “;”, the proposed setting
# differs from the default Samba behaviour
# – When commented with “#”, the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# “testparm” to check that you have not made any basic syntactic
# errors.

[fur-pp]
comment = work
path =/mnt/data/fur-pp
browseable = yes
guest ok = yes
writeable = yes
read only = no
[SFC-HR]
comment = work
path =/mnt/data/SFC-HR
browseable = yes
guest ok = yes
writeable = yes
read only = no

#======================= Global Settings =======================

[global]
# workgroup = WORKGROUP
# server string = Samba Server
# security = user
# map to guest = Bad User
# smb protocol = SMB3

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# ‘interfaces’ option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes

#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
max log size = 1000

# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
logging = file

# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d

####### Authentication #######
[B456]
comment = work
path =/mnt/data/fur-datacenter
browseable = yes
guest ok = yes
writeable = yes
read only = no

# Server role. Defines in which mode Samba will operate. Possible
# values are “standalone server”, “member server”, “classic primary
# domain controller”, “classic backup domain controller”, “active
# directory domain controller”.
#
# Most people will want “standalone server” or “member server”.
# Running as “active directory domain controller” will require first
# running “samba-tool domain provision” to wipe databases and create a
# new domain.
server role = standalone server

obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# ‘passwd program’. The default is ‘no’.
pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if ‘server role = classic
# primary domain controller’, ‘server role = classic backup domain controller’
# or ‘domain logons’ is set
#

# It specifies the location of the user’s
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user’s home directory
# (this is Samba’s default)
# logon path = \\%N\%U\profile

# The following setting only takes effect if ‘domain logons’ is set
# It specifies the location of a user’s home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U

# The following setting only takes effect if ‘domain logons’ is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in ‘DOS’ file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/useradd –create-home %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a “machines” group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c “%u machine account” -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup –force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you’re not using the ranges
# for something else.)
; idmap config * : backend = tdb
; idmap config * : range = 3000-7999
; idmap config YOURDOMAINHERE : backend = tdb
; idmap config YOURDOMAINHERE : range = 100000-999999
; template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 means that usershare is disabled.
# usershare max shares = 100

# Allow users who’ve been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user’s home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to ‘no’ if you want to be able to write to them.
; read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only “username”
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the “logon path” option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

[printers]
comment = All Printers
browseable = no
path = /var/tmp
printable = yes
guest ok = no
read only = yes
create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace ‘lpadmin’ with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin

[fur-datacenter]
comment = work
path =/mnt/data1tb/fur-datacenter
browseable = yes
guest ok = yes
writeable = yes
read only = no

[fur-nas]
comment = work
path =/mnt/data/fur-nas
browseable = no
guest ok = yes
writeable = yes
read only = no

#[fur-video Uncensored]
comment = work
path =/mnt/data/fur-video
browseable = yes
guest ok = yes
writeable = yes
read only = no

service ssh restart
#############################
# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented. Uncommented options override the
# default value.

Include /etc/ssh/sshd_config.d/*.conf

#Port 22
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::

#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_ecdsa_key
#HostKey /etc/ssh/ssh_host_ed25519_key

# Ciphers and keying
#RekeyLimit default none

# Logging
#SyslogFacility AUTH
#LogLevel INFO

# Authentication:

#LoginGraceTime 2m
PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

#PubkeyAuthentication yes

# Expect .ssh/authorized_keys2 to be disregarded by default in future.
#AuthorizedKeysFile .ssh/authorized_keys .ssh/authorized_keys2

#AuthorizedPrincipalsFile none

#AuthorizedKeysCommand none
#AuthorizedKeysCommandUser nobody

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#HostbasedAuthentication no
# Change to yes if you don’t trust ~/.ssh/known_hosts for
# HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don’t read the user’s ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no

# Change to yes to enable challenge-response passwords (beware issues with
# some PAM modules and threads)
KbdInteractiveAuthentication no

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
#GSSAPIStrictAcceptorCheck yes
#GSSAPIKeyExchange no

# Set this to ‘yes’ to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the KbdInteractiveAuthentication and
# PasswordAuthentication. Depending on your PAM configuration,
# PAM authentication via KbdInteractiveAuthentication may bypass
# the setting of “PermitRootLogin prohibit-password”.
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and KbdInteractiveAuthentication to ‘no’.
UsePAM yes

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PermitTTY yes
PrintMotd no
#PrintLastLog yes
#TCPKeepAlive yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS no
#PidFile /run/sshd.pid
#MaxStartups 10:30:100
#PermitTunnel no
#ChrootDirectory none
#VersionAddendum none

# no default banner path
#Banner none

# Allow client to pass locale environment variables
AcceptEnv LANG LC_*

# override default of no subsystems
Subsystem sftp /usr/lib/openssh/sftp-server

# Example of overriding settings on a per-user basis
#Match User anoncvs
# X11Forwarding no
# AllowTcpForwarding no
# PermitTTY no
# ForceCommand cvs server

1.) Facebook (Priority สูงสุด) – เข้าถึงลูกค้าได้เร็ว และง่ายที่สุด
✅ ทำไมต้อง Facebook?

คนไทยนิยมใช้มากที่สุด 📊
กลุ่มเป้าหมายของ Evergreen Furniture (เจ้าของบ้าน, คอนโด, ออฟฟิศ, โครงการอสังหาฯ) มีอยู่บน Facebook
ยิงโฆษณาเจาะกลุ่มเป้าหมายได้แม่นยำ (อายุ, ความสนใจ, รายได้ ฯลฯ)
มี Marketplace ที่สามารถขายเฟอร์นิเจอร์ได้โดยตรง
✅ กลยุทธ์ที่ควรใช้:

ยิงโฆษณา Facebook Ads (Target กลุ่มลูกค้าที่สนใจแต่งบ้าน, เฟอร์นิเจอร์, อสังหาฯ)
โพสต์ Content ที่น่าสนใจ เช่น รีวิวลูกค้า, ไอเดียแต่งบ้าน, การใช้งานจริง
Live สดขายสินค้า หรือรีวิวสินค้ารายสัปดาห์
สร้างกลุ่ม Facebook (Community) ให้คนรักเฟอร์นิเจอร์มาแชร์ไอเดีย

2.) TikTok (Priority รองลงมา) – ไวรัลเร็ว ดึงดูดคนรุ่นใหม่
✅ ทำไมต้อง TikTok?

แพลตฟอร์มที่ ไวรัลง่ายสุดในไทย 📈
กลุ่มเป้าหมายอายุ 25-45 ปี ชอบดูคลิปรีวิวสินค้าสั้นๆ ก่อนตัดสินใจซื้อ
คนที่ดู TikTok มักจะตัดสินใจซื้อไว
✅ กลยุทธ์ที่ควรใช้:

ทำคลิปสั้น 15-30 วิ รีวิวเฟอร์นิเจอร์ ตั้งแต่ Before → After
ใช้เสียงไวรัล + Hashtag Trend เช่น #แต่งห้องสวย #เฟอร์นิเจอร์ไม้
Collab กับ Influencer ให้มาช่วยโปรโมตสินค้า

3.) Instagram (Priority รองลงมา) – สร้างภาพลักษณ์พรีเมียม
✅ ทำไมต้อง Instagram?

คนใช้ IG สนใจ ดีไซน์สวยงาม และการตกแต่งบ้าน
แบรนด์เฟอร์นิเจอร์ระดับโลก เช่น IKEA, Muji ใช้ IG สร้าง Branding
มีระบบ Instagram Shopping ที่ช่วยให้ลูกค้าซื้อสินค้าได้ง่าย
✅ กลยุทธ์ที่ควรใช้:

โพสต์ภาพสินค้าสวยๆ และไอเดียแต่งบ้าน
ใช้ Instagram Reels (คล้าย TikTok) โปรโมตสินค้า
ทำ Stories Poll & Q&A สร้าง Engagement

สรุป: แพลตฟอร์มไหนควรเริ่มก่อน?
1️⃣ Facebook → เน้นโฆษณา + Content + Live ขายของ
2️⃣ TikTok → ไวรัลเร็ว + รีวิวสั้น + Influencer
3️⃣ Instagram → Branding สร้างภาพลักษณ์พรีเมียม

💡 แนะนำให้เริ่มจาก Facebook ก่อน เพราะเข้าถึงกลุ่มลูกค้าได้ไวสุด จากนั้นต่อด้วย TikTok และ Instagram เพื่อเสริมพลังให้แบรนด์!

Admin -พร้อม
Budget -พร้อม ก็ลุยได้เลย
วางแผนทำ Content รายเดือน หรือ Ads Strategy  😊

** กระโดดเข้าไปใน Market place LZ ,SP หรืออื่นก็ไม่ใช่เรื่องยากอีกต่อไป (งบประมาณสำคัญที่สุด ควรตั้งเป็นงบการตลาด)