Vista - TFTP Server Problem

I'm trying to start a local tftp server session using SolarWinds or WinAgents TFTP Server Manger. However I keep getting the following messages:

"WinAgents TFTP Server can not bind to UDP port 69 on one of local network
interfaces. Probably, the port is used by other application. Please stop other
software running on UDP port 69 and restart WinAgenst TFTP Server"
or

"SolarWinds UPD port 69 is currently used by another process: TftpService"

When I tried to identify the program using UDP port 69 using the netstat -anb
command I can't find anything that indicates that this port is in use.

Has anybody encountered this problem I neee to use TFTP to copy an IOS from my laptop to a Cisco 2600 router.

Any help would be greatly appreciated!

Interesting. Does NETSTAT -NAO likewise fail to reveal any UDP69 bindings? Does the same app error occur if you boot to [safe mode + net]?

I'm attaching a text file with the results of netstat -nao the first results with the wireless on no physcial connection. The second text file is with the wireless off and a physical connection to my router it appears that the DHCP address assigned to the wirelsss card is associated with UDP port 69 either way.

I hope this helps.

PID 3096 is bound to UDP69, so the TASKLIST command can now tell you what that process is. Just search for 3096 in the TASKLIST output or use this:

TASKLIST |find "3096"

Since PIDs are process instance-specific, the next time that process restarts it will amost certainly have a different PID, so you may need to do the NETSTAT thing again.

I did execute TASKLIST |find "3096" but with no results. :-( One quick question the tftp feature that is enable in "Windows Vista Features" does this need to be disabled? I'm assuming this feature does not enable my laptop as a tftp server.

Regards,

Danny

Every time a process (re)starts, its PID will be different. For example, if I start Notepad, its PID might be 576 the first time, then 3096 on restart, then 1028 for the 3rd instance...

Since NETSTAT does find a process bound to UDP69 on your machine, it's just a matter of following up relatively quickly with TASKLIST to check the corresponding PID before the process has a chance to restart.

You can also match a PID to a process name from Task Manager. Click the "View" menu, add columns, and tick the PID box.

I'd suggest not focusing on any particular Windows "feature" until you know what that thing bound to UDP69 is. It may have absolutely nothing to do with Windows.

Ok as per the attached .txt file I've discoverd the related application to the PID number discovered in netstat. The million dollar question how to I stop this file from executing?

There's $1E6 riding on this? Why didn't you say so before?

OK, so it's something calling itself "TftpService.exe". That is a fairly generic name, but I note with interest that web searching suggests it might correspond to "WinAgents TftpServe" - the very thing you're trying to install, if I understand correctly.

So one explanation for your issue might be that you're trying to install a second instance which fails to bind to UDP69 because the first instance of the app is already running.

Otherwise, if you want to check the full path to "TftpService.exe" in the hope of determining its install location, start the Task Manager (ctrl+shift+esc), click the "View" menu, select columns, tick the "Image path name" box, and then find TftpService.exe in the list of processes - you should then be able to see the full path to the EXE file.