Are you sure the server receive the request?
Did amandad get execute on the server? Post its debug log.
Check your firewall/network log.

Jean-Louis

fedora wrote:

hi all,

I am having problem with amrecover..

amrecover DailySet1
AMRECOVER Version 2.5.1p3. Contacting server on server.com ...
[request failed: timeout waiting for ACK]

the amrecover debug file was:

amrecover: debug 1 pid 12565 ruid 0 euid 0: start at Tue Oct 30 16:35:10
2007
Reading conf file "/usr/local/etc/amanda/amanda-client.conf".
Reading conf file "/usr/local/etc/amanda/DailySet1/amanda-client.conf".
amrecover: debug 1 pid 12565 ruid 0 euid 0: rename at Tue Oct 30 16:35:10
2007
security_getdriver(name=bsd) returns 0x50a0e0
security_handleinit(handle=0x8c04660, driver=0x50a0e0 (BSD))
amrecover: bind_portrange2: Skip port 706: Owned by silc.
amrecover: bind_portrange2: Skip port 707: Owned by borland-dsj.
amrecover: bind_portrange2: Try  port 708: Available   - Success
amrecover: dgram_bind: socket bound to 0.0.0.0.708
amrecover: dgram_send_addr(addr=0xbfc07310, dgram=0x50b004)
amrecover: (sockaddr_in *)0xbfc07310 = { 2, 10080, 202.53.250.162 }
amrecover: dgram_send_addr: 0x50b004->socket = 3
amrecover: dgram_send_addr(addr=0xbfc070b0, dgram=0x50b004)
amrecover: (sockaddr_in *)0xbfc070b0 = { 2, 10080, 202.53.250.162 }
amrecover: dgram_send_addr: 0x50b004->socket = 3
amrecover: dgram_send_addr(addr=0xbfc070b0, dgram=0x50b004)
amrecover: (sockaddr_in *)0xbfc070b0 = { 2, 10080, 202.53.250.162 }
amrecover: dgram_send_addr: 0x50b004->socket = 3
security_seterror(handle=0x8c04660, driver=0x50a0e0 (BSD) error=timeout
waiting for ACK)
security_close(handle=0x8c04660, driver=0x50a0e0 (BSD))

any helps would be appreciated. :-D