Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foo_upnp The UPnP Media Server could not be started (Read 3380 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foo_upnp The UPnP Media Server could not be started

Can somebody help me what do to if:

The UPnP Media Server could not be started. Port 56923 *might* be in use by another application or foo_upnp instance.

I deinstalled foo_upnp.fb2k-component and installed new.
The same Popup

 

Re: foo_upnp The UPnP Media Server could not be started

Reply #1
Do you use torrent? Or other download clients/protocols? Do you host or connect to any specific services (game servers, home media server, home confort control systems, IP intercoms, SIP services, whatever else)? I suppose you get this error because something like this occurs on your OS. Does the same error occurs after PC is restarted? If not I suppose it is something like torrent (randomly choosing port at each stary). If yes, then try netstat command from Command Prompt (look for switches list to see enough details) or Wireshark for more advanced network traffic analysis.

Re: foo_upnp The UPnP Media Server could not be started

Reply #2
Hello,
I am facing the same error message.
I checked all that and could observe that changing the port helps just for a while. No idea which program blocks/uses that port randomly. Even when I switched to another port, it just worked for a short time. So I frequently change the port manually. Maybe a different port range might help in my situation.
Netstat wasn't helpful strangely oO
Yours

Re: foo_upnp The UPnP Media Server could not be started

Reply #3
Try to close Mirouter.exe (if you use it)