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 directoryIt 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
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 CobleyThe problem here isn't sysvol, it's 'usershares', is there anything in your smb.conf referring to 'usershares' ? Rowland
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 >