NFS issue - Suse

This is a discussion on NFS issue - Suse ; I'd like to use SuSE 10.3 as an NFS server, although I don't have any experience with this application (none?). Yast provides for the setup of a NFS server, but perhaps a static IP is desirable, in view of the ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: NFS issue

  1. NFS issue

    I'd like to use SuSE 10.3 as an NFS server, although I don't have any
    experience with this application (none?). Yast provides for the setup
    of a NFS server, but perhaps a static IP is desirable, in view of the
    fact that the clients' fstab is supposed to include a line something
    like this:

    :/home /mnt/home nfs rw 0 0

    (The client of course is possibly not a SuSE installation, so the
    above method is generally applicable.) In any case, should be
    the same every time. Currently the server-to-be obtains an IP address
    from a 2wire 2700HG-D "Internet gateway" by DHCP. However, when I
    modify the setting of the (sole) network card for a static IP address,
    it no longer connects to the Internet (therefore, the card presumably
    isn't functioning with a static address).

    I note that it is possible to assign an "alias" to a network card, so
    perhaps this is a way to obviate the problem? The alias address could
    be used in fstab instead of the possibly changing address assigned by
    DHCP? Any advice would be appreciated.

  2. Re: NFS issue

    On Thu, 03 Jan 2008 15:25:33 -0800, tim1948 wrote:

    > I'd like to use SuSE 10.3 as an NFS server


    Do you want the NFS server to be seen

    a) only to other machines on your LAN, or
    b) only to external Internet sites, or
    c) to both machines on your LAN and to external Internet sites?

    Presumably your intention is only option (a)?

    In that case the best way to proceed is to have the machine configured
    as the NFS server to have a fixed internal private network IP (either class
    A [10.0.0.0 - 10.255.255.255], class B [172.16.0.0 - 172.31.255.255], or
    class C [192.168.255.0 - 192.168.255.255], with class C being the
    preferred choice for small networks) and the other machines on your
    LAN being assigned appropriate IPs within the same network.

    If you insist on assigning this IP by DHCP rather than statically in
    your /etc/sysconfig/network/ manipulated by YaST, then perhaps you can
    tell your 2Wire internet gateway to always assign the chosen fixed IP
    to the MAC address of the network card on that machine.

    The reason presumably that you can no longer see the InterNet when you
    assign the IP addresses manually to the network card on your NFS server,
    is because you have not chosen an IP address in the same network as that
    currently assigned by your 2Wire internet gateway to its internal LAN
    port. Either you choose an IP on the NFS server for the same network
    as the factory default (if you have not changed it) for the 2Wire internet
    gateway internal LAN port, or you go into the configuration on the 2Wire
    internet gateway and change the assigned IP for the internal LAN port.

    Assuming a Class C network configuration, here is a suggestion for
    allocating IP networks on your LAN

    2Wire internet gateway internal port -- 192.168.1.1
    NFS server machine 192.168.1.11
    other machine on LAN 192.168.1.12
    another machine on LAN 192.168.1.13

    You should be able to configure your 2Wire internet gateway to
    automatically allocate the other machines IPs by the DHCP method,
    specifying a DHCP range to be allocated from say 192.168.1.12 -
    192.168.1.up_to_253_maximum

    The choice of the IP's is up to you, but they all need to be on the
    same Class C network otherwise your machines will not be able to see
    each other or talk to the gateway to get to the internet.

    The way to test the connection is to use ping IP_number or
    ping host_name (the latter provided you have the host_name and IP_number
    in /etc/hosts or DNS properly configured).

    Hope this helps.

  3. Re: NFS issue

    tim1948 wrote:

    > (The client of course is possibly not a SuSE installation, so the
    > above method is generally applicable.) In any case, should be
    > the same every time. Currently the server-to-be obtains an IP address
    > from a 2wire 2700HG-D "Internet gateway" by DHCP. However, when I
    > modify the setting of the (sole) network card for a static IP address,
    > it no longer connects to the Internet (therefore, the card presumably
    > isn't functioning with a static address).


    Server with changing IP is never a good idea. Better try to make the
    gateway assign static IPs.

    If *really* not possible, then set the DHCP lease time (period in which
    the same IP is reserved for a specific network card) to a very high
    level. But that's just a workaround...

    Cheerz Lars


  4. Re: NFS issue

    tim1948 wrote:

    Hi Tim,
    I'm having trouble with NFS also. I have a mixed LAN with OpenSUSE 10.3,
    Ubuntu and Windows. I use Samba for windows which is working. But I too
    am having trouble with NFS. I have one box on DHCP and two with static
    IP addresses. (I haven't gotten into my smoothwall setup to add the
    3rd). But despite whether I try to mount a share using Yast NFS Client
    from a static or dynamic IP address I get the following error message:
    "Unable to mount NFS entries from /etc/fstab". I've been googling around
    to try and find a cure but no luck yet. I sometimes can get the share to
    mount and it shows the folders but won't let me access (even see)
    subfolders or files in that folder.

    If I get anywhere with it I'll repost. But so far, I'm running my head
    against the wall. I figure it is a user/password/permissions issue but
    haven't figured out how to correct it. And why it won't mount from fstab
    is beyond me.

    Good luck,
    Tom

+ Reply to Thread