cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
501
Views
0
Helpful
5
Replies

tftp service

rbatchu
Level 1
Level 1

Hi

Our pix 525 running with 6.2.2 has been configure with three interfaces inside (192.168.1.x), outside and dmz (172.168.3.x)

wri net 192.168.1.10 pix-config. I m able to save the pix config to my internal tftp host. and That is works fine.

Problem is when is I m unable to push config to a tftpserver in DMZ (172.168.3.x) network.When I try to do this, Pix still try to access iniside interface instead of dmz interface.

what could be up?

5 Replies 5

a.awan
Level 4
Level 4

Try setting the tftp server ip address using the tftp-server [interface_name] [ip_address] command. By default the PIX assumes that the TFTP server resides on the inside interface as it is more secure. The above mentioned command should let you setup a tftp server on the dmz and then you can just issue the command 'write net :pix-config'.

No luck

pix# sho tftp

tftp-server dmzlan 172.168.3.25 c:\cisco

pix# wri net:pixconfig

Usage: write erase|floppy|mem|terminal|standby

write net []:

Any Ideas??

When the pix tells you Usage: then that usually means there is a syntax problem. Its been a while since i have worked on a PIX but i think you will need a space between net and the :

In short "write net :pixconfig" should get you working.

Still no luck.

I m able to ping the tftp server from the pix. and I also made sure that tftp service is running.

but i get an unspecified error. I couldnt see anything in pix logs.

pix# sho tftp-server

tftp-server dmzlan 172.168.3.25 c:

pix# ping dmzlan 172.168.3.25

172.168.3.25 response received -- 0ms

172.168.3.25 response received -- 0ms

172.168.3.25 response received -- 0ms

pix# wri net :pix-config

Building configuration...

TFTP write 'c:/pix-config' at 172.168.3.25 on interface 3

Unspecified Error

[FAILED]

Well at least now the PIX is trying to use the interface you want to access the TFTP. I think the problem lies in either the path you are giving or the TFTP server's permissions. Try to get some logs from the TFTP server itself and see if it is actually seeing any connection initiations.