ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    NIS and NFS and YP in Ubuntu Server 14.04

    IT Discussion
    linux ubuntu nis nfs unix
    3
    29
    12.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • scottalanmillerS
      scottalanmiller
      last edited by

      I edited your posts for readability.

      1 Reply Last reply Reply Quote 0
      • scottalanmillerS
        scottalanmiller
        last edited by

        You are getting way too deep when your errors are very shallow. Right now it looks like NIS isn't running yet:

        oot@ubuntu:~# ypwhich
        ypwhich: Can't communicate with ypbind
        root@ubuntu:~# ypcat passwd
        No such map passwd.byname. Reason: Can't bind to server which serves this domain
        

        Before you are doing all of this.... just look and see if NIS is running. Just this command on your NIS server:

        netstat -tulpn
        
        1 Reply Last reply Reply Quote 0
        • Reid CooperR
          Reid Cooper
          last edited by

          Or query the NIS service and ask it if it is running.

          1 Reply Last reply Reply Quote 1
          • Reid CooperR
            Reid Cooper
            last edited by

            Have firewall ports been opened for RPCBIND and whatever else is needed?

            1 Reply Last reply Reply Quote 1
            • LakshmanaL
              Lakshmana
              last edited by Lakshmana

              How to open ports for the NIS and NFS in iptables?
              I have followed the below to link configure for the NIS configurattion now.

              https://help.ubuntu.com/community/SettingUpNISHowTo

              But I was not able to open the ports I have given in the website

              I have also installed the iptables-persistent in the ubuntu server but the default path to edit rules was not able to identify.

              When I use the rules for the port I have opened means the error coming here is
              Bad Argument"IP"

              scottalanmillerS 2 Replies Last reply Reply Quote 0
              • scottalanmillerS
                scottalanmiller @Lakshmana
                last edited by

                @Lakshmana said:

                How to open ports for the NIS and NFS in iptables?

                Same way as the other times you opened ports in iptables. Just change the port numbers. For now, while you are trying to figure things out, just turn iptables off.

                1 Reply Last reply Reply Quote 1
                • scottalanmillerS
                  scottalanmiller @Lakshmana
                  last edited by

                  @Lakshmana said:

                  When I use the rules for the port I have opened means the error coming here is
                  Bad Argument"IP"

                  Instead of describing the issue in cases like this, supply the screen shot or a copy/paste of the commands that fail and the error. In almost all cases it's just a typo or missed argument. In every case we will ask you to do this. So instead of making us ask, just start by providing the information so we can assist more quickly.

                  1 Reply Last reply Reply Quote 0
                  • LakshmanaL
                    Lakshmana
                    last edited by

                    Configured Properly and now it is working

                    1 Reply Last reply Reply Quote 0
                    • Reid CooperR
                      Reid Cooper
                      last edited by

                      What was wrong?

                      1 Reply Last reply Reply Quote 0
                      • LakshmanaL
                        Lakshmana
                        last edited by

                        I have not mentioned the server at /etc/hosts and ypbind does not happen because of this option the whole setup has issue.

                        1 Reply Last reply Reply Quote 0
                        • Reid CooperR
                          Reid Cooper
                          last edited by

                          I am guessing that you do not have all of your servers listed in DNS and that might be causing the problem requiring /etc/hosts to have an entry?

                          1 Reply Last reply Reply Quote 0
                          • Reid CooperR
                            Reid Cooper
                            last edited by

                            You can use IP addresses in your configuration files too, instead of hostnames if you are lacking DNS.

                            1 Reply Last reply Reply Quote 0
                            • LakshmanaL
                              Lakshmana
                              last edited by

                              OK.

                              1 Reply Last reply Reply Quote 0
                              • 1
                              • 2
                              • 2 / 2
                              • First post
                                Last post