Problem with ws that does'nt boot after being moved from one subnet to another
This was a problem with the arp cache as I should have realised.
So the right answer was:
use arp -d hostname to clear the cache from unwanted entries.
All the answers makes a nice checklist and a few tips
1. are the /etc/ethers entries correct ?
2. have you rebuilt NIS properly ?
3. delete any old arp table entries on the server. Use arp -d.
4. check that the client is installed correctly, if necessary re-install.
5. is the client on the same IP network ?
6. is there an entry in /tftpboot for the clients IP address on the
boot server ?
7. check the network with a cable scanner.
8. use tcpdump (available from any good archive)
and check that the arps, bootparam requests are going to the right place
9. You should see what happens if you type `rarpd -d <interfacename>'
10.Check the transivers/ connections
11. Use etherfind to track the interaction between the clients and the server
Thank you very much:
eeimkey@eeiua
sjl@doc.ic.ac.uk
warren@mwunix.mitre.org
hansen@scr.slb.com
higgins@math.niu.edu
maclean@cs.mcgill.ca
miker@sbcoc.com
garyb@gcm.com
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:06:47 CDT