When I try to use the PDM to save my PIX configuration to a TFTP server, I get an access violation. Here's what I specified:
I told the PDM to create a file named "pixconfig". The PDM accepted that just fine.
when I went to do the actual save, it told me "Configuration file name must start with "/". It wanted me to put a "/" in front of the "pixconfig" file name. When I did that and then tried to save the configuration:
The PIX said: TFTP write '/pixconfig' at 192.168.10.4 on interface 1
My TFTP server said: Error EACCESS on file /pixconfig. Ext error The directory name is invalid. [30/08]
I then tried to create a directory named "pixconfig" below the TFTP root folder and have the PIX create a file named "new" using the path /pixconfig/new but got the same error messages.
I have students having this same problem and I have to find a fix for it. Any ideas?
Your configuration part in PDM is correct. When you enabled TFTP server (Admininitration-TFTP Server), you basically need to enabled the inside interface, assign IP and on the path, you just need to put '/'. Then apply.
If you check your PIX from CLI, you should see something like:
tftp-server inside /
The '/' will be associated with the default tftp directory/folder specified in your tftp server. PIX will just push it to TFTP server, and TFTP server will know which directory to save the config file.
So, if you want to save the running config (File-Save Running Configuration to TFTP Server...), give any filename with extension, i.e config-31aug2006.txt.
I have this thing running fine. TFTP server is 3CDaemon. Alternatively, try to use other tftp server.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...