I still don't seem to be able to get my computer connecting, as an NFS client, to itself, my NFS server. (Or a second computer acting as NFS client) (both machines on SuSE9.2 Pro) Any ideas on what configurations to check or should I just revert to micro$haft?
On Sunday 20 February 2005 20:10, John wrote:
I still don't seem to be able to get my computer connecting, as an NFS client, to itself, my NFS server. (Or a second computer acting as NFS client) (both machines on SuSE9.2 Pro)
What are you trying to share? The /home directory on the server perhaps so that the client can share the files? A NIS environment? A workgroup serving gimp from a central server? Can't keep guessing! NFS is really easy to setup especially if you use yast but we can't help unless you tell us what you want to do.
/home is one of four directories that I wish to share (the others are custom, not part of the standard structure). When trying to configure NFS client in YAST (the server was also configured in YAST), it gives me the option to choose the NFS server hostname. Neither of my computers seem to recognise that I have a server configured and, therefore, fail to find it. If I try and type the server name in longhand, the client configurator does not believe me. What am I doing wrong? Thanks steve wrote:
On Sunday 20 February 2005 20:10, John wrote:
I still don't seem to be able to get my computer connecting, as an NFS client, to itself, my NFS server. (Or a second computer acting as NFS client) (both machines on SuSE9.2 Pro)
What are you trying to share? The /home directory on the server perhaps so that the client can share the files? A NIS environment? A workgroup serving gimp from a central server? Can't keep guessing!
NFS is really easy to setup especially if you use yast but we can't help unless you tell us what you want to do.
On Sunday 20 February 2005 20:42, John wrote:
/home is one of four directories that I wish to share (the others are custom, not part of the standard structure).
When trying to configure NFS client in YAST (the server was also configured in YAST), it gives me the option to choose the NFS server hostname.
use the IP of the server rather than its name and see if that makes a difference.
steve wrote:
On Sunday 20 February 2005 20:42, John wrote:
/home is one of four directories that I wish to share (the others are custom, not part of the standard structure).
When trying to configure NFS client in YAST (the server was also configured in YAST), it gives me the option to choose the NFS server hostname.
use the IP of the server rather than its name and see if that makes a difference.
Yes that works.
On Monday 21 February 2005 10:49, John wrote:
steve wrote:
On Sunday 20 February 2005 20:42, John wrote:
/home is one of four directories that I wish to share (the others are custom, not part of the standard structure).
When trying to configure NFS client in YAST (the server was also configured in YAST), it gives me the option to choose the NFS server hostname.
use the IP of the server rather than its name and see if that makes a difference.
Yes that works.
Good. Now you should be able to see /home on the client where you mounted it. Yes? If you want to use the host name rather than the IP then add the name and IP to the /etc/hosts file on the client
steve wrote:
On Monday 21 February 2005 10:49, John wrote:
steve wrote:
On Sunday 20 February 2005 20:42, John wrote:
/home is one of four directories that I wish to share (the others are custom, not part of the standard structure).
When trying to configure NFS client in YAST (the server was also configured in YAST), it gives me the option to choose the NFS server hostname.
use the IP of the server rather than its name and see if that makes a difference.
Yes that works.
Good. Now you should be able to see /home on the client where you mounted it. Yes?
If you want to use the host name rather than the IP then add the name and IP to the /etc/hosts file on the client
Shouldn't DNS take care of that?
On Monday 21 February 2005 11:05, John wrote:
steve wrote:
On Monday 21 February 2005 10:49, John wrote:
steve wrote:
On Sunday 20 February 2005 20:42, John wrote:
/home is one of four directories that I wish to share (the others are custom, not part of the standard structure).
When trying to configure NFS client in YAST (the server was also configured in YAST), it gives me the option to choose the NFS server hostname.
use the IP of the server rather than its name and see if that makes a difference.
Yes that works.
Good. Now you should be able to see /home on the client where you mounted it. Yes?
If you want to use the host name rather than the IP then add the name and IP to the /etc/hosts file on the client
Shouldn't DNS take care of that?
Have you got a fully functioning DNS set up on your network? -- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
Fergus Wilde wrote:
On Monday 21 February 2005 11:05, John wrote:
steve wrote:
On Monday 21 February 2005 10:49, John wrote:
steve wrote:
On Sunday 20 February 2005 20:42, John wrote:
/home is one of four directories that I wish to share (the others are custom, not part of the standard structure).
When trying to configure NFS client in YAST (the server was also configured in YAST), it gives me the option to choose the NFS server hostname.
use the IP of the server rather than its name and see if that makes a difference.
Yes that works.
Good. Now you should be able to see /home on the client where you mounted it. Yes?
If you want to use the host name rather than the IP then add the name and IP to the /etc/hosts file on the client
Shouldn't DNS take care of that?
Have you got a fully functioning DNS set up on your network?
I hope so. Certainly, my web service (Apache) distinguishes between my domain names. However, whilst my XP workstation seems to resolve the FQDN of my Linux (SuSE 9.2) server, my laptop (also SUSE 9.2) does not. All of my configuartion has been with YAST; which files do I need to edit (and with what information) to sort this? Thanks
On Monday 21 February 2005 11:39, John wrote:
Fergus Wilde wrote:
On Monday 21 February 2005 11:05, John wrote:
steve wrote:
On Monday 21 February 2005 10:49, John wrote:
steve wrote:
On Sunday 20 February 2005 20:42, John wrote: >/home is one of four directories that I wish to share >(the others are custom, not part of the standard >structure). > >When trying to configure NFS client in YAST (the server >was also configured in YAST), it gives me the option to >choose the NFS server hostname.
use the IP of the server rather than its name and see if that makes a difference.
Yes that works.
Good. Now you should be able to see /home on the client where you mounted it. Yes?
If you want to use the host name rather than the IP then add the name and IP to the /etc/hosts file on the client
Shouldn't DNS take care of that?
Have you got a fully functioning DNS set up on your network?
I hope so. Certainly, my web service (Apache) distinguishes between my domain names. However, whilst my XP workstation seems to resolve the FQDN of my Linux (SuSE 9.2) server, my laptop (also SUSE 9.2) does not.
Yes ... you mean you have a correctly set up DNS server on your local network that resolves the names of all the machines on that network? (sounds like you don't?) If not, you should put the names of the machines involved into the /etc/hosts files of the local machines (if your network is modest in size) or set up such a DNS server, though this is non-trivial as far as I'm aware. If, for example, you add a line like this to the /etc/hosts file of your laptop: [valid ip address] linuxserver.example.com linuxserver Then your laptop will translate instructions like 'ssh linuxserver' as 'ssh [valid ip address]. That ought to work for NFS too. $ man hosts has the details. HTH Fergus
All of my configuartion has been with YAST; which files do I need to edit (and with what information) to sort this?
Thanks
-- Fergus Wilde Chetham's Library Long Millgate Manchester M3 1SB Tel: +44 161 834 7961 Fax: +44 161 839 5797 http://www.chethams.org.uk
Shouldn't DNS take care of that?
Have you got a fully functioning DNS set up on your network?
I hope so. Certainly, my web service (Apache) distinguishes between my domain names. However, whilst my XP workstation seems to resolve the FQDN of my Linux (SuSE 9.2) server, my laptop (also SUSE 9.2) does not.
All of my configuartion has been with YAST; which files do I need to edit (and with what information) to sort this?
Thanks
You know that your DNS isn't working because putting the IP instead of the hostname in the yast NFS configuration module worked whereas the hostname didn't. I'd recommend getting it working with /etc/hosts first as setting up a DNS is not a small task. So the file you need to edit is /etc/hosts. You can also edit this file from yast. Good luck, Steve.
steve wrote:
You know that your DNS isn't working because putting the IP instead of the hostname in the yast NFS configuration module worked whereas the hostname didn't. I'd recommend getting it working with /etc/hosts first as setting up a DNS is not a small task. Actually, if the same machine is the DNS server and the DHCP server, 9.2 has made it quite easy via the Yast DNS Server and DHCP server tools. AFAIR, 9.2 was the first version to have these, but they work very well and make it quite easy comparatively. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871
On Monday 21 February 2005 06:39, John wrote:
Fergus Wilde wrote:
On Monday 21 February 2005 11:05, John wrote:
steve wrote:
On Monday 21 February 2005 10:49, John wrote:
steve wrote:
On Sunday 20 February 2005 20:42, John wrote: >/home is one of four directories that I wish to share >(the others are custom, not part of the standard >structure). > >When trying to configure NFS client in YAST (the server >was also configured in YAST), it gives me the option to >choose the NFS server hostname.
use the IP of the server rather than its name and see if that makes a difference.
Yes that works.
Good. Now you should be able to see /home on the client where you mounted it. Yes?
If you want to use the host name rather than the IP then add the name and IP to the /etc/hosts file on the client
Shouldn't DNS take care of that?
Have you got a fully functioning DNS set up on your network?
I hope so. Certainly, my web service (Apache) distinguishes between my domain names. However, whilst my XP workstation seems to resolve the FQDN of my Linux (SuSE 9.2) server, my laptop (also SUSE 9.2) does not.
All of my configuartion has been with YAST; which files do I need to edit (and with what information) to sort this?
YaST->Network Services->DNS and Host Name Make sure the IPs of the DNS servers is correct. If you don't use a Search Domain then you will need to use the fully qualified host name when naming the server in NFS (ie, myhost.mydomain). Jeff
Jeffrey Laramie wrote:
On Monday 21 February 2005 06:39, John wrote:
Fergus Wilde wrote:
On Monday 21 February 2005 11:05, John wrote:
steve wrote:
On Monday 21 February 2005 10:49, John wrote:
steve wrote:
>On Sunday 20 February 2005 20:42, John wrote: > > >>/home is one of four directories that I wish to share >>(the others are custom, not part of the standard >>structure). >> >>When trying to configure NFS client in YAST (the server >>was also configured in YAST), it gives me the option to >>choose the NFS server hostname. >> >> >use the IP of the server rather than its name and see if >that makes a difference. > > Yes that works.
Good. Now you should be able to see /home on the client where you mounted it. Yes?
If you want to use the host name rather than the IP then add the name and IP to the /etc/hosts file on the client
Shouldn't DNS take care of that?
Have you got a fully functioning DNS set up on your network?
I hope so. Certainly, my web service (Apache) distinguishes between my domain names. However, whilst my XP workstation seems to resolve the FQDN of my Linux (SuSE 9.2) server, my laptop (also SUSE 9.2) does not.
All of my configuartion has been with YAST; which files do I need to edit (and with what information) to sort this?
YaST->Network Services->DNS and Host Name
Make sure the IPs of the DNS servers is correct. If you don't use a Search Domain then you will need to use the fully qualified host name when naming the server in NFS (ie, myhost.mydomain).
Jeff
I've checked the configuration in YaST as suggested and all seems as I would expect. My XP workstation resolves and pings all my DNS names but my SuSE9.2 laptop only returns unknown host. J
Make sure the IPs of the DNS servers is correct. If you don't use a Search Domain then you will need to use the fully qualified host name when naming the server in NFS (ie, myhost.mydomain).
Jeff
I've checked the configuration in YaST as suggested and all seems as I would expect. My XP workstation resolves and pings all my DNS names but my SuSE9.2 laptop only returns unknown host.
OK, then your NFS problem is actually a DNS problem. Check that the laptop firewall allows port 53 udp and tcp through. Try disabling the laptop firewall and retry. From the laptop can you telnet to port 53 on the server? Jeff
Jeffrey Laramie wrote:
Make sure the IPs of the DNS servers is correct. If you don't use a Search Domain then you will need to use the fully qualified host name when naming the server in NFS (ie, myhost.mydomain).
Jeff
I've checked the configuration in YaST as suggested and all seems as I would expect. My XP workstation resolves and pings all my DNS names but my SuSE9.2 laptop only returns unknown host.
OK, then your NFS problem is actually a DNS problem. Check that the laptop firewall allows port 53 udp and tcp through. Try disabling the laptop firewall and retry. From the laptop can you telnet to port 53 on the server?
Jeff
Without changing firewall configuration, telnet ip_address 53 connected, telnet FQDN 53 did not. Turning off the firewall made no difference to this, nor did re-enabling the firewall and checking the DNS box in YaST J
On Mon, 2005-02-21 at 09:58, John wrote:
Jeffrey Laramie wrote:
OK, then your NFS problem is actually a DNS problem. Check that the laptop firewall allows port 53 udp and tcp through. Try disabling the laptop firewall and retry. From the laptop can you telnet to port 53 on the server?
Jeff
Without changing firewall configuration, telnet ip_address 53 connected, telnet FQDN 53 did not. Turning off the firewall made no difference to this, nor did re-enabling the firewall and checking the DNS box in YaST
Could you please post a copy of your /etc/hosts file and your /etc/resolv.conf file. There appears to be a problem with one or both of these files. Also PLEASE only reply to the list! I don't need two copies of your reply. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 * Only reply to the list please* "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
On Sunday 20 February 2005 14:42, John wrote:
/home is one of four directories that I wish to share (the others are custom, not part of the standard structure).
When trying to configure NFS client in YAST (the server was also configured in YAST), it gives me the option to choose the NFS server hostname. Neither of my computers seem to recognise that I have a server configured and, therefore, fail to find it. If I try and type the server name in longhand, the client configurator does not believe me.
What am I doing wrong?
1. Another poster suggested you check for a firewall running. Make sure you check the client and the server since either could be blocking. 2. Check the DNS on the client. If YaST can't find the server by name it may be a DNS issue. 3. Run "rpcinfo -p" on both the client and the server. Are the NFS services running? 4. Try "telnet localhost 111" to see if you can connect to the portmapper. Jeff
On Sunday 20 Feb 2005 19:10 pm, John wrote:
I still don't seem to be able to get my computer connecting, as an NFS client, to itself, my NFS server. (Or a second computer acting as NFS client) (both machines on SuSE9.2 Pro)
Any ideas on what configurations to check
Not unless you tell us what you have done and what you want to do (and in the case of connecting via nfs to the same machine - why.)
or should I just revert to micro$haft?
That sort of comment will most likely result in you getting less help, not more. -- "I see your Schwartz is as big as mine" -Dark Helmet
Did you setup a firewall? Check your config file! Le Dimanche 20 Février 2005 09:45, Dylan a écrit :
On Sunday 20 Feb 2005 19:10 pm, John wrote:
I still don't seem to be able to get my computer connecting, as an NFS client, to itself, my NFS server. (Or a second computer acting as NFS client) (both machines on SuSE9.2 Pro)
Any ideas on what configurations to check
Not unless you tell us what you have done and what you want to do (and in the case of connecting via nfs to the same machine - why.)
or should I just revert to micro$haft?
That sort of comment will most likely result in you getting less help, not more.
-- "I see your Schwartz is as big as mine" -Dark Helmet
-- Yves Baudrier Linux registered user # 182046
Firewall has been configured through YAST - both the check boxes on the NFS page and the NFS box on the firewall page are checked. I suppose one of my questions is 'which config file(s)'? J Yves Baudrier wrote:
Did you setup a firewall? Check your config file!
Le Dimanche 20 Février 2005 09:45, Dylan a écrit :
On Sunday 20 Feb 2005 19:10 pm, John wrote:
I still don't seem to be able to get my computer connecting, as an NFS client, to itself, my NFS server. (Or a second computer acting as NFS client) (both machines on SuSE9.2 Pro)
Any ideas on what configurations to check
Not unless you tell us what you have done and what you want to do (and in the case of connecting via nfs to the same machine - why.)
or should I just revert to micro$haft?
That sort of comment will most likely result in you getting less help, not more.
-- "I see your Schwartz is as big as mine" -Dark Helmet
On Sun, 2005-02-20 at 14:10, John wrote:
I still don't seem to be able to get my computer connecting, as an NFS client, to itself, my NFS server.
Huh! And why would you want to nfs mount an nfs share from the machine to itself. This seems rather lame to me. And maybe also to the programmers that wrote nfs which is why it doesn't work. Even on M$ this would be a rather lame thing to do.
(Or a second computer acting as NFS client) (both machines on SuSE9.2 Pro)
Any ideas on what configurations to check or should I just revert to micro$haft? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998
* Only reply to the list please* "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 Sun, 2005-02-20 at 14:10, John wrote:
I still don't seem to be able to get my computer connecting, as an NFS client, to itself, my NFS server.
Huh! And why would you want to nfs mount an nfs share from the machine to itself. This seems rather lame to me. And maybe also to the programmers that wrote nfs which is why it doesn't work. Even on M$ this would be a rather lame thing to do.
(Or a second computer acting as NFS client) (both machines on SuSE9.2 Pro)
Any ideas on what configurations to check or should I just revert to micro$haft?
Lame or not, it offers a way to verify that NFS is working - if it can't see itself, how can it expect other computers to see it?
John wrote:
Ken Schneider wrote:
On Sun, 2005-02-20 at 14:10, John wrote:
I still don't seem to be able to get my computer connecting, as an NFS client, to itself, my NFS server.
Huh! And why would you want to nfs mount an nfs share from the machine to itself. This seems rather lame to me. And maybe also to the programmers that wrote nfs which is why it doesn't work. Even on M$ this would be a rather lame thing to do.
Lame or not, it offers a way to verify that NFS is working - if it can't see itself, how can it expect other computers to see it?
The showmount command will show what's being exported.
participants (9)
-
Dylan -
Fergus Wilde -
James Knott -
Jeffrey Laramie -
Joe Morris (NTM) -
John -
Ken Schneider -
steve -
Yves Baudrier