CentOS 5 Server :: Cannot Access / Var Through Samba
Jul 3, 2010
I'm planning to use a virtual CentOS box for web development (to use the same software as on the real server). I configured Samba to have root guest access to /var/www/ but it doesn't let me in /var. Chmod 777 doesn't help. Nethertheless, I have full access to /sbin and /etc.
I'm trying to set up a test system for Windows 7. I've been having trouble getting it to map drives on the domain where I work, so I wanted to set up a test system with a similar setup so I can play around with settings without mucking up our network. Only problem is I can't get it configured to even work with XP, which does work on our domain.
When I type \server in the Run box I get the explorer window showing all of the test shares I've set up. But when I try to access them, it says the network path could not be found. Here is my smb.conf file:
[global] workgroup = MAJOR netbios name = VPN realm = MAJOR.COM
I installed Samba on CentOS, create a principal share called "public" . I want to populate this share with subfolders, and to grant access rights to specific folders for specific users. The content of "public" will be visible for all Samba users, but they will have read/write access only to the specified subfolders based on my security policy. I need the best way for doing this kind of stuff...
I can't be the first one with this problem. What am I missing?
I have setup Samba servers in the past, just none under SELinux. The last one I configured was a couple years ago, so I wouldn't doubt I'm a bit rusty.
---- Environment summary: Clean server install of CentOS 5.4 includes SELinux - lets call this 'server' - updated samba to 3.0.33-3.15.el5_4.1
Client1 - Windows XP sp4 - WINS configuration uses 'server' noted above Client2 - Windows Vista - WINS configuration uses 'server' noted above
---- What works / what doesn't ------ Clients can see the server (XP and vista) in network neighborhood. The following does not work from windows (xp or vista) net view net view \server net view \server-ip net view \servershare
This does work on the server smbclient -L \server smbclient -L \server --user validuser smbclient -L \client1 --user validuser
---- What I have configured and tried (config/output below) -------- firewall ports for samba are open SELinux enforcing or permissive file context is set on share samba booleans are set
***firewall -A RH-Firewall-1-INPUT -s 192.168.0.0/24 -m state --state NEW -m tcp -p tcp --dport 445 -j ACCEPT -A RH-Firewall-1-INPUT -s 192.168.0.0/24 -m state --state NEW -m udp -p udp --dport 137 -j ACCEPT -A RH-Firewall-1-INPUT -s 192.168.0.0/24 -m state --state NEW -m udp -p udp --dport 138 -j ACCEPT -A RH-Firewall-1-INPUT -s 192.168.0.0/24 -m state --state NEW -m tcp -p udp --dport 139 -j ACCEPT
***SELinux mode/booleans # sestatus SELinux status: enabled SELinuxfs mount: /selinux Current mode: permissive Mode from config file: enforcing Policy version: 21 Policy from config file: targeted
# getsebool -a | grep smb allow_smbd_anon_write --> off smbd_disable_trans --> on
# getsebool -a | grep samba samba_domain_controller --> on samba_enable_home_dirs --> on samba_export_all_ro --> off samba_export_all_rw --> off samba_share_fusefs --> off samba_share_nfs --> off use_samba_home_dirs --> on virt_use_samba --> off
I've been running a Samba server under RedHat 8 for five years without a hiccup. I want to cut over to a F10 box but cannot get shares accessible. smbclient attempts fail over NT password error. SELinux is disabled. Server is visible on the network. Users require no password access to shared data.
smb.conf follows:
# Samba config file created using SWAT # from UNKNOWN (>) # Date: 2009/06/12 14:15:15
I have to rename a group of machines in my little samba domain (tbd backend) but there is an ugly bug that makes this impossible. have set 'rename user script' variable corectly, also checked all configurations.When i change computer name in my windows box, it shows an error saying something like "Error calling remote procedure"Looking on server side, username for the machine gets correctly changed in /usr/passwd, and also in samba database.But samba log says:
=============================================================== [2009/10/08 11:10:32, 0] lib/fault.c:fault_report(42) INTERNAL ERROR: Signal 11 in pid 11052 (3.0.33-3.7.el5_3.1)
i did install and configure samba buy google tutorials. I can ping the centos box from windows but cannt access folder which is on centos. I can ping the machine.
cannot restrict share access to a single user. I've played with the security and valid users options in the smb.conf and I can get it to mount if I remove the valid users option, but this does not provide the access restriction I need. I also left it open and tried making the folder permissions rwx for backupadmin only and that didn't work. I'm using a credentials file which I include below, but I've tried manually entering them in the command too.
[root@aaphst02 /]# mount -t cifs //aapsan01/aapxen01 /mnt/aapxen01 --verbose -o credentials=/root/smbcreds mount.cifs kernel mount options: unc=//aapsan01aapxen01,ip=10.0.1.34,user=backupadmin,ver=1,rw,credentials=/root/smbcreds,pass=********
I have a test server (2.6.18-194.el5) that allows automated tools from Windows 7/Windows Server 2008 to access the filesystem (anonymous NFS access) via Samba (3.5.4-0.70.el5_6.1). Documentation on the smbusers file on samba.org seems a little thin.
* why is it necessary map unix users to samba users?
* what purpose does this mapping serve?
* does the umask of the unix user limit the samba user it is mapped to when creating files/directories? what about anonomous access?
* why are files created via anonymous access owned by 'nobody'?
* how can I control what user and permissions files/directories are created with?
I am using RHEL5 in that i have installed samba rpm as well as created samba users while access the shared folders in WINDOWS i got "access dined" error.
I've installed CentOS 5.3 on a machine, and I need a Samba version 3.2 or higher. Since 3.4 is out, I thought I'd grab that. But, "yum list|grep samba" gives me only version 3.0.33. Is there a package of Samba I can grab that will upgrade the 3.0 installation so that I don't have two laying around? If not and I need to compile from source, do you have any suggestions for what arguments I should give configure? I'm not used to Linux coming from the BSD world
I'm new with Samba and have access problem with Samba on Rhel 5. I want to share iso directory, and user admin can read and write while user bill can read only. smb.conf file looks like this#======================= Global Settings =====================================
I'm setting up a LAMP production server for the first time. When I installed Ubuntu server edition, I selected to install Samba. My idea was to be able to easily access the server's files on the LAN using Windows. All was well and I could ping/ssh between Windows and the Ubuntu server without any problems using the host names. Later, I became concerned that running Samba on a production server might introduce security issues. Therefore, I used apt to purge Samba.
Now I am unable to ping/ssh between the Windows machines and the server using the host names. It only works if I use the IP address.
Two questions:
1.) Is it a security risk to run Samba on a production LAMP server?
2.) How do I get back to being able to use host names without installing Samba?
This is my first post. I am not all that new to Linux. I have done lots of reading on the OS but always felt a little timid when it came to trying out stuff.Here is my problem I have a stand alone samba server I am trying to setup to share all my digital photos and other doc. I can see the share from other machines. On the windows machines you can see the users home directory and the share itself in an folder icon. Whenever I try to access the share it asks for a passwd. I enter the passwd and the share folder is visible when I click on the folder I get and error message.
I have just configured samba on suse linux. I can see it in the windows workgroup but i cannot access it. When it says the server is not accessible. You might not have permission to use this network resource.I have attached a copy of smb.conf
First off a little history of me lol. I'm not completely a Linux noobie, but I'm not the most advanced user either. With that said I have a few interesting problems with Samba.First off I can see the NetBios name under Windows Networking (Windows 7), however everytime I try to connect to it I get an Access Denied and/or "Incorrect Password/Username" error. I have gone into secpol.msc and changed the values that other posts have suggested. Both the server and the workstation are located under the same group, and I have used the smbpasswd -a <username>. The server is not configured to be a Primary Domain Controller so.. I'm lost. Infact my brain hurts from 3 days of this. I have posted my SMB.CONF file to see if that helps. Hum.. Maybe I'm just trying to access a file share that isn't there..
I have installed samba server one month ago and it was working fine till yesterday but today morning when any network client is trying to access samba shared files by giving smb://<serveripaddress> it is asking for password...that is ok but when he is giving the password it is again opening the same password window to enter password again.The clients are giving correct password that is confirm. At the server side i have run smbclient -L localhost -U% and that is giving proper response so that also means that samba server is working fine so i dont know what could be the problem and what its solution.
I configure named and stumble upon the following problem: named is serious about user rights, every config file named uses should be named:named. I set rights to named:named as follows, but they get changed to root:named when I restart named as root. The same thing happens with SELinux context. This results in access denied type errors.
Following yesterday's and then today's upgrade of my Debian 8 32-bit system (among other things to samba 2:4.1.17+dfsg-2+deb8u2 (yesterday: ...deb8u1)) I cannot connect my Mint 17.3 laptop to the server anymore. Were there any changes to smb.conf regarding authentication or other aspects that might lead to this problem? I am enclosing part of my smb.conf. By the way - I also have trouble using ssh to connect to the Debian machine, such as the ssh-command taking "for ever" and then getting the message "Write failed: Broken pipe" when entering an ls-command on the command line.
H. Stoellinger smb.conf: [global] workgroup = RAINERMUSIK netbios name = hsdesk server string = Samba Server hsdesk
I cannot access my Ubuntu samba server using windows XP or 7. I keep getting prompted for a username/password. I have created both a unix username with password and a samba username with the same password i used for the unix user. When windows prompts me for the username/password i give it the same one i created on the samba server, but it still will not take it. I know samba is running because i can view the shares but cannot access them without getting prompted for username/password. I just have the one user for now while i am testing, but there will be more.
I am using samba version 3 (probably), and the problem is that the linux based nas can only be accessed via its ip 192.168.x.x but not its hostname /server string appointed by the smb.conf file:
Code: [global] netbios name = NAS server string = NAS smb passwd file = /etc/smbpasswd
I have just configured samba and it is working fine, the only problem that i have face when i go to access some sharing on samba server it asking me about password but the problem is that its username option is embossed. By default it will login as guest but i dont know the guest password.
I recently switched from centos to fedora as my server choice. Probably not the best decision but I like trying new things. Now before I switched I had my samba server setup just they way I wanted it. Now I'm having a hard time getting it back to that way. Here is my smb.conf
Code: [global] workgroup = workgroup netbios name = netbios name server string = Linux Server security = user wins support = yes encrypt passwords = Yes domain logons = yes [homes] comment = Home Directories browseable = yes writable = yes valid users = %S
[me] path = /home/me read only = no public = yes create mask = 0777 directory mask = 0777 browseable = yes writable = yes
Now I did throw away my old smb.conf because it wasn't that complicated and I figured I could reproduce it.. aside from that everything is working except for the fact that I can access any share I want to listed without it requesting a password. I have a username and password setup with smbpasswd and I think everything else is setup correctly involving samba shares but I have no idea why it won't request a password.
So I setup the newest Ubuntu on my old desktop on a 30g HD and have 2 200G HDs with a ntfs file system on those two. I got SSH and FTP configured, then went on to setup Samba.I have it (seemingly) set up well. /dev/sb1 gets mounted on /data1 /dev/sc1 gets mounted on /data2.I want anyone connected to my router to be able to see this machine and be able to read and write to both shares.
I configured WINS on my laptop to point to the linux box. and i've seen the pc in question (TECH-PC) in "My Network Places" on both of our laptops.Long story short, I try to connect to my network share and it says i don't have permission and i need to contact my network admin. This computer is the only one with Linux installed, the rest are windows-OS.Let me know if you need more info, pretty stumped here, have searched, read, scrapped my install and started from scratch, maybe i need to sleep on it
I am using samba t share my files.I am sharing /media/MEDIA folder. it is a ntfs partition mounted with ntfs-3g with write/read access from linux.I can see and browse my shares and also create files in the root of this partition, ie /media/MEDIA, but in its subfolders i do not have write permissions.
another interesting thing is that i have permission to create directory and delete files everywhere and in any folder, subfolder but when trying to create files i get not enough free disk space error.by the way i dont know if this config file is correct, i find as template in internet.
I'm running Ubuntu 9.1 server on an PII Compaq. Read an article "Samba: How to share files for your LAN without user/password" [URL] and some others and can see and pull up files, can't change or delete. Here is my smb.conf:
# 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 .....
I have a CentOS + Samba server and Windows XP client machines. Users, passwords and permissions are entered on the server machine.users and passwords ( same as on the server ) are entered in the XP client machine.When attempting to access a public file on the server using a XP client machine and the IP address of my server, I am asked a user name and password and none of the already entered seem to work. I cannot access the server file (prompted again and again to enter user name and password). What did i miss
I've recently installed CentOS 5, because I needed a good OS to run VMware Server. Just a heads up, I'm not very familiar with RH/CentOS distros, I usually use Arch Linux. My VMware install went fine, config is standard settings. Now I'm trying to access the VMware Infrastructure Web Access using port 8222 (http) and 8333 (https), but it's a no go. I'm connecting from another machine on the LAN, as the CentOS box is headless. I restarted the vmware services, and they seem to be launching fine. I don't know much about VMware though. I verified with netstat and ports 8222 and 8333 are listening.