01-30-2006 02:47 AM - edited 03-10-2019 01:52 AM
Hi
While trying to upgrade IDS 4235 (Version 4.1(1)S47) using FTP or IDM, it gives "Error: exp timeout" message. What could be the reason?
If the FTP server is a Windows XP machine, and the signature/service pack file is in C:\Inetpub\ftproot, what is the exact URL we have to specify with the upgrade command / IDM. Does it need to specify the relative directory or absolute directory in the URL?
Thanks in advance.
Regards // Anoop
01-30-2006 06:40 AM
The ftp client logic in the 4.1(1) sensor was not very robust. It is probably not compatible with your ftp server. The ftp client in 4.1(5) and 5.x is much more robust. Here is a workaround until you get to 4.1(5):
- from service account, manually ftp the upgrade pkg file over to the sensor (into /tmp directory for this example)
- from cli "conf t; ssh host
- now perform a "local upgrade using scp":
up scp://service@
02-01-2006 02:18 AM
Hi
Thanks for the reply. Is this the only workaround for upgrading the IDS? Is there any way to upgrade the IDS other than using the service account as mentioned in your reply?
Please reply.
Thanks & Regards // Anoop
02-01-2006 06:43 AM
Remember this workaround is just for 4.1(1). Once you upgrade past this version you should be able to use any ftp server.
You can try another ftp server or check your ftp server config - cannot use custom hello/goodbye prompts
NOTE: anonymous accounts do not work
You can also use "scp" file transfer protocol and copy the upgrade package from an ssh server:
up scp://user@
02-01-2006 06:49 AM
Your ftp server should allow you to setup up users and a users home directory:
user: test
home dir: c:\ftpserver
So copy the sig/service pack package file into c:\ftpserver then use a relative path - see the following upgrade command:
up ftp://test@1.2.3.4/
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: