ASA 5505 writes running-config to tftp for some machines, not others

[enjama]

Hello -

We have a 5505 that writes the running-config to one machine in the subnet (192.168.3.77) successfully, but won't write to two others: 192.168.3.30 and 192.168.3.103 (DHCP). 

The two machines that we cannot write the config to have similar outcomes: The filename is written, but the file is zero bytes.  The tftp log shows errors - " I/O error during upload. Retrying to send data. Block 0. Retry number XX" using the IPSwitch TFTP server, and using the solarwinds tftp server (V10 AND V9) we get "TFTP connected from binary put started" and then nothing.

We have tried multiple tftp servers on the machines that can't be written to, and made sure permissions are write-enabled (mimicking the setup on the working machine).

I have attached the running config, please let us know if we are missing anything.

[Philip D'Ath]

What happens if you try to tftp put a file yourself from your own computer to the affected servers?

[enjama]

We've narrowed it down to the tftp implementation, but were unable to fix it.  We implemented a workaround that isn't as elegant, but it works - we cut and paste the ssh buffer to a file for backup.

[johnd2310]

Hi,

Have you checked antivirus and firewall settings on the machines?

Thanks

John