[Samba] Computer can't access Sysvol
Rowland Penny
rowlandpenny241155 at gmail.com
Thu Jul 2 05:00:48 MDT 2015
On 02/07/15 10:32, John Cobley wrote:
>
> On 01/07/2015 14:59, Rowland Penny wrote:
>> On 01/07/15 13:36, John Cobley wrote:
>>> Ok, I've worked out the caching was due to setting up
>>> administratively assigned offline folders.
>>>
>>> However I think I was getting a little mixed up with my servers. The
>>> error log was from a server that still had the share enabled. I've
>>> now removed the share from the config and restarted the Samba
>>> server. Despite this I am still seeing the error when computers try
>>> to update group policy using this server. The only way to update
>>> group policy is to change to the main server using DFS.
>>>
>>>
>>> On 01/07/2015 10:15, John Cobley wrote:
>>>> I did have a "usershares" share when I first set the domain up.
>>>> This has since been removed. The strange thing is that from my PC
>>>> (which was the first to be added to the domain) and from this PC
>>>> (which was the second) I can still see the share (and access it
>>>> from my PC). Seems like there is some caching going on somewhere.
>>>> Any idea how it can be cleared?
>>>>
>>>> John
>>>>
>>>> On 30/06/2015 18:35, Rowland Penny wrote:
>>>>> On 30/06/15 18:08, John Cobley wrote:
>>>>>> Hi All,
>>>>>>
>>>>>> I have a computer which I recently took off the domain before
>>>>>> shipping to HP for repair. I've now had it back and re-added it
>>>>>> to the domain and it no-longer appears to be able to access the
>>>>>> sysvol share (even using a domain admin login).
>>>>>>
>>>>>> I've seen this behaviour in one other machine but as it was just
>>>>>> a test machine I ignored the problem.
>>>>>>
>>>>>> When I try to access the share I can see this in the log -
>>>>>>
>>>>>>> [2015/06/30 17:00:53.055144, 0]
>>>>>>> ../source3/param/loadparm.c:4365(process_usershare_file)
>>>>>>> process_usershare_file: stat of
>>>>>>> /var/lib/samba/usershares/sysvo failed. No such file or directory
>>>>>>
>>>>>> It seems the computer is asking trying to look at a folder that
>>>>>> doesn't exist (the actual folder is "/var/lib/samba/sysvol/".
>>>>>>
>>>>>> I suppose using a symlink may help to get around the problem but
>>>>>> it doesn't really fix the underlying issue.
>>>>>>
>>>>>> Does anyone have any pointers? I can provide extra information
>>>>>> if required.
>>>>>>
>>>>>>
>>>>>> Regards,
>>>>>>
>>>>>> John Cobley
>>>>>
>>>>> The problem here isn't sysvol, it's 'usershares', is there
>>>>> anything in your smb.conf referring to 'usershares' ?
>>>>>
>>>>> Rowland
>>>>>
>>>>
>>>
>>
>> Can we see your smb.conf files ?
>>
>> Rowland
>>
> smb.conf
>> ## Global parameters
>> [global]
>> netbios name = KINGDOM
>> workgroup = CHESTER-DC
>> realm = CHESTER-DC.COMTEK.CO.UK
>> #Note that setting non-int log levels crashes the replication
>> cron script!
>> # log level = 10 acls:9
>> # log level = 1 auth:3 passdb:5 sam:3 smb:3 lanman:3 acls:3
>> locking:3 registry:3
>> # log level = 1 auth:8 acls:8
>> include = /etc/samba/smb.common
>> include = /etc/samba/smb.print
> smb.common
>> [global]
>> server role = active directory domain controller
>> dns forwarder = 10.4.4.10
>> idmap_ldb:use rfc2307 = yes
>> idmap config * : backend = tdb
>> idmap config * : range = 1000000-1999999
>> # idmap config * : backend = autorid
>> # idmap config * : backend = hash
>> # idmap config * : range = 4000000-4999999
>> idmap config CHESTER-DC : backend = ad
>> idmap config CHESTER-DC : range = 1000-999999
>> rpc_server:spoolss = external
>> rpc_daemon:spoolssd = fork
>> load printers = no
>> cups server = printers.comtek.co.uk
>> log file = /var/log/samba/log.%m
>> #kb
>> max log size = 1000
>> panic action = /usr/share/samba/panic-action %d
>>
>> [netlogon]
>> path = /var/lib/samba/sysvol/chester-dc.comtek.co.uk/scripts
>> read only = No
>>
>> [sysvol]
>> path = /var/lib/samba/sysvol
>> read only = No
> smb.print
>> [printers]
>> path = /var/spool/samba
>> printable = yes
>> printing = CUPS
>>
>> [print$]
>> path = /var/lib/samba/printers
>> comment = Printer Drivers
>> writeable = yes
>>
>> [AccountsMFD]
>> path = /var/spool/samba/
>> browseable = yes
>> printable = yes
>> printer name = AccountsMFD
>>
>> [AskarsPrinter]
>> path = /var/spool/samba/
>> browseable = yes
>> printable = yes
>> printer name = AskarsPrinter
>>
>> [BelfastMFD]
>> path = /var/spool/samba/
>> browseable = yes
>> printable = yes
>> printer name = BelfastMFD
>>
>> [DeesideAdmin]
>> path = /var/spool/samba/
>> browseable = yes
>> printable = yes
>> printer name = DeesideAdmin
>>
>> [DeesideDalek]
>> path = /var/spool/samba/
>> browseable = yes
>> printable = yes
>> printer name = DeesideDalek
>> [DeesideDalek]
>> path = /var/spool/samba/
>> browseable = yes
>> printable = yes
>> printer name = DeesideDalek
>>
>> [EngineeringBW]
>> path = /var/spool/samba/
>> browseable = yes
>> printable = yes
>> printer name = EngineeringB+W
>>
>> [EngineeringColour]
>> path = /var/spool/samba/
>> browseable = yes
>> printable = yes
>> printer name = EngineeringColour
>>
>> [ITMFD]
>> path = /var/spool/samba/
>> browseable = yes
>> printable = yes
>> printer name = ITMFD
>>
>> [LogisticsB+W]
>> path = /var/spool/samba/
>> browseable = yes
>> printable = yes
>> printer name = LogisticsB+W
>>
>> [NortelB+W]
>> path = /var/spool/samba/
>> browseable = yes
>> printable = yes
>> printer name = NortelB+W
>>
>> [SalesLaser]
>> path = /var/spool/samba/
>> browseable = yes
>> printable = yes
>> printer name = SalesLaser
>>
>> [SalesFax]
>> path = /var/spool/samba/
>> browseable = yes
>> printable = yes
>> printer name = SalesFax
>>
>> [SalesMFD]
>> path = /var/spool/samba/
>> browseable = yes
>> printable = yes
>> printer name = SalesMFD
>>
>> [Zebra_TLP2844]
>> path = /var/spool/samba/
>> browseable = yes
>> printable = yes
>> printer name = Zebra_TLP2844
>
There doesn't seem to be anything wrong with your smb.conf files, apart
from this:
idmap config * : backend = tdb
idmap config * : range = 1000000-1999999
# idmap config * : backend = autorid
# idmap config * : backend = hash
# idmap config * : range = 4000000-4999999
idmap config CHESTER-DC : backend = ad
idmap config CHESTER-DC : range = 1000-999999
And the only thing wrong with it is, it wont do anything on a DC.
Could you check just what is in /var/lib/samba/sysvol and compare it
with a working samba DC. I added a DC to my domain and had problems with
sysvol and you could have the same problem.
Also what OS are you using and what version of samba4
Rowland
More information about the samba
mailing list