TFTP not working since Sierra Upgrade

Question

Level 1

5 points

TFTP not working since Sierra Upgrade

I am a network engineer, however not a "Bash" guru so I need some help. Since my upgrade to Sierra I am inable to get TFTP working either natively or through 3rd party apps like Pumpkin or SecureCRT.

These both worked prior to the upgrade. I actually get differing results based on the application as well.

Natively if I turn on TFTP via Terminal I can see that it is running via a netstat. When I turn it off I can see that as well, however when I start Pumpkin it says the port (69) is already in use by the OS.

In Secure CRT the TFTP server appears to start and work, but when a file is transferred to it it fails with the following error:

Wed Feb 8 07:53:24 2017,31735,[::ffff:10.110.254.37]:53841,Error writing data to transfer socket: Invalid argument

I am pulling my hair out on this, has anyone else experienced this issue and found any resolution?

MacBook Pro, iOS 10.2.1

Posted on Feb 8, 2017 8:13 AM

Reply

Answer 1

Jun 2, 2017 6:57 AM in response to jmfleming

I have the exact problem. I've tried three different tftp servers (native, securecrt, and tftpserver). All of them show running with a netstat, but according to nmap scans, port 69 remains firmly closed. I want to use securecrt to tftp code to my switches as required. This is driving me nuts!

I am running the beta 10.12.6.

I had this problem for a while, I just used a different box to do the uploads. I believe I had the same problem under El Capitan and Sierra

Reply