I config my smb.conf like follow#======================= Global Settings =====================================[global] workgroup = WORKGROUP server string = Samba Server security = share log file = /var/log/samba/%m.log max log size = 50 dns proxy = no #============================ Share Definitions ===========================
I've got a Windows 7 PC that up until now has been the only one that needed to connect, and therefore, haven't had any issues. Now I'm trying to get an Android tablet and another Windows 7 machine connected and I'm just getting access denied. The 2nd Windows 7 machine will mount the share, but I can't traverse directories. Conf is below.
I'm running CentOS 6.4 and having a problem with Samba shares. All my Windows based computers cannot see CentOS shared folders in the Workgroup, but can open them by IP. Also there is a NAS drive that all Windows boxes can access by name, but CentOS server cannot, only by IP. I did my tests on my home network before getting this box installed at my friend's shop, and everything worked.
I have a question for those of you who are already familiar with Samba 4.x. I understand this new major release comes with many changes under the hood. Now I wonder if I can still configure it as simply as 3.x.
I think I configured my Samba fine, but I cant access the share from a Windows machine. The network is set as bridged in VB configuration and I can ping the Windows machine from CentOS. Also, I can ping it back from the Windows machine.
I've read several threads regarding the setup and use of Samba, and Samba has always been working fine until recently. I didn't change anything, but for some reason, it appears that Samba only resolves hosts on the default "Workgroup" workgroup. However, the /etc/samba/smb.conf file is setup to use a different workgroup.
Having a couple issues:1) I cant connect to my windows computer. When I enter the log in info (both from windows and #! it gets rejected. 2) Everytime after a reboot I have to run sudo /etc/init.d/samba restartor I cant connect to #! from windows. Ive looked through Google and every forum I can think of and having to restart samba seems to be a common issue but I cant find a real fix.