Trying to get NFS to work AGAIN...

[luggw1]

...And being a little brain dead in the process. Let me begin by saying that I don't even pretend to understand all the ins and outs of networks, but this setup seems like it should be a pretty simple one.

OK, here's the deal. I've got two machines. One that I've been using for some time without a problem, connected to the Internet via a wireless router and running SuSE 10.0.

The second machine hasn't run in many months, but also runs SuSE 10.0 and now also connects to the Internet via the same wireless router.

Formerly, these machines were part of a wired network (including a wired router) and had hard coded IP addresses. The new router uses DHCP to assign IP addresses to the connected machines, but these two always seem to get the same two addresses.

I've used YaST to configure the NFS Server on the machine named compaq and defined some shares for it to serve. I also configured the NFS client on the machine named antec. I set up the /etc/hosts files on each to look as follows:

compaq:
127.0.0.1 localhost
127.0.0.2 compaq.local compaq
192.168.1.102 antec.local antec


antec:
127.0.0.1 localhost
127.0.0.2 antec.local antec
192.168.1.104 compaq.local compaq

I also setup the /etc/fstab file on the client antec machine to automatically mount the NFS shares at boot time. Note that all these things were done back when the machines were wired together and had hard coded IPs. When I brought the second machine back to life a few days ago, I went through and changed the hosts files on both machines to the new addresses, but this seems to have made things worse instead of better.

Now, when I attempt to ping the other machine I get the following:
compaq:/home/luggw1 # ping antec
PING antec.local (192.168.1.102) 56(84) bytes of data.
From 192.168.1.104: icmp_seq=2 Destination Host Unreachable
From 192.168.1.104 icmp_seq=2 Destination Host Unreachable

The response is similar from the other machine. I now seem to have thoroughly hosed myself and don't see a way out. So, here are my questions.

1. In the wonderful world of DHCP, how does one handle the situation of variable IPs being associated with a host name where NFS is concerned?

2. Since this is a painfully simple network with a total of three machines (two Linux, one Windoze) (nope, wait a minute, one of the Linux boxex dual boots into Windoze and runs Windoze through VMWare too) and a print server, do we even need DHCP?

3. What do I need to do to get NFS back on its feet?

Thanks for the help.

Bill Lugg

[luggw1]

I restarted the antec machine and much to my surprise EVERYTHING began working again! I am again able to move files back and forth between the two machines.

However, I would still be interested in the community's thoughts regarding DHCP in this situation.

Thanks.
Bill Lugg

[kslnxusr]

I just use static IP's. I only have 4 devices so management is not a big deal.

For a larger install you can make DHCP automatically update a DNS server, so if you setup your own DNS and DHCP you could probably make it work. You can make DHCP assign the same address to a particular MAC address but that would mean running a DHCP server off the router, unless you flash a new image to the router.

For me it's just easier to use static settings.

[emn8w8]

Hi, Bill,

I'm no network guru either, but the configuration you described in your original post is asking for trouble...it has to do with subnets. If you assign two different subnet IP adresses to your machines like you did (127.0.0.2 and 192.168.1.102) they will never be able to communicate....the ping response of "Destination Host Unreachable" is therefore no surprise. If you want them in the same subnet you have to assign them IP adresses like Compaq 192.168.1.101 & Antec 192.168.1.102; or like Compaq 10.0.0.2 & Antec 10.0.0.3. The 3 numbers before the point form the subnet, the last number is for the machine. This limits the size of your LAN to 254 machines: x.x.x.0 to x.x.x.254. The last one: x.x.x.255 is used as broadcast adress for the communication. If you really have to work with 2 different subnets then you have to use a machine with 2 NIC's and assign each of the NIC the appropriate subnet number. This configuration is often used as a firewall.
DHCP must have been in your case the miracle that solved the problem: most probably is on your wireless router the DHCL server enabled and has it passed out IP numbers to your machines in the same subnet. And that it will work...!
Try to find out what IP numbers both machines have in use...

Erik Meulmeester