Path: number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.co   
   !wns14feed!worldnet.att.net!164.128.36.58!news.ip-plus.net!newsf   
   ed.ip-plus.net!news-zh.switch.ch!switch.ch!solnet.ch!solnet.ch!n   
   wsfeed.freenet.de!border2.nntp.ams.giganews.com!nntp.giganews.co   
   !sn-xt-ams-06!sn-xt-ams-04!sn-ams!sn-feed-ams-02!sn-post-ams-01!   
   n-post-sjc-01!supernews.com!corp.supernews.com!not-for-mail   
   From: Michael Hopkins    
   Newsgroups: alt.os.linux.ubuntu   
   Subject: Re: NFS server broken by 6.10 upgrade   
   Date: Wed, 21 Feb 2007 14:47:10 +0000   
   Organization: Posted via Supernews, http://www.supernews.com   
   Message-ID:    
   User-Agent: Microsoft-Entourage/11.3.3.061214   
   CC: Daniel Tr=?ISO-8859-1?B?/A==?=mper    
   Thread-Topic: NFS server broken by 6.10 upgrade   
   Thread-Index: AcdVxypOaSndzMG6EduEwgAX8gBuJA==   
   References:    
   <45D9D110.7040001@gmx.de>  <45DABAF1.3090504@gmx.de>   
   In-Reply-To: <45DABAF1.3090504@gmx.de>   
   Posted-And-Mailed: yes   
   Mime-version: 1.0   
   Content-type: text/plain; charset="UTF-8"   
   Content-transfer-encoding: 8bit   
   X-Complaints-To: abuse@supernews.com   
   Lines: 64   
   Xref: number1.nntp.dca.giganews.com alt.os.linux.ubuntu:10815   
      
   On 20/2/07 09:10, in article 45DABAF1.3090504@gmx.de, "Daniel Trümper"   
    wrote:   
      
   > -----BEGIN PGP SIGNED MESSAGE-----   
   > Hash: SHA1   
   >    
   > Hi Michael,   
   >    
   >> How do I diagnose and/or change this?   
   > try something like "$ netstat -natp". There you will see which ports are   
   > listening and which process is behind it.   
   >    
   >> I have set static ports for the various NFS daemons and matched those to the   
   >> firewall on both client and server.  The ports I set them to were confirmed   
   >> in Œrpcinfo ­p¹. Also, turning both firewalls off completely makes no   
   >> difference.   
   > Hm. You should have a file called something like "/etc/modules.d/lockd"   
   > with content similar to   
   >    
   > - --snip--   
   > options lockd nlm_udpport=4001 nlm_tcpport=4001   
   > - --snap--   
   >    
   > Do you have in your menu.lst a line similar to   
   >    
   > - --snip--   
   > # kopt=[...] lockd.udpport=4001 lockd.tcpport=4001   
   > - --snap--   
   >    
   > Note that the line actually is a comment. Do the daemons   
   > {portmap,nfsd,statd,lockd,mountd} all have a fixed portnumber? If there   
   > is a "random" in rpcinfo this might be the problem.   
   >    
   >> Searching on Ubuntu forums with ŒNFS 6.10¹ it appears that I am not alone.   
   > Yeah, I saw some. Several where having the problem with the fixed ports   
   > I think. Actually I am running my server on dapper so I cannot say if   
   > the packet itself is broken but I doubt that...   
   >    
   > Cheers,   
   > Daniel   
      
   Well it appears that the problem is only on nfs-kernel-server.  If I install   
   nfs-user-server then all is well.  Should I report this as a bug?   
      
   Also, a new problem is: I'm not sure if I can tie down the mountd ports with   
   nfs-user-server (unless someone knows how?  /etc/services doesn't appear to   
   help and trying to call --port XXX in the /etc/init.d/ startup script   
   doesn't work either) so it means adjusting two firewalls on every server   
   restart - grrrrr...   
      
   M   
      
      
   _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/   
      
           _/    _/   _/_/_/             Hopkins Research Ltd   
          _/    _/   _/    _/   
         _/_/_/_/   _/_/_/          http://www.hopkins-research.com/   
        _/    _/   _/   _/   
       _/    _/   _/     _/               'touch the future'   
                         
   _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/   
      
   --- Platinum Xpress/Win/WINServer v3.0pr5   
    * Origin: Omicron Theta BBS (1:261/20)