All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Lantschner <ingo.lists@vum.at>
To: nfs@lists.sourceforge.net
Subject: udp port sunrpc unreachable
Date: Thu, 02 Feb 2006 10:21:14 +0100	[thread overview]
Message-ID: <drsiub$vok$1@sea.gmane.org> (raw)

Hi all,
I have a propably simple problem here - but can not find a solution:
NFS-Client wslisi should mount a directory from NFS-Server wsvideo. 
Potmaper und nfs-common are installed on both machines. The server has 
nfs-kernel-server installed:
-------------------------------------------------------------------------
wsvideo$ env LANG=C dpkg -l nfs*
...
un  nfs-client                       <none>
ii  nfs-common                       1.0.6-3.1ubuntu1
ii  nfs-kernel-server                1.0.6-3.1ubuntu1
--------------------------------------------------------------------------

But I still can not connect - tcpdump says that port 111 (sunrpc) is not 
reachable:
-------------------------------------------------------------------------
# tcpdump -t not port 22
IP wslisi.696 > wsvideo.sunrpc: S 727126627:727126627(0) win 5840 <mss 
1460,sackOK,timestamp 2256871 0,nop,wscale 2>
IP wsvideo.sunrpc > wslisi.696: R 0:0(0) ack 727126628 win 0
IP wslisi.697 > wsvideo.sunrpc: UDP, length: 56
IP wsvideo > wslisi: icmp 92: wsvideo udp port sunrpc unreachable
IP wsvideo.32803 > fw.domain:  29191+ PTR? 13.4.168.192.in-addr.arpa. (43)
IP wslisi.698 > wsvideo.sunrpc: S 724474935:724474935(0) win 5840 <mss 
1460,sackOK,timestamp 2256872 0,nop,wscale 2>
IP wsvideo.sunrpc > wslisi.698: R 0:0(0) ack 724474936 win 0
IP fw.domain > wsvideo.32803:  29191* 1/0/0 (64)
IP wsvideo.32803 > fw.domain:  29192+ PTR? 12.4.168.192.in-addr.arpa. (43)
IP fw.domain > wsvideo.32803:  29192* 1/0/0 (63)
IP wsvideo.32803 > fw.domain:  29193+ PTR? 254.4.168.192.in-addr.arpa. (44)
IP fw.domain > wsvideo.32803:  29193* 1/0/0 (60)
arp who-has wsvideo tell wslisi
arp reply wsvideo is-at 00:0c:76:71:02:09
arp who-has fw tell wsvideo
arp reply fw is-at 00:4f:4e:05:d1:bd
--------------------------------------------------------------------------

netstat sees tcp open:

--------------------------------------------------------------------------
$ env LANG=C netstat -an | grep 111
tcp        0      0 127.0.0.1:111           0.0.0.0:*           LISTEN
udp        0      0 127.0.0.1:111           0.0.0.0:*
--------------------------------------------------------------------------

Any idea? TIA Ingo.



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2006-02-02  9:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-02  9:21 Ingo Lantschner [this message]
2006-02-02 14:31 ` udp port sunrpc unreachable Trond Myklebust
2006-02-02 15:19   ` J. Bruce Fields
2006-02-02 15:25     ` Trond Myklebust
2006-02-02 15:29       ` J. Bruce Fields
2006-02-02 15:36         ` Trond Myklebust
2006-02-02 18:25           ` SOLVED: " Ingo Lantschner
2006-02-03 15:53             ` Ingo Lantschner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='drsiub$vok$1@sea.gmane.org' \
    --to=ingo.lists@vum.at \
    --cc=nfs@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.