[Samba] Windows 2008 Standard SP2 cannot access samba share by hostname but ok with IP

Jerome Yanga jerome.yanga at gmail.com
Fri Oct 18 15:32:58 MDT 2013


I found the solution to the file lock issue.

I simply disabled "strict locking".

I hope somebody else out there will be helped with this knowledge.

Thank you for the support.

regards,
j


On Tue, Oct 15, 2013 at 7:15 AM, Jerome Yanga <jerome.yanga at gmail.com>wrote:

> bump :)
>
>
> On Fri, Oct 11, 2013 at 8:21 AM, Jerome Yanga <jerome.yanga at gmail.com>wrote:
>
>> Greg,
>>
>> I do understand and I have done my homework with regards to the file lock
>> even before I posted here.  I apologize for not providing all the info all
>> at once.  I find that if I do, a lot is missed so I provide as it becomes
>> pertinent.
>>
>> In performing my test, I created another share identical to what you see
>> above and made sure that no one else is connected to it.  I simply dragged
>> and dropped a file from a Windows 7 to the share and I got error 0x80070021
>> on the following cases.
>>
>> 01)  copying a new file into the share
>> 02)  overwriting an existing file
>>
>> Creating a new file does not seem to show this issue--as expected.
>>
>> Like you, I also appreciate how much Rowland has helped me.  I have been
>> on that end of the line before and I know the hard work and patience it
>> needs.
>>
>> regards,
>> j
>>
>>
>>
>> On Fri, Oct 11, 2013 at 8:09 AM, Gregory Sloop <gregs at sloop.net> wrote:
>>
>>>
>>>
>>> JY> Rowland,
>>>
>>> JY> I did see those from my searches as well.  However, this samba
>>> JY> configuration worked prior to migrating it to RHEL and into a more
>>> current
>>> JY> samba.
>>>
>>> JY> regards,
>>> JY> j
>>>
>>> >>
>>> >>
>>> >>  HI Jerome, '0x80070021' is a windows error and the most likely cause
>>> >> would seem to be trying to copy a users .pst file whilst outlook is
>>> still
>>> >> running, try doing a web search on the error.
>>> >>
>>> >> Rowland
>>> >>
>>>
>>> But that doesn't address Rowland's point at all. Are you sure this file
>>> isn't in use, even if it might have "worked" before?
>>>
>>> It seems pretty dismissive, IMO, to simply say "it worked before."
>>>
>>> [I've seen Rowland spend an enormous amount of time recently trying to
>>> help people, and in several cases it seems the person getting helped
>>> isn't putting in nearly as much effort as I'd expect. I'm not saying
>>> it's that way in this case - but IMO, you need to address the "Is this
>>> file open and that's the cause of the error?"]
>>>
>>> But perhaps I'm just feeling cranky this morning. :)
>>>
>>> ---
>>> ...And I have to say, 'Man Rowland, you and Steve have gone way above
>>> and beyond in spending time and effort helping.' You guys make
>>> community software rock!
>>>
>>> -Greg
>>>
>>>
>>
>


More information about the samba mailing list