(SuSE Linux 9.3 Pro) I'm trying to set up a Linux-only network to use the Network File System (NFS). The description of NFS sounds like just what I need but I'm having problems trying to set up an NFS server. I've seen the note in the SuSE admin manual stating that I need to have a DNS so I decided to try to set that up first. YaST says I need something called a "forwarder". My first problem. I have no idea what a forwarder is and referencing the SuSE admin manual was no help. Can someone explain to me what a "forwarder" is? Some other questions. I assume that DNS requires static IP addresses. Is that true? If so, how can I reconcile that with DHCP? If not, how do I tell DNS that I'm using DHCP? In short... I am completely lost in the terminology and processes needed to set up NFS. Can someone point me to a starting point and give me a few pointers on how to proceed. I will sincerely appreciate any assistance. -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Sunday 24 Jul 2005 19:23, Donald D Henson wrote:
(SuSE Linux 9.3 Pro)
I'm trying to set up a Linux-only network to use the Network File System (NFS). The description of NFS sounds like just what I need but I'm having problems trying to set up an NFS server.
I've seen the note in the SuSE admin manual stating that I need to have a DNS so I decided to try to set that up first.
You don't need a DNS unless you are using hostnames to specify exports. I only have local name resolution by /etc/hosts and it works fine.
YaST says I need something called a "forwarder". My first problem. I have no idea what a forwarder is and referencing the SuSE admin manual was no help. Can someone explain to me what a "forwarder" is?
A DNS forwarder simply passes the DNS requests out to an external DNS server.
Some other questions. I assume that DNS requires static IP addresses. Is that true?
No, the dhcp server can be configured to update the DNS records, but it's probably too much hard work for a small network.
If so, how can I reconcile that with DHCP?
You can tell dhcp to always assign the same IP to a specific MAC which effectively means each client always has the same address.
If not, how do I tell DNS that I'm using DHCP? In short...
I am completely lost in the terminology and processes needed to set up NFS. Can someone point me to a starting point and give me a few pointers on how to proceed. I will sincerely appreciate any assistance.
Keep it simple first. export a single directory to your whole network (specified by subnet IP address) and try to mount it from a client. For example, I have (approximately): in /etc/exports on the server (gandalf): /srv/nfs/data 192.168.0.0/24(rw,root_squash,no_all_squash,sync) and in /etc/fstab on the clients: gandalf:/srv/nfs/data /media/server/data nfs defaults 0 0 which mounts the remote fs when the client boots. HTH Dylan -- "The man who strikes first admits that his ideas have given out." (Chinese Proverb)
Using your comments and the reference provided by Paul, I was able to set up an NIS server and export a directory. It all appeared to be working correctly. I entered the host name of a client machine, linux. When I try to access the exported directory, I get an error message that the host cannot be found. I'm sure that what I've said above is insufficient data. Can you either see what I'm doing wrong or ask some clarifying questions? Don Henson Dylan wrote:
On Sunday 24 Jul 2005 19:23, Donald D Henson wrote:
(SuSE Linux 9.3 Pro)
I'm trying to set up a Linux-only network to use the Network File System (NFS). The description of NFS sounds like just what I need but I'm having problems trying to set up an NFS server.
I've seen the note in the SuSE admin manual stating that I need to have a DNS so I decided to try to set that up first.
You don't need a DNS unless you are using hostnames to specify exports. I only have local name resolution by /etc/hosts and it works fine.
YaST says I need something called a "forwarder". My first problem. I have no idea what a forwarder is and referencing the SuSE admin manual was no help. Can someone explain to me what a "forwarder" is?
A DNS forwarder simply passes the DNS requests out to an external DNS server.
Some other questions. I assume that DNS requires static IP addresses. Is that true?
No, the dhcp server can be configured to update the DNS records, but it's probably too much hard work for a small network.
If so, how can I reconcile that with DHCP?
You can tell dhcp to always assign the same IP to a specific MAC which effectively means each client always has the same address.
If not, how do I tell DNS that I'm using DHCP? In short...
I am completely lost in the terminology and processes needed to set up NFS. Can someone point me to a starting point and give me a few pointers on how to proceed. I will sincerely appreciate any assistance.
Keep it simple first. export a single directory to your whole network (specified by subnet IP address) and try to mount it from a client. For example, I have (approximately):
in /etc/exports on the server (gandalf): /srv/nfs/data 192.168.0.0/24(rw,root_squash,no_all_squash,sync)
and in /etc/fstab on the clients: gandalf:/srv/nfs/data /media/server/data nfs defaults 0 0
which mounts the remote fs when the client boots.
HTH Dylan
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
Please reply on list so others with similar problems can read the solutions... On Sunday 24 Jul 2005 22:57, you wrote:
Using your comments and the reference provided by Paul, I was able to set up an NIS server and export a directory. It all appeared to be working correctly.
OK, what are you using the NIS server for?
I entered the host name of a client machine, linux.
Where did you enter this?
When I try to access the exported directory, I get an error message that the host cannot be found. I'm sure that what I've said above is insufficient data. Can you either see what I'm doing wrong or ask some clarifying questions?
Can you send the contents of /etc/exports from the server and either /etc/fstab from the client or the command you typed to mount the nfs export? Dylan -- "The man who strikes first admits that his ideas have given out." (Chinese Proverb)
First step try ping linux from your client. If you can not ping the server or resolve the name you have a problem either on your dns or your NIS host tables or your host tables. Donald D Henson wrote:
Using your comments and the reference provided by Paul, I was able to set up an NIS server and export a directory. It all appeared to be working correctly. I entered the host name of a client machine, linux. When I try to access the exported directory, I get an error message that the host cannot be found. I'm sure that what I've said above is insufficient data. Can you either see what I'm doing wrong or ask some clarifying questions?
Don Henson
Dylan wrote:
On Sunday 24 Jul 2005 19:23, Donald D Henson wrote:
(SuSE Linux 9.3 Pro)
I'm trying to set up a Linux-only network to use the Network File System (NFS). The description of NFS sounds like just what I need but I'm having problems trying to set up an NFS server.
I've seen the note in the SuSE admin manual stating that I need to have a DNS so I decided to try to set that up first.
You don't need a DNS unless you are using hostnames to specify exports. I only have local name resolution by /etc/hosts and it works fine.
YaST says I need something called a "forwarder". My first problem. I have no idea what a forwarder is and referencing the SuSE admin manual was no help. Can someone explain to me what a "forwarder" is?
A DNS forwarder simply passes the DNS requests out to an external DNS server.
Some other questions. I assume that DNS requires static IP addresses. Is that true?
No, the dhcp server can be configured to update the DNS records, but it's probably too much hard work for a small network.
If so, how can I reconcile that with DHCP?
You can tell dhcp to always assign the same IP to a specific MAC which effectively means each client always has the same address.
If not, how do I tell DNS that I'm using DHCP? In short...
I am completely lost in the terminology and processes needed to set up NFS. Can someone point me to a starting point and give me a few pointers on how to proceed. I will sincerely appreciate any assistance.
Keep it simple first. export a single directory to your whole network (specified by subnet IP address) and try to mount it from a client. For example, I have (approximately):
in /etc/exports on the server (gandalf): /srv/nfs/data 192.168.0.0/24(rw,root_squash,no_all_squash,sync)
and in /etc/fstab on the clients: gandalf:/srv/nfs/data /media/server/data nfs defaults 0 0
which mounts the remote fs when the client boots.
HTH Dylan
-- Joseph Loo jloo@acm.org
You may be onto something. I cannot ping from either host to the other. (By the way, linux is the client & toshiba is the server.) For example: ping linux (from toshiba) results in error: unknown host linux I get a similar response in the other direction. Assuming that I have a problem on my DNS or my host tables, how do I determine which and, more importantly, how do I fix it. If possible, I would like to fix it using YaST but I can use the cli if necessary. Don Henson Joseph Loo wrote:
First step try ping linux from your client. If you can not ping the server or resolve the name you have a problem either on your dns or your NIS host tables or your host tables.
Donald D Henson wrote:
Using your comments and the reference provided by Paul, I was able to set up an NIS server and export a directory. It all appeared to be working correctly. I entered the host name of a client machine, linux. When I try to access the exported directory, I get an error message that the host cannot be found. I'm sure that what I've said above is insufficient data. Can you either see what I'm doing wrong or ask some clarifying questions?
Don Henson
Dylan wrote:
On Sunday 24 Jul 2005 19:23, Donald D Henson wrote:
(SuSE Linux 9.3 Pro)
I'm trying to set up a Linux-only network to use the Network File System (NFS). The description of NFS sounds like just what I need but I'm having problems trying to set up an NFS server.
I've seen the note in the SuSE admin manual stating that I need to have a DNS so I decided to try to set that up first. You don't need a DNS unless you are using hostnames to specify exports. I only have local name resolution by /etc/hosts and it works fine.
YaST says I need something called a "forwarder". My first problem. I have no idea what a forwarder is and referencing the SuSE admin manual was no help. Can someone explain to me what a "forwarder" is?
A DNS forwarder simply passes the DNS requests out to an external DNS server.
Some other questions. I assume that DNS requires static IP addresses. Is that true? No, the dhcp server can be configured to update the DNS records, but it's probably too much hard work for a small network.
If so, how can I reconcile that with DHCP? You can tell dhcp to always assign the same IP to a specific MAC which effectively means each client always has the same address.
If not, how do I tell DNS that I'm using DHCP? In short...
I am completely lost in the terminology and processes needed to set up NFS. Can someone point me to a starting point and give me a few pointers on how to proceed. I will sincerely appreciate any assistance.
Keep it simple first. export a single directory to your whole network (specified by subnet IP address) and try to mount it from a client. For example, I have (approximately):
in /etc/exports on the server (gandalf): /srv/nfs/data 192.168.0.0/24(rw,root_squash,no_all_squash,sync)
and in /etc/fstab on the clients: gandalf:/srv/nfs/data /media/server/data nfs defaults 0 0
which mounts the remote fs when the client boots.
HTH Dylan
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Monday 25 July 2005 1:56 pm, Donald D Henson wrote:
You may be onto something. I cannot ping from either host to the other. (By the way, linux is the client & toshiba is the server.) For example:
ping linux (from toshiba) results in error:
unknown host linux
I get a similar response in the other direction.
Assuming that I have a problem on my DNS or my host tables, how do I determine which and, more importantly, how do I fix it. If possible, I would like to fix it using YaST but I can use the cli if necessary.
The first thing you should try to do is to ping each system from the other
using the IP addresses. Obviously your 2 systems are not either in DNS
or /etc/host.
If you can ping successfully in both directions by IP address, which means
your routing tables are ok, the easiest way to fix is to add the systems to
your hosts files using YaST:
YaST/Network Services/Host names.
Assuming that neither Linux nor Toshiba exist in any DNS database. If they
do, then your search path may be wrong.
Let's say that you are on network foo.bar, and that linux.foo.bar and
toshiba.foo.bar are set up in DNS, you would need to set up foo.bar as your
search path either in YaST or in /etc/resolv.conf. That way ping linux
would search for linux.foo,bar and resolve it. If you don't want to mess
with DNS, just use host names.
--
Jerry Feldman
I depends on houw you want to set things up. If you have a full blown system you might want to use either DNS or NIS. The quick and easy way is to enter the machines ip address in the /etc/hosts. I just use my trusty editor and add the item in. After you do it ( you need to be root) you should be able to ping the host machine provided you setup the network sturf, i.e., netmask. Donald D Henson wrote:
You may be onto something. I cannot ping from either host to the other. (By the way, linux is the client & toshiba is the server.) For example:
ping linux (from toshiba) results in error:
unknown host linux
I get a similar response in the other direction.
Assuming that I have a problem on my DNS or my host tables, how do I determine which and, more importantly, how do I fix it. If possible, I would like to fix it using YaST but I can use the cli if necessary.
Don Henson
Joseph Loo wrote:
First step try ping linux from your client. If you can not ping the server or resolve the name you have a problem either on your dns or your NIS host tables or your host tables.
Donald D Henson wrote:
Using your comments and the reference provided by Paul, I was able to set up an NIS server and export a directory. It all appeared to be working correctly. I entered the host name of a client machine, linux. When I try to access the exported directory, I get an error message that the host cannot be found. I'm sure that what I've said above is insufficient data. Can you either see what I'm doing wrong or ask some clarifying questions?
Don Henson
Dylan wrote:
On Sunday 24 Jul 2005 19:23, Donald D Henson wrote:
(SuSE Linux 9.3 Pro)
I'm trying to set up a Linux-only network to use the Network File System (NFS). The description of NFS sounds like just what I need but I'm having problems trying to set up an NFS server.
I've seen the note in the SuSE admin manual stating that I need to have a DNS so I decided to try to set that up first.
You don't need a DNS unless you are using hostnames to specify exports. I only have local name resolution by /etc/hosts and it works fine.
YaST says I need something called a "forwarder". My first problem. I have no idea what a forwarder is and referencing the SuSE admin manual was no help. Can someone explain to me what a "forwarder" is?
A DNS forwarder simply passes the DNS requests out to an external DNS server.
Some other questions. I assume that DNS requires static IP addresses. Is that true?
No, the dhcp server can be configured to update the DNS records, but it's probably too much hard work for a small network.
If so, how can I reconcile that with DHCP?
You can tell dhcp to always assign the same IP to a specific MAC which effectively means each client always has the same address.
If not, how do I tell DNS that I'm using DHCP? In short...
I am completely lost in the terminology and processes needed to set up NFS. Can someone point me to a starting point and give me a few pointers on how to proceed. I will sincerely appreciate any assistance.
Keep it simple first. export a single directory to your whole network (specified by subnet IP address) and try to mount it from a client. For example, I have (approximately):
in /etc/exports on the server (gandalf): /srv/nfs/data 192.168.0.0/24(rw,root_squash,no_all_squash,sync)
and in /etc/fstab on the clients: gandalf:/srv/nfs/data /media/server/data nfs defaults 0 0
which mounts the remote fs when the client boots.
HTH Dylan
-- Joseph Loo jloo@acm.org
participants (4)
-
Donald D Henson -
Dylan -
Jerry Feldman -
Joseph Loo