Question about Computers & Internet
Follow these instruction to configure samba server
To configure Samba using a graphical interface, use the Samba Server Configuration Tool.
The Samba Server Configuration Tool is a graphical interface for managing Samba shares, users, and basic server settings. It modifies the configuration files in the /etc/samba/ directory. Any changes to these files not made using the application are preserved.
To use this application, you must be running the X Window System, have root privileges, and have the redhat-config-samba RPM package installed. To start the Samba Server Configuration Tool from the desktop, go to the Main Menu Button (on the Panel) => System Settings => Server Settings => Samba or type the command redhat-config-samba at a shell prompt (for example, in an XTerm or a GNOME terminal).
Samba Server Configuration Tool
The Samba Server Configuration Tool does not display shared printers or the default stanza that allows users to view their own home directories on the Samba server.
Configuring Server Settings
The first step in configuring a Samba server is to configure the basic settings for the server and a few security options. After starting the application, select Preferences => Server Settings from the pulldown menu. The Basic tab is displayed as shown in Figure 24-2.
Configuring Basic Server Settings
On the Basic tab, specify which workgroup the computer should be in as well as a brief description of the computer. They correspond to the workgroup and server string options in smb.conf.
Configuring Security Server Settings
The Security tab contains the following options:
Authentication Mode — This corresponds to the security option. Select one of the following types of authentication.
ADS — The Samba server acts as a domain member in an Active Directory Domain (ADS) realm. For this option, Kerberos must be installed and configured on the server, and Samba must become a member of the ADS realm using the net utility, which is part of the samba-client package. Refer to the net man page for details. This option does not configure Samba to be an ADS Controller.
Domain — The Samba server relies on a Windows NT Primary or Backup Domain Controller to verify the user. The server passes the username and password to the Controller and waits for it to return. Specify the NetBIOS name of the Primary or Backup Domain Controller in the Authentication Server field.
The Encrypted Passwords option must be set to Yes if this is selected.
Server — The Samba server tries to verify the username and password combination by passing them to another Samba server. If it can not, the server tries to verify using the user authentication mode. Specify the NetBIOS name of the other Samba server in the Authentication Server field.
Share — Samba users do not have to enter a username and password combination on a per Samba server basis. They are not prompted for a username and password until they try to connect to a specific shared directory from a Samba server.
User — (Default) Samba users must provide a valid username and password on a per Samba server basis. Select this option if you want the Windows Username option to work. Refer to Section 18.104.22.168 Managing Samba Users for details.
Encrypt Passwords — This option must be enabled if the clients are connecting from a Windows 98, Windows NT 4.0 with Service Pack 3, or other more recent versions of Microsoft Windows. The passwords are transfered between the server and the client in an encrypted format instead of in as a plain-text word that can be intercepted. This corresponds to the encrypted passwords option. Refer to Section 24.2.3 Encrypted Passwords for more information about encrypted Samba passwords.
Guest Account — When users or guest users log into a Samba server, they must be mapped to a valid user on the server. Select one of the existing usernames on the system to be the guest Samba account. When guests logs in to the Samba server, they have the same privileges as this user. This corresponds to the guest account option.
After clicking OK, the changes are written to the configuration file and the daemon is restart; thus, the changes take effect immediately.
Managing Samba Users
The Samba Server Configuration Tool requires that an existing user account be active on the system acting as the Samba server before a Samba user can be added. The Samba user is associated with the existing user account.
To add a Samba user, select Preferences => Samba Users from the pulldown menu, and click the Add User button. On the Create New Samba User window select a Unix Username from the list of existing users on the local system.
If the user has a different username on a Windows machine and will be logging into the Samba server from the Windows machine, specify that Windows username in the Windows Username field. The Authentication Mode on the Security tab of the Server Settings preferences must be set to User for this option to work.
Also configure a Samba Password for the Samba User and confirm the Samba Password by typing it again. Even if you select to use encrypted passwords for Samba, it is recommended that the Samba passwords for all users are different from their system passwords.
To edit an existing user, select the user from the list, and click Edit User. To delete an existing Samba user, select the user, and click the Delete User button. Deleting a Samba user does not delete the associated system user account.
The users are modified immediately after clicking the OK button.
Starting and Stopping the Server
On the server that is sharing directories via Samba, the smb service must be running.
View the status of the Samba daemon with the following command: /sbin/service smb status
Start the daemon with the following command: /sbin/service smb start
Stop the daemon with the following command: /sbin/service smb stop
To start the smb service at boot time, use the command: /sbin/chkconfig --level 345 smb on
Posted on Jun 06, 2008
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need.
Posted on Jan 02, 2017
Tips for a great answer:
Sep 02, 2011 | Computers & Internet
The following networking job I have done in this Lab. It is enough for a small office to access or transfer file Printing and access of shared Internet in different type of operating system.
We have recently set up a home office (small laboratory) LAN. All the computers access the internet through a USB wireless (CMDA) dongle. The USB stick is Huawei EC168C and internet service provider is Reliance Infocom (India). But any USB internet dongle can be use to share internet in a LAN in the following way. And you don't need a router for that. In the areas where ISP cannot give wire line internet connection this type of USB wireless sticks are really helpful for home office.
Basic LAN Connection:
Here this lab has 4 PCs. One Windows XP, another Windows Vista starter and two RedHat Linux server systems. Here in this lab I have done the basic LAN connection using cat5 cable & RJ45 connector and an 8 port hub. I have connect the two windows based OS. Using cross cable I have connected two windows system with the hub. Then I put static IP address in Ipv4 of TCP/IP. After that I set workgroup name to join in a workgroup in windows PCs. Then I tried to ping the systems, and it was pinging. Then I have setup a home or small office network in both windows system. That I have enabled the Printer sharing. After that I can share file, data and printer through the system gateway.
Now I have to connect other two Linux PCs in this network. With same cross cable I have joined the both Linux system with the hub. Then to detect the Ethernet device I have put down "DEVICE=eth0" entry in /etc/sysconfig/network-scripts/ifcfg-eth0 file. Then I set IP address in Ethernet device in network configuration in graphical mode (or System-config-network in text mode).After doing this job I restart the network service with "service network restart" command. Then I am trying to ping the systems to one another, And It was pinging.
Now Linux system can access with each other and files also shared through SSH, Telnet,FTP using process and command.
I have configured the Linux system in the following way. First I have set the host name in /etc/sysconfig/network file by VI editor. Next I have edit /etc/sysconfig/network-scripts/ifcfg-eth0 file with "Device=eth0" to detect the Ethernet device. After that I have put the IP add in network configuration file and Restart the network service. To keep the eth0 on permanently I also use the chkconfig command.
After doing this job File sharing can be possible through network file sharing (Nfs). I have install Nfs package & shared the nfs dir by editing exports file. Then I am trying to automount the NFS dir by automounting process. So that I put automounting entry of nfs file in fstab file. After that it's automounted in other system's mount location.
Windows & Linux Networking:
Through basic LAN both OS can only ping each other. To share file or data samba server (a client server in Linux) must be configured in Linux system. So I Install smb rpm package from yum repository. Then I have Configure the samba/smb.conf file. I put the Workgroup name on Workgroup column of samba/smb.conf file. Then I Set the network IP without host to route in network in Host allow column. At last I put down all details of Samba dir, users at the end of the configuration file set the samba password. After that I restart the samba demon to up the samba server. Now files can shared through samba server. In windows I Set the workgroup name pairs with samba server and also set username and password same as samba server. Now I trying to send or access file through samba in both OS and it happened.
USB Net Connect:
Here in this lab workers are use internet from an Usb net connect. So it must be shared in Network. It is too fast so shared internet can be access easily. In Windows XP system I connect the USB netconnect & share it in network. IF all the network setting is ok then all the systems can access shared internet through gateway. Here all users use this shared internet now.
Access of Another System:
VNC Server & Viewer is software through which we can access of another system easily. I just install the software & set the password. Then I run the vnc server. After that I Put the IP add of vncserver from vncviewer of another system and type the password & start access the vnc server system. It can be access form WAN also. I just Run the Vnc server and connect the internet and I got a Wan IP add provided by ISP.
on Jan 12, 2011 | Network Computing Devices (NSH800S/A)...
Oct 09, 2010 | Canonical Ltd. Ubuntu
Oct 27, 2009 | FIC Samba SM-1845 (SM1845GV) Barebone
Mar 05, 2008 | Computers & Internet
Jan 02, 2008 | Toshiba Magnia SG20 Web Server
1,711 people viewed this question
Usually answered in minutes!