CTR 2.0.4.135 autoupdate failure

[Volker Janusch]

Dear Madam or Sir,

the floowing failure occured:

"Alarm Status: Auto update failed using ftp://ftp-sj.cisco.com/cisco/crypto/3DES/ciscosecure/ids/ctr/updates/ctr-updates-2.0.xml. Please correct! (Failed to open url "ftp://ftp-sj.cisco.com/cisco/crypto/3DES/ciscosecure/ids/ctr/updates/ctr-updates-2.0.xml". null)"

The page to download the updates manual is accessible. I updated the database with the manual update file "ctr-policy-2.0.4.137.S117-K9.exe". It works.

If I try to connect the url "ftp://ftp-sj.cisco.com/cisco/crypto/3DES/ciscosecure/ids/ctr/updates/ctr-updates-2.0.xml", the browser (proxy) sends the following information:

"The following URL could not be retrieved: ftp://ftp-sj.cisco.com/cisco/crypto/3DES/ciscosecure/ids/ctr/updates/ctr-updates-2.0.xml

Squid sent the following FTP command:

CWD cisco

and then received this reply

/cisco: Permission denied"

Is there a mistake with the access rights?

Best Regards.

Volker

[cskipper]

CTR does not support FTP. Replace ftp:// with http://

[Volker Janusch]

Thank you for this hint.

After replace ftp:// with http:// the following failure occured:

failed to get http protocol response code when opening url "http://ftp-sj.cisco.com/cisco/crypto/3DES/ciscosecure/ids/ctr/updates/ctr-updates-2.0.xml"

I can connect this url with CRT-Servers browser without any failure.

[cskipper]

use:

http://ftp-sj.cisco.com

CTR appends the rest.

If this still does not work, manually download the latest update, execute it on your CTR box, then change your autoupdate location to https://localhost

Thanks

[Volker Janusch]

We use this "manual" option sice this failure was occured. The reason for this request was to go back to automatic signature update. It was working for a long time. Where is the failure?

Should I say to the customer "bad luck"?