Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 8 of 8 total
Thread Windows LAN
Thu, Jan 28 2016 9:40 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

I'm hoping there's someone here who's suffered this and can tell me the way out.

Small home network - 4 PCs (3xW7x64, 1xW10x32) mixture of wired & wireless.

Sometimes I can't create a file on one of the PCs, generally mine (\\OPTIMUS). I know it must have something to do with security / privileges but I have everything set to allow everyone to do everything.

I haven't yet hit the right phrase with Google.

Any help that has a chance of working gracefully received - even Mathews <VBG>


Roy Lambert
Thu, Jan 28 2016 10:01 AMPermanent Link

Matthew Jones

Roy Lambert wrote:

> Sometimes

This is rather unspecific. Is it repeatable, just a specific share, a
specific directory, or what? The key is that there are two things that
give permission, the share, and the folder(s). And be sure to select
the Advanced button in permissions and tell it to set this permission
on sub-folders and files too.

Apart from that, I think more detail is needed. Does a retry work? Does
it stop working for ages and then work? Does it work with a different
name? What AV do you have running?

Sorry, not an instant solution, but perhaps better than this "Mathew"
chap (who is this person with only one 't' in his name I wonder. 8-)

--

Matthew Jones
Thu, Jan 28 2016 11:00 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Matthew

>This is rather unspecific. Is it repeatable, just a specific share, a
>specific directory, or what? The key is that there are two things that
>give permission, the share, and the folder(s). And be sure to select
>the Advanced button in permissions and tell it to set this permission
>on sub-folders and files too.

Sometimes means today none of the other PCs can write to \\OPTIMUS, or delete an existing file, but \\OPTIMUS can do what it likes to them.

\\OPTIMUS is the latest machine and its the only one with SSD. I have no idea if that's significant. I'm setting up a tablet for someone just now so I'm going to do more playing later

>Apart from that, I think more detail is needed. Does a retry work? Does
>it stop working for ages and then work? Does it work with a different
>name? What AV do you have running?

Part of the problem is that if I had an idea of what detail to look for I'd probably find the solution. I seem to specialise in things that are intermittent, and hard to locate Frown

I have AVG & MBAM on all machines

Thanks

Roy
Fri, Jan 29 2016 3:40 AMPermanent Link

Matthew Jones

I can only suggest looking at the events record on each and seeing if
there is something there. Check that the clocks are in sync, as that is
a common problem - too far adrift and the protocols can't work.


--

Matthew Jones
Fri, Jan 29 2016 8:39 AMPermanent Link

Raul

Team Elevate Team Elevate

On 1/28/2016 9:40 AM, Roy Lambert wrote:
> I'm hoping there's someone here who's suffered this and can tell me the way out.
> Small home network - 4 PCs (3xW7x64, 1xW10x32) mixture of wired & wireless.
> Sometimes I can't create a file on one of the PCs, generally mine (\\OPTIMUS). I know it must have something to do with security / privileges but I have everything set to allow everyone to do everything.

I would the newer SMB protocols here. Window7 i believe introduced SMBv2
and Win8 (Win10 in your case) also has SMBv3.

I myself have found that mapping an actual drive sometimes works better
than accessing it using UNC share name.

Outside of that you can google for SMB settings and either change them
or even possibly try disabling newer protocols (for example disable
SMBv3 on win10 so then i think everything in your lan should talk SMBv2
or even go as far as disable SMBv2 and SMBv3 both abd default to SMBv1).

Raul
Sat, Jan 30 2016 6:38 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Raul


>I would the newer SMB protocols here. Window7 i believe introduced SMBv2
>and Win8 (Win10 in your case) also has SMBv3.

Interesting suggestion - I'll have a look.

Roy
Sat, Jan 30 2016 6:38 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Matthew

>I can only suggest looking at the events record on each and seeing if
>there is something there. Check that the clocks are in sync, as that is
>a common problem - too far adrift and the protocols can't work.

For some reason I never think of looking at the Windows logs. Once I've finished the messing around changing telecoms suppliers has caused I'll investigate.

Roy
Tue, Feb 2 2016 11:23 AMPermanent Link

Roy Lambert

NLH Associates

Team Elevate Team Elevate

Found it and yes it was permissions. I'd been looking in security and had forgotten there were additional permissions in sharing (thank you microsoft). How and why they change I don't know, but I now know what to look for and if I can spot the culprit I can give it a good kicking, if not at least I can fix it.

Roy Lambert
Image