Zhang Weiwu 写道:
> John Andersen 写道:
>
>> On Sunday 08 April 2007, Zhang Weiwu wrote:
>>
>>
>>
>>> Apr 9 15:46:47 joe mountd[17301]: refused mount request from
>>> 218.193.55.201 for /home (/): not exported Apr 9 15:46:57 joe
>>> mountd[17301]: can't get hostname of 218.193.55.201
>>>
>>> This is the first time I see mount failed because reverse DNS lookup
>>> failed. My dumb questions are:
>>>
>>> 1. If reverse lookup had been a must, why I hadn't have this problem
>>> with Linux clients?
>>> 2. Can I turn off reverse lookup on the DNS server? It's impossible
>>> for me to set up reverse lookup because client is not in the
>>> network managed by me and I don't see how reverse lookup offered
>>> better security: because I only export read-only shares!
>>>
>>>
>> Looks to me like windows was trying to mount /home instead
>> of '/home/packman' and that is what it is complaining about.
>>
>>
> I thought the same but later I read this article
> http://support.microsoft.com/kb/926095
> Seems MS is aware of this.
>
>> Did you try to add 218.193.55.201 to hosts file?
>>
> Why? But anyway I added this line to my /etc/hosts
> 218.193.55.201 abcdefg
>
> strange, after I added this line to /etc/hosts there is no longer error
> message in /var/log/messages. But still Windows client cannot connect.
> Some times, the Windows client ask for a username and password, because
> this is anonymous share I don't know what to fill in, typed several
> username like 'guest' 'anonymous' and finally some real username and
> password: no access. Press "ESC" to get rid of login dialog, trying
> connect to NFS share again got "Network Path Not Found" error from
> Windows client. During all these, no error messages produced in
> /var/log/messages.
>
> If the MS KB article had been right, that "Some NFS servers require
> valid PTR records as part of the security mechanism." Then why all other
> Linux hosts in the same local network (e.g. 218.193.55.200,
> 218.193.55.202...) mounts just fine?
>
A little bit of progress as I digging through documents: This is quote
from nfs.sf.net
Acquire and install a recent distribution of Linux. To enable NLM
lock recovery, ensure your client's host name, as returned by uname
-n, matches the host name returned by DNS.
So, hostname reverse lookup is needed if NLM lock recovery is enabled.
So, perhaps Linux NFS clients do not enable NLM by default and Windows
clients do.
I wouldn't be surprised if MS Product don't let me switch NLM on and off
because in general MS products are not tweak-able without 3rd party
software. Well after I start NFS client administration (mmc) on Windows,
there is no option for NLM.
So, I tried to add no_auth_nlm option to /etc/exports... no use. Same
old behavior.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
