Cisco ASA 5505 TFTP (Access Violation)

[Matt S]

I am trying to send a new asdm image to my cisco asa 5505 firewall. I have tftpd64 installed on Server 2008 R2 and the file I'm trying to send is in the same directory as the tftpd64; so it is accessible. The tftpd64 shows the IP of the server, security is set to none, and is set to tftp server (in settings under GLOBAL tab)

On the cisco asa 5505 I have performed the following command to give access to the tftp server and copy the file

cisco(config)# tftp-server inside 10.4.1.3 255.255.255.0

cisco(config)# copy tftp disk0:

Address or name of remote host [10.4.1.3]?

Source filename [255.255.255.0]? asdm-771.bin

Destination filename [asdm-771.bin]?

Accessing tftp://10.4.1.3/asdm-771.bin;int=inside... %Error reading tftp://10.4.1.3/asdm-771.bin;int=inside (Access violation.)

I am not sure why I'm getting access violation. I was able to transfer the file from a remote machine through a VPN connection but the speeds are so slow it timed out at around 15%. This is why I decided to move the file to the remote server and then do a tftp transfer of the image file.

[Georg Pauwen]

Hello Matt,

is the IP address of the PC in the same subnet as that of the server, 10.4.1.0/24 ?

[Matt S]

Yes, the PC is 10.4.1.101, server was 10.4.1.3, and asa was 10.4.1.1

[Marius Gunnerud]

I haven't worked with servers in quite a while now, but remembering back to when I did work with them, I remember that the 2008 R2 had some really strict and (in my opinion) strange security setting.  for example, I was trying to pre-stage a server 2008 R2 for a client but I was unable to do so unless the server detected another device on the local network.

So I do not know which security settings it would be that need to be changed.  Perhaps someone else here knows..

--

Please remember to select a correct answer and rate helpful posts

[chris-goulder]

One cause for this is if the server you are trying to run tftpd on is already running the windows deployment services server (WDSS), which includes a tftp service and that will own udp port 69 on the platform.

In this case tftpd will run without warnings but when tftp'ing to the platform you are talking to WDSS and not tftpd

netstat -a -b will show if port 69 already listening and which process owns it

If WDSS running, temp disable it while you run tftpd

(the WDSS tftp service itself is not great)

[godfrey_mungora]

Had ran into the same problem issue was i was running tftpd32 with a standard windows account, make sure you run it as admin.