Re: suse 9.1 nfs: not tcp available

From: Michael W. Cocke (cocke_at_catherders.com)
Date: 06/05/04 

Date: Sat, 05 Jun 2004 11:18:07 -0400

On Thu, 03 Jun 2004 17:46:01 -0400, Arthur Hagen <art@broomstick.com>
wrote:

>Jens Kluge wrote:
>
>> Hi folks,
>> Whenever starting SuSE Linux 9.1 I get the following boot.msg:
>> .
>> .
>> Importing Net File System (NFS) nfs server reported
>> nfs server reported tcp not available, falling back to udp
>> 3 times)
>> done
>> .
>> .
>>
>> Already installed samba uprade from Suse which helped me to make smb/
>> work. Nevertheless this did not help to discard the message above
>>
>> Any ideas????
>
>Did you by any chance enable SuSEfirewall2?
>NFS needs access to port 111 and 2049 (in addition to ports negotiated
>through RPC).
>
>Regards,

The original message never showed up here, so please excuse the
confused quotes. The following is to the original poster.

Did you actually read the error message? That plus the man page for
nfs will tell you exactly what happened.

"Many NFS servers do not support tcp. In those cases, the transport
protocol falls back to udp". (A very close paraphrase of what the man
page says).

Has nothing to do with firewalls, samba, portmap, rpc, or the phase of
the moon. If you have an NFS server somewhere that DOES support tcp
(Suse 9.1 happens to), you can connect using tcp. If you don't want
to see the error message when connecting to a server that doesn;t
support tcp, add 'udp' to your fstab.

Mike- 

--
If you're not confused, you're not trying hard enough.
--
Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com.  If
email from you bounces, try non-HTML, non-encoded, non-attachments,
----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---