On Monday 09 April 2007 12:38:05 Zhang Weiwu wrote: > Anders Johansson 写道: > > On Monday 09 April 2007 09:49, Zhang Weiwu wrote: > >> joe:/home/zhangweiwu # cat /etc/exports > >> /home/packman/ *(ro,no_subtree_check,insecure,sync) > > > > Don't use * as a wildcard in /etc/exports. It says explicitly in the > > documentation that this can happen. * requires reverse DNS. > > Hell, which document?? man exports even didn't mentioned the word > "reverse" nor 'DNS'
No, but in the section "wildcards" it clearly states that * matches host- and domain names, not IP addresses. And if that is going to work, you have to have reverse lookup configured and working > > > If you don't want to have reverse DNS, use IP notation 0.0.0.0/0.0.0.0 > > instead. > > strangely, even if I use 0.0.0.0/0.0.0.0 (and restart nfs) I still > cannot connect, behavior: > > If I use 0.0.0.0/0.0.0.0 in place of wildcard (*), 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 but still 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. I don't know. There is no authentication in NFSv3, so I can only assume that you are doing something wrong on the windows side. 0.0.0.0/0.0.0.0 means "allow everyone" -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
