minshall@kinetics.UUCP (Greg Minshall) (07/20/89)
From article <28276.8907132008@crete.cs.glasgow.ac.uk>, by inei@cs.glasgow.ac.UK (Nick Nei): > > Unable to install a Kbox in a different subnet. Our main ethernet > is 130.209.240.X with many Kboxes. When I try to load up a Kbox > in the next subnet, ie. 130.209.241.X, it fails. The atalkalog > file only shows CONF requests from the Kbox but no ROUTE and no > ZONE request: > > 7/13 21:02 aaCONF to 130.209.241.65 > 7/13 21:02 aaCONF to 130.209.241.65 > ... OK. I don't know if this is the cause of the problem you are having (and, actually, by omission you tend to say this isn't the problem). However, I've seen other people run afoul of this, and this is as good a place as any to document the following: If the "atalkad" host has more than one IP address (because, say, you are using a Sun or Vax as an IP gateway) you may have problems. Let's say you have configured an FPS box to use IP address X as the IP address of the "atalkad" host (but the host also has an interface with IP address Y). If, because of the (changing) routing topology, the path back to the FPS box goes out interface Y, many hosts will set the UDP source address to Y. When the FPS box receives the datagram it will drop the datagram, because it isn't from the "atalkad" host. Hope this helps (if not the original poster, at least someone). Greg Minshall Kinetics/Excelan/Novell minshall@kinetics.com 1-415-947-0998