I’ve been trying to get my openSUSE desktop PC to work as an NFS server, but I can’t seem to connect to it. When I try to mount it from a remote machine, I run sudo mount -t nfs 192.168.2.2:/home/ /home/dan/Desktop/share however I press enter and nothing happens after that. Let me know what logs and such I should retrieve to troubleshoot this. Thanks!
-Dan
dmesg ?
Could you be a little more specific? I don’t remember what to do with “dmesg”…I remember seeing it, but I am definitely not at the point of remembering all these logfile locations and how to get them.
Thanks,
Dan
I’m also beginning to sense that all my remote access problems are related. I can’t connect to that computer via ssh, NFS, or Samba. I know I have used at least ssh with this client before because I spent some time troubleshooting an Ubuntu desktop via ssh. So, what then should I be looking for on the host machine? I did use the YAST utilities to open the firewall ports for NFS and samba, but obviously they still don’t work. NFS just hangs, while Samba actually times out. Any clues here?
Thanks,
Dan
Sorry, **dmesg **is a command to be executed (as root) in a console/terminal.
When you have questions about a command and what it does and what its options and/or parameters are you type man <command> in a console terminal (you do not need to be root for that). So as an example (and a place to start) do
man man
to know more about **man **and then
man dsmesg
to know more about dmesg.
You can get a nicer layout of you man pages using Konqueror with man: as the protocol in the location bar. So the above examples then will be man:man and man:dmesg.
Hope this helps, because looking into the loggging using **dmesg **will, I hope, tell you more about the many problems you have in this connection.
BTW does the connection between the two systems exist at all? Try
ping <the-other-system>
(and do **man ping **when you want to know more about ping).
Thanks! I did try pinging my desktop machine (host) from my laptop (client) today, and got no response. What does this signify (other than no response)?
-Dan
That means that you have no connection at all between the systems (except physical by way of the cables maybe 
). And thus it is of no use to try if things run over that connection (like ssh, nfs, printing, whatever).
Check your NIC configuration and status on both sides. When in doubt if correct post the output of
sudo ifconfig
on both sides. And tell us how the physical connection looks like (direct cable, router, wireless?).
And what happens during boot with the interfaces? Did you look through the output of
sudo dmesg | more
to find problems with them?
Here’s the ifconfig for the desktop (server):
eth0 Link encap:Ethernet HWaddr 00:1E:8C:D4:F7:2D
inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::21e:8cff:fed4:f72d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:53764 errors:0 dropped:1513506548466 overruns:0 frame:0
TX packets:47779 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:60043403 (57.2 Mb) TX bytes:6511153 (6.2 Mb)
Interrupt:253 Base address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:920 errors:0 dropped:0 overruns:0 frame:0
TX packets:920 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:174701 (170.6 Kb) TX bytes:174701 (170.6 Kb)
I also did dmesg | more, but I’m not sure what I’m looking for there. I skimmed through the output, and the only thing I noticed is something about no ivp6 routers found or something, but I don’t know that that’s relevant. Any hints here?
Also, here’s the ifconfig for the laptop (client):
eth0 Link encap:Ethernet HWaddr 00:15:C5:18:73:30
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:22
eth1 Link encap:Ethernet HWaddr 00:16:CE:6C:72:C0
inet addr:192.168.2.5 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::216:ceff:fe6c:72c0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1335 errors:0 dropped:0 overruns:0 frame:0
TX packets:1079 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1128694 (1.0 MiB) TX bytes:163217 (159.3 KiB)
Interrupt:16 Memory:dfdfc000-dfe00000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:66 errors:0 dropped:0 overruns:0 frame:0
TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5176 (5.0 KiB) TX bytes:5176 (5.0 KiB)
vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
inet addr:192.168.198.1 Bcast:192.168.198.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08
inet addr:192.168.92.1 Bcast:192.168.92.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Is there maybe a firewall port I missed on the server or something like that? How do I check that?
-Dan
I also asked for a description how the two systems are physicaly connected.
From the ifconfigs I suppose that 192.168.2.2 (eth0 on desktop) and 192.168.2.5 (eth1 on the laptop) are the IP addresses involved in the connection we are talking about. That would mean we are talking about a wired connection, right? Are they connected directly or via a router? Please help, so that I get some idea of how it looks like. Do not think that when things are obvious to you they will also be obvious to me.
And to further enlighten me could you post for both systems:
sudo netstat -rn
(that is an r and an n after the - ).
The firewall will not interfere with the ping trafic normaly, but during the testing, switching of the firewall removes an extra player in the whole problem. And as I suppose that you are behind a router that acts as a firewall, that is not much of a security thread.
On IPv6. I do not think that that is a problem because you are not using it. But many people use YaST > Netwotk Devices > Network Card and then the tab Global Options to uncheck IPv6. It helped to solve some problems (particularly in performace) and as long as you do not use IPv6 …
Sorry, I forgot to mention the connectivity! The server has a wired connection to a Belkin router, while the client connects via secure wireless to the router.
Here is the netstat output of the server:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth0
And the client:
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 192.168.2.1 0.0.0.0 UG 0 0 0 eth1
-Dan
Sorry, maybe it is me, but can we please both give only one name to any of the entities involved.
So not desktop in one sentence and server in another one. Or ‘a Belkin router’ vs ‘the router’. Im am still not sure if we are talking about one or two routers. And I still feel that you not fully confirmed/denied my guess about wired/wifi and direct/via-router of the connection (and only that one) we are talking about. I will again offer you my guess:
desktop (192.168.2.2) <-cable-> router (192.168.2.1) <-cable-> laptop (192.168.2.5)
Please confirm or make a better schema.
I do not know where the other NICs on the laptop are for, they are up but they have no routes through them.
Default routes seem to go to the router (from my schema above). Interfaces are UP. When the router is functioning correct a
sudo ping 192.168.2.5
from the desktop (and vv.) should work.
Sorry, I haven’t been clear. I guess I’m afraid I’m not using the right terminology.
When I say “server”, I imply my desktop computer. When I say “client”, I imply my laptop. Also, I only have one router: the belkin router, which has LAN and wifi output.
I also corrected your diagram, see below:
desktop (192.168.2.2) <-cable-> router (192.168.2.1) <-wireless internet connection-> laptop (192.168.2.5)
I also tried “pinging” on both the server and client now, and it works (server pings client, client pings server). I assume the output of the ping command is not really relevant, as it’s just tracking packets of data.
-Dan
Of course it does not matter what they are called as long as we do you the same words both and all the time. I prefer desktop and laptop becuase I can imagine something on that. Client and server are functions, not sytem types to me. But it is clear now.
Thanks a lot. This means that you can now ping, which you could not earlier. So now you can go one step higher and try to run a service over it.
I am a bit in a hurry now and forgot if you run 10.3 or 11.? or what. But try NFS without any firewall on first. I will look further into it tomorrow. When you have more info in the meantime, please post.
I think I at least have my various remote connection methods set up correctly now. I disabled the firewall, and now I can now access the server via SAMBA (partially) and SSH. SAMBA works only in certain folders; it asks me to log in to view other folders, but it doesn’t seem to accept any logins. I don’t think I set a password, but I tried some anyway, and also tried changing the domain from the default MSHOME to BLACKDIAMOND, which is what I set it to in the server. Regardless, that’s a separate issue. The SSH connection works fine.
However, NFS still isn’t working. When I run
sudo mount -v -a -t nfs 192.168.2.2:/ ~/
in the client machine, it returns this error:
mount to NFS server '192.168.2.2' failed.
RPC Error: 15 ( Program not registered )
Am I typing something wrong or is there still something amiss?
Thanks,
Dan
Can not help you with SAMBA. I do not know much about MS. Why do you use SAMBA between Linux systems? It is something to use with MS systems.
Your NFS mount is not correct I think. The mountpoint ~/ is a bit ambigious. Whose ~, that from a user or from root? What do you mean with it? Better use an absolute path.
Now more generaly about NFS. Some points to check.
On the NFS-client side: using YaST > System > System Services (Runlevel) look to ‘nfs (nfs client services)’, is it Yes?
On the NFS-server side: using YaST > System > System Services (Runlevel) look to ‘nfs server (start the kernel based NFS daemon)’ is it Yes, and is it the ‘kernel based’ one? In the past problems were solved by using the kernel based instead of the user based NFS service.
And to get some more information on NFS server side post the ouput of
cat /etc/exports
and of
sudo exportfs -v
On the server, the nfs kernel daemon is the one running. I can’t check it in the same way on the client, as it runs Ubuntu, but I would have to assume that the case is the same there. Also, I’m using Samba as well as NFS (and ssh) mainly because I wanted them all to be set up, and I was curious to see which ones worked, when ssh was first being problematic. There’s no reason that I can see not to use Samba between Linux machines, and if anything, it’s there so when I use Windows XP on my laptop I can still connect.
Here is cat /etc/exports:
dan@linux-8amt:~> cat /etc/exports
%H/ 192.168.0.0/255.255.255.0(rw,async)
/home/ 192.168.0.0/255.255.255.0(rw,async)
/home/groups/ 192.168.0.0/255.255.255.0(rw,async)
/media/BRANDESKY20/ 192.168.0.0/255.255.255.0(rw,async)
/home/dan/ *(rw,async,all_squash)
And exportfs -v:
linux-8amt:/home/dan # exportfs -v
/media/BRANDESKY20
192.168.0.0/255.255.255.0(rw,async,wdelay,root_squash,no_subtree_check)
/home/groups 192.168.0.0/255.255.255.0(rw,async,wdelay,root_squash,no_subtree_check)
/home/dan/%H 192.168.0.0/255.255.255.0(rw,async,wdelay,root_squash,no_subtree_check)
/home 192.168.0.0/255.255.255.0(rw,async,wdelay,root_squash,no_subtree_check)
/home/dan <world>(rw,async,wdelay,root_squash,all_squash,no_subtree_check)
-Dan
I think I found an error in the export statements.
You export to 192.168.0.0/255.255.255.0. That means to all systems where the IP address starts with 192.168.0. But your systems are in the 192.168.2 network and thus do not match.
Either change it to 192.168.2.0/255.255.255.0 (meaning all hosts in the 192.168.2 network) or to 192.168.0.0/255.255.0.0 (meaning all hosts in the 192.168 network).
I corrected my export statements, but I still get a message saying “mount to nfs server failed” when I try to connect. I did restart nfsserver as well.
-Dan
Got no reaction from you in my remark above. It has two ?-marks, but I got 0 answers. What is you mount statement now.