Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 3 subscribers
  • Views 1956 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Why is sophos using port 69 (TFTP)?

givemecontrol

So i went to run my TFTP server to back up some cisco configs this AM as i do every few months, but lo and behold i cant bind to the port. Thats weird i say as i run netstat -a -b -n to see what i have done here..

Turns out i did nothing. its the SAV service that is running on port 69. Can you please explain this? was not like this before, and obviously i need my tftp server to work. What the heck is going on here sophos?

 

this is just a desktop machine, my desktop  machine...

 



This thread was automatically locked due to age.
  • +1

    Hello givemecontrol,

    this looks like a regular netstat output. Please note that the owning process is shown after (below) the port. Thus it might or might not (I assume the latter) be SavService.exe that is listening on port 69 ...

    Christian

  • 0 in reply to QC

    ooof! good catch QC, you are correct that it was not sophos. My bad!

  • 0 in reply to givemecontrol

    Hello givemecontrol,

    an understandable mistake. netstat's output format is somewhat elusive given that the process name starts in column 1 while connection information is indented, quite counterintuitive. Intending to reply to your initial post I ran netstat and was puzzled that SAVService seemed to listen on UDP 161 ... SNMP? ... noticed the final lines and only then remembered the weird arrangement of the output.

    Christian

Unfiltered HTML