Dylan wrote:
Please reply on list so others with similar problems can read the solutions...
I thought I did. I guess I forgot the strange way this list is configured.
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 mistyped. I meant that I was able to set up an NFS server, not an NIS server.
I entered the host name of a client machine, linux.
Where did you enter this?
I used YaST to set up a client machine. That's where I entered the host name.
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?
/etc/exports: /home/dhenson/Documents/UOP/ linux(ro,root_squash,sync) /etc/fstab: /dev/hda3 / reiserfs acl,user_xattr 1 1 /dev/hda1 /windows/C ntfs ro,users,gid=users,umask=0$/dev/hda2 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 sysfs /sys sysfs noauto 0 0 /dev/cdrom /media/cdrom subfs noauto,fs=cdfss,ro,procuid$/dev/dvd /media/dvd subfs noauto,fs=cdfss,ro,procuid$
Dylan
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Monday 25 Jul 2005 01:16, Donald D Henson wrote:
Dylan wrote:
On Sunday 24 Jul 2005 22:57, you wrote:
I entered the host name of a client machine, linux.
Where did you enter this?
I used YaST to set up a client machine. That's where I entered the host name.
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?
/etc/exports:
/home/dhenson/Documents/UOP/ linux(ro,root_squash,sync)
OK, this is fine, except that if you specify an individual host by name then you DO need to have working name resolution (DNS or /etc/hosts.) Also, what is the host name of the server, and each client?
/etc/fstab:
Right, there's no nfs entry there, was that from the client or the server? Are we sure we are talking about the same machines as client and server? Dylan -- "The man who strikes first admits that his ideas have given out." (Chinese Proverb)
Dylan wrote:
On Monday 25 Jul 2005 01:16, Donald D Henson wrote:
Dylan wrote:
On Sunday 24 Jul 2005 22:57, you wrote:
I entered the host name of a client machine, linux. Where did you enter this? I used YaST to set up a client machine. That's where I entered the host name.
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? /etc/exports:
/home/dhenson/Documents/UOP/ linux(ro,root_squash,sync)
OK, this is fine, except that if you specify an individual host by name then you DO need to have working name resolution (DNS or /etc/hosts.) Also, what is the host name of the server, and each client?
Host name of server = toshiba Host name of client = linux
/etc/fstab: Right, there's no nfs entry there, was that from the client or the server?
The fstab was from the server.
Are we sure we are talking about the same machines as client and server?
I'm not sure I understand your question. I am using two machines on an Etherfast (100 Mb/s) network, hardwired. For learning purposes, I'm using a laptop (toshiba) as my server and a desktop (linux) as a client.
Dylan
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Monday 25 Jul 2005 18:47, Donald D Henson wrote:
Dylan wrote:
/etc/exports:
/home/dhenson/Documents/UOP/ linux(ro,root_squash,sync)
OK, this is fine, except that if you specify an individual host by name then you DO need to have working name resolution (DNS or /etc/hosts.) Also, what is the host name of the server, and each client?
Host name of server = toshiba
Host name of client = linux
/etc/fstab:
Right, there's no nfs entry there, was that from the client or the server?
The fstab was from the server.
OK, and the one from the client? can you ping from each machine to the other by hostname? Does the clien't hostname apear in /etc/hosts on the server and the server's hostname in the same file on the client? Restricting the export to single hosts introduces complications into the setup wrt having accurate name resolution functioning. It really is best at the initial stage to use the subnet-IP-address/subnet-mask approach for exporting and explicit server IP address for mounting so you can be sure that it's working then sort out restricting access.
Are we sure we are talking about the same machines as client and server?
I'm not sure I understand your question. I am using two machines on an Etherfast (100 Mb/s) network, hardwired.
I take it you mean cabled and connected via a switch/hub.
For learning purposes, I'm using a laptop (toshiba) as my server and a desktop (linux) as a client.
OK, was just checking.
Dylan
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
-- "The man who strikes first admits that his ideas have given out." (Chinese Proverb)
Dylan wrote:
On Monday 25 Jul 2005 18:47, Donald D Henson wrote:
Dylan wrote:
/etc/exports:
/home/dhenson/Documents/UOP/ linux(ro,root_squash,sync) OK, this is fine, except that if you specify an individual host by name then you DO need to have working name resolution (DNS or /etc/hosts.) Also, what is the host name of the server, and each client? Host name of server = toshiba
Host name of client = linux
/etc/fstab: Right, there's no nfs entry there, was that from the client or the server? The fstab was from the server.
OK, and the one from the client?
/dev/hda2 / reiserfs acl,user_xattr 1 1 /dev/sda1 /data1 auto noauto,user 0 0 /dev/hda1 swap swap pri=42 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 proc /proc proc defaults 0 0 usbfs /proc/bus/usb usbfs noauto 0 0 sysfs /sys sysfs noauto 0 0 /dev/cdrecorder /media/cdrecorder subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/cdrom /media/cdrom subfs noauto,fs=cdfss,ro,procuid,nosuid,nodev,exec,iocharset=utf8 0 0 /dev/fd0 /media/floppy subfs noauto,fs=floppyfss,procuid,nodev,nosuid,sync 0 0 can you ping from each machine to the
other by hostname?
I cannot ping in either direction Does the clien't hostname apear in /etc/hosts on the
server and the server's hostname in the same file on the client?
Here's the /etc/hosts contents for the client (linux) 127.0.0.1 localhost # special IPv6 addresses ::1 localhost ipv6-localhost ipv6-loopback fe00::0 ipv6-localnet ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 127.0.0.2 linux.site linux Here's the /etc/hosts contents for the server (toshiba) 127.0.0.1 localhost # special IPv6 addresses ::1 localhost ipv6-localhost ipv6-loopback fe00::0 ipv6-localnet ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 127.0.0.2 toshiba.site toshiba (I'm a bit out of my depth here but isn't the fact that two hosts have the same IP address a problem?)
Restricting the export to single hosts introduces complications into the setup wrt having accurate name resolution functioning. It really is best at the initial stage to use the subnet-IP-address/subnet-mask approach for exporting and explicit server IP address for mounting so you can be sure that it's working then sort out restricting access.
I'm game. How do I do that?
Are we sure we are talking about the same machines as client and server? I'm not sure I understand your question. I am using two machines on an Etherfast (100 Mb/s) network, hardwired.
I take it you mean cabled and connected via a switch/hub.
For learning purposes, I'm using a laptop (toshiba) as my server and a desktop (linux) as a client.
OK, was just checking.
Dylan -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Monday 25 Jul 2005 19:43, Donald D Henson wrote:
Here's the /etc/hosts contents for the client (linux)
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 127.0.0.2 linux.site linux
Here's the /etc/hosts contents for the server (toshiba)
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 127.0.0.2 toshiba.site toshiba
(I'm a bit out of my depth here but isn't the fact that two hosts have the same IP address a problem?)
Erm, maybe a silly question, but have you configured the network cards on each machine? Dylan -- "The man who strikes first admits that his ideas have given out." (Chinese Proverb)
On Mon, 2005-07-25 at 20:27 +0100, Dylan wrote:
On Monday 25 Jul 2005 19:43, Donald D Henson wrote:
Here's the /etc/hosts contents for the client (linux)
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 127.0.0.2 linux.site linux
Here's the /etc/hosts contents for the server (toshiba)
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 127.0.0.2 toshiba.site toshiba
(I'm a bit out of my depth here but isn't the fact that two hosts have the same IP address a problem?)
Erm, maybe a silly question, but have you configured the network cards on each machine?
Apparently the OP has not. Having two machines with the same IP address is like two separate houses with the same phone number trying to each other, it won't work. Setup the network interfaces using YaST with different addresses first. you can use the 127.0.0.x addresses but it is highly recommended that you do NOT. Use an address similar to 192.168.1.10 for one machine and 192.168.1.20 for the other. Once you can ping each machine then try using NFS, not before. I also recommend reading up a little on networking so you have a little better understanding of what is needed. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
On Mon, 2005-07-25 at 20:27 +0100, Dylan wrote:
On Monday 25 Jul 2005 19:43, Donald D Henson wrote:
Here's the /etc/hosts contents for the client (linux)
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 127.0.0.2 linux.site linux
Here's the /etc/hosts contents for the server (toshiba)
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 127.0.0.2 toshiba.site toshiba
(I'm a bit out of my depth here but isn't the fact that two hosts have the same IP address a problem?) Erm, maybe a silly question, but have you configured the network cards on each machine?
Apparently the OP has not. Having two machines with the same IP address is like two separate houses with the same phone number trying to each other, it won't work. Setup the network interfaces using YaST with different addresses first. you can use the 127.0.0.x addresses but it is highly recommended that you do NOT. Use an address similar to 192.168.1.10 for one machine and 192.168.1.20 for the other. Once you can ping each machine then try using NFS, not before.
Did that except I used 192.168.100.x. I can now ping the IP addresses in both directions if I use the IP addresses but cannot ping using the host names. I also recommend reading up a little on
networking so you have a little better understanding of what is needed.
Jeez, I never thought of that. I'll have to try that sometime. -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Mon, 2005-07-25 at 15:01 -0600, Donald D Henson wrote:
Ken Schneider wrote:
Apparently the OP has not. Having two machines with the same IP address is like two separate houses with the same phone number trying to each other, it won't work. Setup the network interfaces using YaST with different addresses first. you can use the 127.0.0.x addresses but it is highly recommended that you do NOT. Use an address similar to 192.168.1.10 for one machine and 192.168.1.20 for the other. Once you can ping each machine then try using NFS, not before.
Did that except I used 192.168.100.x. I can now ping the IP addresses in both directions if I use the IP addresses but cannot ping using the host names.
I also recommend reading up a little on
networking so you have a little better understanding of what is needed.
Jeez, I never thought of that. I'll have to try that sometime.
Change the entries in /etc/hosts to reflect the IP address changes. Also a FQDN contains three parts not two like you have set in /etc/hosts. There is a section in the admin manual that ships with SuSE and available in PDF format on the install media. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
Change the entries in /etc/hosts to reflect the IP address changes. Also a FQDN contains three parts not two like you have set in /etc/hosts. There is a section in the admin manual that ships with SuSE and available in PDF format on the install media.
What's an FQDN? -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
Donald, On Tuesday 26 July 2005 06:08, Donald D Henson wrote:
Ken Schneider wrote:
Change the entries in /etc/hosts to reflect the IP address changes. Also a FQDN contains three parts not two like you have set in /etc/hosts. There is a section in the admin manual that ships with SuSE and available in PDF format on the install media.
What's an FQDN?
Fully Qualified Domain Name. One that resolves to the same address no matter where the resolution is initiated. By the way, A FQDN need not have three parts, it may have only two. Many people have ceased to use the conventional "www" component. Visit any of these: http://cygwin.com/ http://netscape.com/ http://mozilla.org/ http://archive.org/ Often, two-component DNS names in the Web will be redirected to another address with more components, but not all are. Randall Schulz
On Tue, 2005-07-26 at 06:24 -0700, Randall R Schulz wrote:
Donald,
On Tuesday 26 July 2005 06:08, Donald D Henson wrote:
Ken Schneider wrote:
Change the entries in /etc/hosts to reflect the IP address changes. Also a FQDN contains three parts not two like you have set in /etc/hosts. There is a section in the admin manual that ships with SuSE and available in PDF format on the install media.
What's an FQDN?
Fully Qualified Domain Name. One that resolves to the same address no matter where the resolution is initiated.
By the way, A FQDN need not have three parts, it may have only two. Many people have ceased to use the conventional "www" component.
Should have stated that it -normally- has three parts when a company is serving more than one service but two will work.
Visit any of these:
http://cygwin.com/ http://netscape.com/ http://mozilla.org/ http://archive.org/
Often, two-component DNS names in the Web will be redirected to another address with more components, but not all are.
Randall Schulz
-- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken Schneider wrote:
On Tue, 2005-07-26 at 06:24 -0700, Randall R Schulz wrote:
By the way, A FQDN need not have three parts, it may have only two. Many people have ceased to use the conventional "www" component.
Should have stated that it -normally- has three parts when a company is serving more than one service but two will work.
Enven then, it's only necessary, when more than one server is used to provide multiple services and port forwarding isn't used.
Randall R Schulz wrote:
Donald,
On Tuesday 26 July 2005 06:08, Donald D Henson wrote:
Ken Schneider wrote:
Change the entries in /etc/hosts to reflect the IP address changes. Also a FQDN contains three parts not two like you have set in /etc/hosts. There is a section in the admin manual that ships with SuSE and available in PDF format on the install media. What's an FQDN?
Fully Qualified Domain Name. One that resolves to the same address no matter where the resolution is initiated.
Thanks. I find that the hardest part of learning to do anything in Linux is learning the terminology.
By the way, A FQDN need not have three parts, it may have only two. Many people have ceased to use the conventional "www" component.
Visit any of these:
http://cygwin.com/ http://netscape.com/ http://mozilla.org/ http://archive.org/
Often, two-component DNS names in the Web will be redirected to another address with more components, but not all are.
Randall Schulz
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Tuesday 26 July 2005 10:32 am, Donald D Henson wrote:
Thanks. I find that the hardest part of learning to do anything in Linux is learning the terminology. You are probably correct, but in the case of FQDN, this is not a Linux or Unix terminology. If you were a Windows system administrator, you would need to learn Windows terminology.
In this world of Computers, we happen to live in an acronymical world. And
in many cases we recycle acronyms.
Additionally, a while back I attended an AIX presentation, and being a long
time Unix developer and former IBM mainframe person, I found that IBM has
effectively used a large number of its own acronyms replacing the
relatively standard Unix (and Linux) acronyms.
--
Jerry Feldman
On Tuesday 26 July 2005 14:08, Donald D Henson wrote:
Ken Schneider wrote:
Change the entries in /etc/hosts to reflect the IP address changes. Also a FQDN contains three parts not two like you have set in /etc/hosts. There is a section in the admin manual that ships with SuSE and available in PDF format on the install media.
What's an FQDN?
Fully Qualified Domain Name, I think - others will soon put me right otherwise HTH Fergus
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
Fergus Wilde wrote:
On Tuesday 26 July 2005 14:08, Donald D Henson wrote:
Ken Schneider wrote:
Change the entries in /etc/hosts to reflect the IP address changes. Also a FQDN contains three parts not two like you have set in /etc/hosts. There is a section in the admin manual that ships with SuSE and available in PDF format on the install media. What's an FQDN?
Fully Qualified Domain Name, I think - others will soon put me right otherwise
Looks like you got it right.
HTH Fergus
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
Donald D Henson wrote:
Ken Schneider wrote:
Change the entries in /etc/hosts to reflect the IP address changes. Also a FQDN contains three parts not two like you have set in /etc/hosts. There is a section in the admin manual that ships with SuSE and available in PDF format on the install media.
What's an FQDN?
Fully Qualified Domain Name. That is, it specifies the entire name.
On Tue, 2005-07-26 at 07:08 -0600, Donald D Henson wrote:
Ken Schneider wrote:
Change the entries in /etc/hosts to reflect the IP address changes. Also a FQDN contains three parts not two like you have set in /etc/hosts. There is a section in the admin manual that ships with SuSE and available in PDF format on the install media.
What's an FQDN?
Fully Qualified Domain Name
Dylan wrote:
On Monday 25 Jul 2005 19:43, Donald D Henson wrote:
Here's the /etc/hosts contents for the client (linux)
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 127.0.0.2 linux.site linux
Here's the /etc/hosts contents for the server (toshiba)
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix ff02::1 ipv6-allnodes ff02::2 ipv6-allrouters ff02::3 ipv6-allhosts 127.0.0.2 toshiba.site toshiba
(I'm a bit out of my depth here but isn't the fact that two hosts have the same IP address a problem?)
Erm, maybe a silly question, but have you configured the network cards on each machine?
I did but I don't think I understood the options. Based on Ken's recommendations, I have changed the IP address of both machines (toshiba = 192.168.100.10 and linux = 192.168.100.20). Assuming this solves one of my problems, what next?
Dylan
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Monday 25 Jul 2005 21:47, Donald D Henson wrote:
Dylan wrote: I did but I don't think I understood the options. Based on Ken's recommendations, I have changed the IP address of both machines (toshiba = 192.168.100.10 and linux = 192.168.100.20). Assuming this solves one of my problems, what next?
1) Name Resolution: on toshiba, add the address for linux to /etc/hosts: 192.168.100.20 linux.site linux similarly for toshiba in linux's file. In both cases, make sure there is a blank line at the end of the file. 2) Set the export on toshiba to: /home/dhenson/Documents/UOP/ 192.168.100.0/24(ro,root_squash,sync) then restart the NFS service (if you are using yast it'll restart the service for you.) On linux, try to explicitly mount the the export (as root): mount -t nfs 192.168.100.10:/home/dhenson/Documents/UOP /mnt then see if you can ls /mnt Dylan
Dylan
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
-- "The man who strikes first admits that his ideas have given out." (Chinese Proverb)
Dylan wrote:
On Monday 25 Jul 2005 21:47, Donald D Henson wrote:
Dylan wrote: I did but I don't think I understood the options. Based on Ken's recommendations, I have changed the IP address of both machines (toshiba = 192.168.100.10 and linux = 192.168.100.20). Assuming this solves one of my problems, what next?
1) Name Resolution:
on toshiba, add the address for linux to /etc/hosts:
192.168.100.20 linux.site linux
similarly for toshiba in linux's file. In both cases, make sure there is a blank line at the end of the file.
Did that and the penny dropped. I've never thought of the /etc/hosts file as part of the name resolution process. For the first time, /etc/hosts makes sense to me. You said to make sure there is a blank line at the end of the file. Is that essential or just a good idea?
2) Set the export on toshiba to:
/home/dhenson/Documents/UOP/ 192.168.100.0/24(ro,root_squash,sync)
then restart the NFS service (if you are using yast it'll restart the service for you.)
I used YaST and substituted a host name for the IP address.
On linux, try to explicitly mount the the export (as root):
mount -t nfs 192.168.100.10:/home/dhenson/Documents/UOP /mnt
then see if you can ls /mnt
Yea. Everything works. I sincerely appreciate your hanging in there with what must sound like a bunch of stupid questions. Unfortunately, much of the documentation in the Linux world makes a lot of assumptions about how much the reader already knows. Troubleshooting a specific problem with knowledgeable individuals like many of you on this list goes a long way toward clarifying concepts in my own mind. Thanks again.
Dylan
Dylan -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Tuesday 26 Jul 2005 14:06, Donald D Henson wrote:
You said to make sure there is a blank line at the end of the file. Is that essential or just a good idea?
Some programs which read the files in /etc expect a blank line at the end (to the extent of failing to run) and others don't seem to care. It doesn't harm to make sure it's there and avoid the problem. /etc/exportfs can be particularly sensitive to whitespace problems IME but as ever YMMV.
Yea. Everything works. I sincerely appreciate your hanging in there with what must sound like a bunch of stupid questions.
Hey, I was in your shoes a few years ago, you are most welcome! Dylan -- "The man who strikes first admits that his ideas have given out." (Chinese Proverb)
On Tue, 26 Jul 2005 03:06, Dylan wrote:
On Monday 25 Jul 2005 01:16, Donald D Henson wrote:
Dylan wrote:
On Sunday 24 Jul 2005 22:57, you wrote:
I entered the host name of a client machine, linux.
Where did you enter this?
I used YaST to set up a client machine. That's where I entered the host name.
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?
/etc/exports:
/home/dhenson/Documents/UOP/ linux(ro,root_squash,sync)
OK, this is fine, except that if you specify an individual host by name then you DO need to have working name resolution (DNS or /etc/hosts.) Also, what is the host name of the server, and each client?
I suggest you use IP numbers ONLY in the /etc/exports otherwise you will be in trouble. Please refer to the man page for details on this. Therefore I recommend you use the following entry /home/dhenson/Documents/UOP/ 192.168.1.0/24(ro,root_squash,sync) Please subsitute the first three parts of ip address of "linux" with the 192.168.1.0/24 entry above. e.g if the ip address is 10.1.1.5 then enter 10.1.1.0/24 -- Regards, Graham Smith
Graham Smith wrote:
I suggest you use IP numbers ONLY in the /etc/exports otherwise you will be in trouble. Please refer to the man page for details on this.
Therefore I recommend you use the following entry /home/dhenson/Documents/UOP/ 192.168.1.0/24(ro,root_squash,sync)
Please subsitute the first three parts of ip address of "linux" with the 192.168.1.0/24 entry above. e.g if the ip address is 10.1.1.5 then enter 10.1.1.0/24
Did that. YaST was unable to find the NFS server when it did it's scan for NFS servers on this network. I entered the IP address for the server set up on toshiba manually. I was then able to access the exported directory and set a mount point. When I finished, YaST reported: Unable to mount NFS entries from /etc/fstab However, it appears to have mounted it anyway. Now I can't get rid of it. I'm beginning to think that YaST has a problem. -- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
On Monday 25 Jul 2005 22:32, Donald D Henson wrote:
Graham Smith wrote:
I suggest you use IP numbers ONLY in the /etc/exports otherwise you will be in trouble. Please refer to the man page for details on this.
Therefore I recommend you use the following entry /home/dhenson/Documents/UOP/ 192.168.1.0/24(ro,root_squash,sync)
Please subsitute the first three parts of ip address of "linux" with the 192.168.1.0/24 entry above. e.g if the ip address is 10.1.1.5 then enter 10.1.1.0/24
Did that. YaST was unable to find the NFS server when it did it's scan for NFS servers on this network. I entered the IP address for the server set up on toshiba manually. I was then able to access the exported directory and set a mount point. When I finished, YaST reported:
Unable to mount NFS entries from /etc/fstab
However, it appears to have mounted it anyway. Now I can't get rid of it.
What do you mean by "can't get rid of it"? What have you tried to achieve that end? Dylan
I'm beginning to think that YaST has a problem.
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
-- "The man who strikes first admits that his ideas have given out." (Chinese Proverb)
Dylan wrote:
Unable to mount NFS entries from /etc/fstab
However, it appears to have mounted it anyway. Now I can't get rid of it.
What do you mean by "can't get rid of it"? What have you tried to achieve that end?
The mounted directory appeared in Nautilus as it should but after removing the mount, the folders still appeared in Nautilus. However, I now believe that was a Nautilus problem.
Dylan
I'm beginning to think that YaST has a problem.
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
-- Donald D. Henson, Managing Director West El Paso Information Network The "Non-Initiation of Force Principle" Rules
participants (9)
-
Donald D Henson -
Dylan -
Fergus Wilde -
Graham Smith -
James Knott -
Jerry Feldman -
Ken Schneider -
Mike McMullin -
Randall R Schulz