Yes. We can run nslookup from the amanda server on the hostnames of any of the machines with NAT addresses we want it to backup and they resolve to the proper NAT addresses. The file /etc/resolv.conf has a domain and a nameserver entry, no search entry, unless thats a synonymous term with nameserver. Ping and ssh work fine from the amanda server to other internal machines.
Whats the proper syntax for running tcpdump on amcheck? Thats not something that I often need to run. ----------- Lee Parsons LAN Administrator The Minnesota Daily www.mndaily.com On Tue, 19 Mar 2002, Doug Silver wrote: > Ok, if you run this: > nslookup `hostname` > > on the amanda server, does that resolve? In the resolv.conf file, are > there 'domain' and 'search' entries? You can ping all the internal > machines, correct? What about some other service like ssh? > > As a last resort, you could run tcpdump while running amcheck to one or > two clients to see what the packets actually look like. > > -- > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Doug Silver > Network Manager > Quantified Systems, Inc > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > On Tue, 19 Mar 2002, Lee Parsons wrote: > > > Our NAT addresses are class C (192.168.0.xxx). The Amanda server resides > > at 192.168.0.18. It is unable to back itself up. We have a DNS server > > set up for the NAT addresses at 192.168.0.10 that is referred to in > > /etc/resolv.conf as the only DNS server for the Amanda server. However > > the Amanda server has no difficulties with the machines on the public IPs > > when it runs amcheck. We also tried to put the IP addresses of the > > internal machines into the disklist file, and it made no difference. > > Still the host timeout. > > > > ----------- > > Lee Parsons > > LAN Administrator > > The Minnesota Daily > > www.mndaily.com > > > > On Tue, 19 Mar 2002, Doug Silver wrote: > > > > > > > > Perhaps a bit more detail would let us figure out the problem. For > > > example, here's my setup: > > > > > > Amanda server: 172.16.20.140 (private IP) it's resolv.conf allows it to > > > resolve both internal and external names since I have an internal DNS > > > machine. I back up a bunch of private IP's (172.10.x) and external > > > (public IPs). > > > > > > Do you have an internal dns server that the amanda server can use to > > > resolve all IPs? I'm not sure if Amanda would use /etc/hosts to resolve > > > IP/names, so that might be a cause too. > > > > > > When you said you tried pointing to the internal machines by their NAT > > > addresses, don't you mean the external machines? Regardless, on the > > > server, recheck inetd, HUP it, and run 'amcheck -c CONFIG'. There should > > > be some sort of /tmp/amanda debug files available. > > > > > > -- > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > Doug Silver > > > Network Manager > > > Quantified Systems, Inc > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > > > > > > > > >
