Path: number1.nntp.dca.giganews.com!border1.nntp.dca.giganews.co   
   !nntp.giganews.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-o   
   line.de!t-online.de!fu-berlin.de!uni-berlin.de!not-for-mail   
   From: =?UTF-8?B?RGFuaWVsIFRyw7xtcGVy?=    
   Newsgroups: alt.os.linux.ubuntu   
   Subject: Re: NFS server broken by 6.10 upgrade   
   Date: Tue, 20 Feb 2007 10:10:09 +0100   
   Lines: 44   
   Message-ID: <45DABAF1.3090504@gmx.de>   
   References:    
   <45D9D110.7040001@gmx.de>    
   Mime-Version: 1.0   
   Content-Type: text/plain; charset=UTF-8   
   Content-Transfer-Encoding: 8bit   
   X-Trace: news.uni-berlin.de wsOM3xW84DebNZ0L/QEf2g8znC8p6+ktdhKuEFvxk0vFpqjDo=   
   User-Agent: Thunderbird 1.5.0.9 (X11/20070103)   
   In-Reply-To:    
   X-Enigmail-Version: 0.94.1.1   
   Xref: number1.nntp.dca.giganews.com alt.os.linux.ubuntu:10729   
      
   -----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   
   -----BEGIN PGP SIGNATURE-----   
   Version: GnuPG v1.4.3 (GNU/Linux)   
      
   iD8DBQFF2rrxtaNKlGovncgRAv/KAKCibad3YINSyGls8T6rrA5RHe2laQCbBg7j   
   z60zjDdlnV2sgQLu0Zwyifk=   
   =eVyi   
   -----END PGP SIGNATURE-----   
   --- Platinum Xpress/Win/WINServer v3.0pr5   
    * Origin: Omicron Theta BBS (1:261/20)