On Mon, 18 Mar 2002, Lee Parsons wrote: > We began using NAT addresses on our network a few months ago, but at first > we kept all of our systems that were backed up by amanda outside the NAT > range. As time moved on we started bringing some of them inside, and it > seemed that the easiest way to get both the inside (translated) and > outside (nontranslated) addresses would be to build an amanda server and > place it inside. After building a system with FreeBSD 4.5 and amanda, we > found that it was able to connect to the machines outside, but none of the > machines inside, including itself. Is there something we missed? We > enabled the "operator" accounts on all the systems, we used inetd to start > amanadad as operator on all the systems, and added the UDP and the two TCP > ports into /etc/services. But yet we still cannot get the new amanda > server to get anything inside, including itself. When we run amcheck it > reports all the systems inside to be "host down?". Any ideas would be > much appreciated. > > ----------- > Lee Parsons > LAN Administrator > The Minnesota Daily > www.mndaily.com >
I would check your DNS settings (and /etc/resolv.conf) and if they correspond to what you have listed in your disklist file. If the amanda server has a problem with the user it will complain about that in particular (i.e. root/operator/etc). In your case, start with one machine and get that one working -- it's probably the same problem everywhere. Perhaps you aren't using the correct FQDN? Debug files will be in /tmp/amanda. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Doug Silver Network Manager Quantified Systems, Inc ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
