>Ok, if you run this: >nslookup `hostname` > >on the amanda server, does that resolve? ...
That may not be relevant. Amanda does not use DNS (directly). All it does is call gethostbyname(), which is a standard system call that "does the right thing", depending on how you have configured your system. For instance, on my Solaris boxes, I set up /etc/nsswitch.conf to look to DNS first and then fall back on /etc/hosts (there are numerous other combinations). Running nslookup only tests DNS. If gethostbyname() isn't also using DNS, this isn't telling you anything. This is why I spent all of five minutes one day writing command line versions of the three standard calls Amanda makes (I'm thinking of tossing these into the Amanda release): ftp://gandalf.cc.purdue.edu/pub/amanda/gethostbyaddr.c ftp://gandalf.cc.purdue.edu/pub/amanda/gethostbyname.c ftp://gandalf.cc.purdue.edu/pub/amanda/getservbyname.c Compile these up (may take a little tweaking, depending on your OS) and then: * On the server, use gethostbyname on the client name from the disklist. Do you get back the IP you expect? * Go to the client and run gethostbyaddr on the IP you *think* the server is presenting itself as. * Then run gethostbyname on the client result, on the client, and make sure you get back the IP you started with. In the special case of the server not being able to back itself up, that sounds more like a problem setting up amandad. There are a couple of articles in the FAQ about this. Finally, I wrote up how Amanda uses ports in docs/PORT.USAGE (it was also posted here quite a while ago). If you don't have the file, grab a copy of the 2.4.3 beta test just to get it. Or ask me offline and I'll send it to you. It's not all that great a debugging paper, but does faithfully (I hope) describe exactly how Amanda does its port allocation, and maybe that will trigger an idea. >Doug Silver John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
