[Samba] Computer can't access Sysvol

John Cobley john.cobley at comtek.co.uk
Wed Jul 1 06:36:09 MDT 2015

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

More information about the samba mailing list