Greetings,
This is an old 233MHZ "box1" or 192.168.1.1 set to be the client. It is connected to another 1GHZ "box2" or 192.168.1.2 via a crossover cable. As you can see I am able to ping the client from the client (no big excitement there), and I am able to ping the server (after much experimentation and research). (Don't ask me ALL the things I did wrong and the BIOS setting when there two NIC's installed --- whew!!!)
Now I am trying to set up a NFS to gain access of files from either box. I am unable to mount the file system for use in either direction. I've read every "HOW-TO" and believe I've got it set up right, but I'm stuck. Both systems are versions of RedHat (7.3 for the older and 8.0 for the newer box).
Anything I should check, do or change? I'm fairly new to Linux so I may have done something basically wrong.
Cheers,
Bob Stelmack
====================================================================== 192.168.1.1 "box1" details ====================================================================== [root@ramjet stelmack]# hostname ramjet [root@ramjet stelmack]# more /etc/exports 192.168.1.1(rw) 192.168.1.2(rw) [root@ramjet stelmack]# cd /mnt [root@ramjet mnt]# ls cdrom cdrom1 floppy floppy.directory home zip100.0.drectory [root@ramjet stelmack]# mount 192.168.1.2: /home mount: RPC: Unable to recieve; error = Connection refused [root@ramjet stelmack]# /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:C0:4F:CF:10:B1 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING 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 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
eth1 Link encap:Ethernet HWaddr 02:00:07:E3:67:38 inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING 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 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:212 errors:0 dropped:0 overruns:0 frame:0 TX packets:212 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 RX bytes:14404 (14.0 Kb) TX bytes:14404 (14.0 Kb)
[root@ramjet stelmack]# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) from 192.168.1.1 : 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=0 ttl=255 time=780 usec Warning: time of day goes back, taking countermeasures. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=255 time=1.811 msec 64 bytes from 192.168.1.1: icmp_seq=2 ttl=255 time=276 usec 64 bytes from 192.168.1.1: icmp_seq=3 ttl=255 time=262 usec 64 bytes from 192.168.1.1: icmp_seq=4 ttl=255 time=268 usec
--- 192.168.1.1 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max/mdev = 0.262/0.679/1.811/0.599 ms [root@ramjet stelmack]# ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2) from 192.168.1.1 : 56(84) bytes of data. Warning: time of day goes back, taking countermeasures. 64 bytes from 192.168.1.2: icmp_seq=0 ttl=64 time=2.513 msec 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=387 usec 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=398 usec 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=397 usec
--- 192.168.1.2 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max/mdev = 0.387/0.923/2.513/0.918 ms
[root@ramjet stelmack]# /usr/sbin/rpcinfo -p localhost program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 32768 status 100024 1 tcp 32768 status 391002 2 tcp 32769 sgi_fam [root@ramjet stelmack]# /usr/sbin/rpcinfo -p 192.168.1.1 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 32768 status 100024 1 tcp 32768 status 391002 2 tcp 32769 sgi_fam [root@ramjet stelmack]# /usr/sbin/rpcinfo -p 192.168.1.2 rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused
[root@ramjet stelmack]# cd /etc [root@ramjet etc]# more host.conf order hosts,bind [root@ramjet etc]# more hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 ramjet localhost.localdomain localhost 192.168.1.1 box1 192.168.1.2 box2 [root@ramjet etc]# more hosts.allow # # hosts.allow This file describes the names of the hosts which are # allowed to use the local INET services, as decided # by the '/usr/sbin/tcpd' server. #
[root@ramjet etc]# more hosts.deny # # hosts.deny This file describes the names of the hosts which are # *not* allowed to use the local INET services, as decided # by the '/usr/sbin/tcpd' server. # # The portmap line is redundant, but it is left to remind you that # the new secure portmap uses hosts.deny and hosts.allow. In particular # you should know that NFS uses portmap!
[root@ramjet sysconfig]# more network NETWORKING=yes HOSTNAME=ramjet
[root@ramjet sysconfig]# cd networking/ [root@ramjet networking]# ls devices ifcfg-lo profiles [root@ramjet networking]# cd profiles [root@ramjet profiles]# ls default [root@ramjet profiles]# cd default [root@ramjet default]# ls hosts ifcfg-eth0 ifcfg-mybtinternet network ifcfg-bt ifcfg-eth0.bak ifcfg-ppp0 resolv.conf ifcfg-bt internet ifcfg-eth1 junk [root@ramjet default]# more hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 ramjet localhost.localdomain localhost 192.168.1.1 box1 192.168.1.2 box2 [root@ramjet default]# more network HOSTNAME=ramjet [root@ramjet default]# more ifcfg-eth0 DEVICE=eth0 ONBOOT=yes BOOTPROTO=static TYPE=Ethernet USERCTL=no PEERDNS=no BROADCAST=192.168.1.255 NETWORK=192.168.1.0 NETMASK=255.255.255.0 [root@ramjet default]# more resolv.conf nameserver 192.168.1.1
[root@ramjet default]# more /etc/rc.d/rc.local #!/bin/sh # # This script will be executed *after* all the other init scripts. # You can put your own initialization stuff in here if you don't # want to do the full Sys V style init stuff.
/sbin/ifconfig eth0 192.168.1.1 broadcast 192.168.1.255 netmask 255.255.255.0 up /sbin/ifconfig eth1 192.168.1.4 broadcast 192.168.1.255 netmask 255.255.255.0 up
touch /var/lock/subsys/local
====================================================================== 192.168.1.2 "box2" details ====================================================================== [root@dell stelmack]# hostname dell [root@dell stelmack]# more /etc/exports 192.168.1.2(rw) 192.168.1.1(rw) [root@dell stelmack]# cd /mnt [root@dell mnt]# ls cdrom floppy home [root@dell mnt]# mount 192.168.1.1: /home mount: RPC: Port mapper failure - RPC: Unable to receive [root@dell mnt]# /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:06:5B:70:C0:C3 inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:20 errors:0 dropped:0 overruns:0 frame:0 TX packets:24 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:1650 (1.6 Kb) TX bytes:1918 (1.8 Kb) Interrupt:11 Base address:0xec80
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:72 errors:0 dropped:0 overruns:0 frame:0 TX packets:72 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4694 (4.5 Kb) TX bytes:4694 (4.5 Kb)
[root@dell mnt]# ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2) from 192.168.1.2 : 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.124 ms 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=0.071 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=0.060 ms
--- 192.168.1.2 ping statistics --- 3 packets transmitted, 3 received, 0% loss, time 2002ms rtt min/avg/max/mdev = 0.060/0.085/0.124/0.027 ms [root@dell mnt]# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) from 192.168.1.2 : 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=255 time=0.307 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=255 time=0.298 ms 64 bytes from 192.168.1.1: icmp_seq=3 ttl=255 time=0.296 ms
--- 192.168.1.1 ping statistics --- 3 packets transmitted, 3 received, 0% loss, time 2000ms rtt min/avg/max/mdev = 0.296/0.300/0.307/0.014 ms [root@dell mnt]# [root@dell mnt]# /usr/sbin/rpcinfo -p 192.168.1.2 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 1024 status 100024 1 tcp 1024 status 391002 2 tcp 1025 sgi_fam [root@dell mnt]# /usr/sbin/rpcinfo -p 192.168.1.1 rpcinfo: can't contact portmapper: RPC: Remote system error - Connection refused[root@dell mnt]# [root@dell mnt]# [root@dell mnt]# cd /etc [root@dell etc]# more host.conf order hosts,bind [root@dell etc]# more hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 dell localhost.localdomain localhost 192.168.1.2 box2 192.168.1.1 box1 [root@dell etc]# more hosts.allow # # hosts.allow This file describes the names of the hosts which are # allowed to use the local INET services, as decided # by the '/usr/sbin/tcpd' server. #
[root@dell etc]# more hosts.deny # # hosts.deny This file describes the names of the hosts which are # *not* allowed to use the local INET services, as decided # by the '/usr/sbin/tcpd' server. # # The portmap line is redundant, but it is left to remind you that # the new secure portmap uses hosts.deny and hosts.allow. In particular # you should know that NFS uses portmap!
[root@dell etc]# [root@dell etc]# [root@dell etc]# cd sysconfig/ [root@dell sysconfig]# more network NETWORKING=yes HOSTNAME=dell [root@dell sysconfig]# cd networking [root@dell networking]# ls devices ifcfg-lo profiles [root@dell networking]# cd profiles [root@dell profiles]# ls default [root@dell profiles]# cd default/ [root@dell default]# ls hosts ifcfg-eth0 network resolv.conf [root@dell default]# more hosts # Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 dell localhost.localdomain localhost 192.168.1.2 box2 192.168.1.1 box1 [root@dell default]# more network HOSTNAME=dell [root@dell default]# more ifcfg-eth0 DEVICE=eth0 BOOTPROTO=none ONBOOT=yes USERCTL=no PEERDNS=no TYPE=Ethernet BROADCAST=192.168.1.255 NETWORK=192.168.1.0 IPADDR=192.168.1.2 NETMASK=255.255.255.0 [root@dell default]# more resolv.conf [root@dell default]# [root@dell default]#
stelmack@nwlink.com
[root@dell mnt]# /usr/sbin/rpcinfo -p 192.168.1.2 program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 1024 status 100024 1 tcp 1024 status 391002 2 tcp 1025 sgi_fam [root@dell mnt]# /usr/sbin/rpcinfo -p 192.168.1.1 rpcinfo: can't contact portmapper: RPC: Remote system error - Connection
Two things there: first, it looks like there might be some firewall working and blocking the rpcinfo connections; second, I think there are usually other services shown in rpcinfo on nfs servers, like lockd and mountd or similar. I'm not sure how RedHat starts such things, but debian has /etc/init.d/nfs-common start /etc/init.d/nfs-user-server start or similar.
Just noticed one more:
[root@dell stelmack]# more /etc/exports 192.168.1.2(rw) 192.168.1.1(rw)
That doesn't look like a valid exports file to me. Check it against man 5 exports on your system (which might use a different format).
Hope that helps,
On Tuesday 15 November 2005 12:51, MJ Ray wrote:
[root@dell stelmack]# more /etc/exports 192.168.1.2(rw) 192.168.1.1(rw)
That doesn't look like a valid exports file to me. Check it against man 5 exports on your system (which might use a different format).
Agreed. The entry in my exports looks like:
/mount *(rw,no_root_squash,sync)
The important thing here is the directory that you need to export. Also, you need to include the name or address of the computers permitted to use this directory in hosts.allow. Again, mine has:
ALL:192.168.0.
For machines in the 192.168.1.xxx range, the entry would need to be changed to:
ALL:192.168.1.
Regards, Paul.
On 11/15/05, stelmack@nwlink.com stelmack@nwlink.com wrote:
Greetings,
This is an old 233MHZ "box1" or 192.168.1.1 set to be the client. It is connected to another 1GHZ "box2" or 192.168.1.2 via a crossover cable. As you can see I am able to ping the client from the client (no big excitement there), and I am able to ping the server (after much experimentation and research). (Don't ask me ALL the things I did wrong and the BIOS setting when there two NIC's installed --- whew!!!)
Why does the BIOS need to know you have two network cards? I've put 3 in a 233MHz vintage PC.
192.168.1.1 "box1" details[root@ramjet stelmack]# /sbin/ifconfig eth0 Link encap:Ethernet HWaddr 00:C0:4F:CF:10:B1 inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
eth1 Link encap:Ethernet HWaddr 02:00:07:E3:67:38 inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
Are these two network cards on the same physical network? If they are not then you should change the "1.4" to "192.168.2.1" and the broadcast to "192.168.2.255". Otherwise how is the OS to know which interface is connected to the other PC?
Hope this helps! Tim.
-
MJ Ray -
Paul -
stelmack＠nwlink.com -
Tim Green