mark@drd.UUCP (Mark Lawrence) (02/09/89)
( Well -- the old "do a 'w' in vi and ZZ out with no saved text going to where you expect it" bug strikes again. Sorry. ) Dear Emily PcNifs, I've got two machines I'm adding to the net: a Dell 310 (razorbks) and a Compaq '386 (bagel). With a previous Dell, we had conflicts with I/O base address and the shared memory (buffer?) address so we checked with Dell this time and got reasonable values (running with IRQ 5, too). On the Compaq, we're assuming that we can use the default values because we don't know any better and because we don't have technical documentation to find out. (IRQ 2 and the default I/O Base address). We are using WD8003E boards. The YP server is a Sun 3/260 (running SunOS 3.5) which supports RARP for a couple of diskless nodes. So as far as I know, there is no reason to install hosts or ethers equivalents on the PCs (and don't, in fact, on the other 6 PC class machines we have PC-NFS 3.0 running on). After installing the boards, running myeaddr.exe and getting the addresses and configuring the numbers into the /etc/ethers and /etc/hosts files on the server and running make in /etc/yp, and doing all the normal config stuff on the PC's, both fail to figure out their hostname and internet address at the 'net strt rdr *' command in the bootup sequence. I made sure with the ypcat command on another machine on the net that the machines were known in the yp ethers and hosts databases. I even went so far as to monitor the e-net traffic using etherfind and compared the failed packets to a session of packets with a machine that works. The initial sequence of three broadcast packets from bagel look thus: 'etherfind -n -x -broadcast' output when doing a 'net strt rdr *' @ bagel 64 rarp 0 0 ffffffff ffff0000 c0053f13 80350001 08000604 00030000 c0053f13 00000000 0000c005 3f130000 64 rarp 0 0 ffffffff ffff0000 c0053f13 80350001 08000604 00030000 c0053f13 00000000 0000c005 3f130000 64 rarp 0 0 ffffffff ffff0000 c0053f13 80350001 08000604 00030000 c0053f13 00000000 0000c005 3f130000 The pertinent info for bagel in the databases are: 0:0:c0:05:3f:13 bagel -- ethers 192.9.200.24 bagel -- hosts (obviously not on the internet) The rarp packet from bagel is identical (as far as I can tell) to a rarp packet from a machine that works properly with the exception of the "from" e-net address field. However, if I monitor traffic from another machine (than the server), I can see the server responding immediately to the RARP broadcast from properly working good machines and ignoring the broadcast from bagel. The configuration files on the server and the yellow pages databases seem correct. I've rebooted the server to make sure the rarpd's aren't just being stubborn headed. I can see the broadcast rarp request going out on the net. What is wrong? Why won't the server respond? Yours Truly Confused