I had the same sporadic error when I first installed my WAN.
I ended up blowing up and replacing the WAP (don't ask) and that fixed it.
Prior to the WAP swap (the new came with later firmware), file copies would
persistently fail with such an error after 4 - 6 GB / randomly.
I did a lot of testing, a few hundred GB to make sure it was stable. I was
not goin to put in a dodgy WAP as my intention was to put the server down in
the garage and didn't want to have to go down there to kick anything -
particularly on a monitorless server.
So, check the firmware on all WAN devices and upgrade judiciously. Check
your drivers. Look for a combo that works and another that does not to
locate the device in the network that fails (EG try removing the WAP from
the picure to test individual cards). Others have reported WEP is not stable
on some devices, so try WAP even though it is slower.
HTH
- Tim
"Ric" <(E-Mail Removed)> wrote in message
news:43288267$0$17217$(E-Mail Removed)...
>
>
>
>>
>> No write access set?
>>
> If you mean the write access in shared properties - yes it is set.
>
> But good news - I have figured this out. Although it was ticked, it
> appears that it was not really set. Unticking, confirming the untick,
> reticking and confirming again has fixed the problem. It is a mystery why
> this ever happened though - everything has worked fine for the past year!
>
|