unable to bind to 1900 WIN7x64

[Chuck_Arch_Ums]

Try setting a port number like 3667 for example in General settings tab, force port of the server and try again.

[Chuck_Arch_Ums]

have you open the port 1900 in windows firewall for UMS?
Seem to be the problem?

[Nadahar]

You're focusing on the wrong port. The web interface (HTTP) is running on port 9001 by default, the content transfer (HTTP) is running on port 5001 by default. These can be modified, but aren't the problem here.

Port 1900 is used for UPnP traffic, and can't be changed. It's defined in the UPnP standard an all UPnP devices must use this port. This port is also reserved exclusively for UPnP use, so no other services should use it: https://en.wikipedia.org/wiki/Simple_Se ... y_Protocol

While the HTTP ports are "acquired" by the process that binds to them, so that they are unavailable for all other processes on the same IP/NIC, port 1900 is supposed to be shared - so that any number of processes can all listen to this port. If UMS can't bind to port 1900, it means that: 1) There's some other software running that has somehow managed to wrongly bind exclusively to this port 2) Some kind of "security system" (firewall, OS permissions etc) preventing access to the port.

There is nothing that can be done with UMS to change this, it has to use this port. The solution is to find the reason UMS can't bind to this port, and resolve that. My guess is that some "rogue software" is running is causing this.

[Nadahar]

Opening a powershell or command line as administrator and running "netstat -abo" should be a good start. It will list all ports currently in use and what processes that use them.

[Nadahar]

It's a bit hard to read the netstat output, but as I read it, "Transfer.exe" isn't involved with port 1900. It's only svchost.exe twice. svchost.exe is a process that runs all Windows services, so it could mean any number of different software. That said, Windows itself also use port 1900 for its "home group" functionality, so it's normal to see svchost.exe using port 1900.

I would try to stop any service that seem like it is some kind of UPnP based service, and just see if it made a difference (run "services.msc" to start/stop services). If you don't find anything there, I would try to disable any firewalls and virus software you have running (just temporarily) to see if one of those block access to the port.

Apart from this, I'm really our of ideas.