On Wednesday 22 February 2006 12:08, you wrote:

> "...large part..."   

2 hosts out of the 3 hosts in the disklist.

> and "...both of them..." 

The 2 on the dmz. The amanda server was fine.

> What is the exact error message?  (That help to find the lines in the
> source code too.)

------------------------------------------------------------
Amanda Tape Server Host Check
-----------------------------
Holding disk /usr/local/amandadisk/sls: 178157244 kB disk space available, 
using 178157244 kB
NOTE: skipping tape-writable test
Tape sls-5 label ok
Server check took 6.560 seconds

Amanda Backup Client Hosts Check
--------------------------------
ERROR: log.slsware.dmz: [addr 192.168.20.239: hostname lookup failed]
ERROR: server.slsware.dmz: [addr 192.168.20.239: hostname lookup failed]
Client check: 3 hosts checked in 0.049 seconds, 2 problems found

(brought to you by Amanda 2.4.5p1)
------------------------------------------------------------

> Strange thing is that you say "name lookup failed", but apparently
> the name is already translated into an IP-number...

I thought so too.

> Do you mean that one host should be 192.169.20.20 and the other
> 192.168.20.218?

Yes.

> Just a wild guess...  DHCP?   

The host doing DHCP on the dmz leases from .241 to .254.

.239 *is* in the NAT range the PIX uses from the lan to the dmz -- the top 
address. 

...

Fixed. Evidently the PIX has been assigning from lower in the range for the 
past months and just last night decided to use the highest (that might bear 
looking into). And I'd neglected to put .239 in DNS and .amhosts on the 
clients. Fencepost error.

So the hostname amanda was referring to was not the client, but the server.

Never mind, and thanks to all. Good guess, Paul :-)

-- 
Glenn English
ghe AT slsware DOT com
GPG ID: D0D7FF20