I had an issue where I couldn’t start a web server on a Windows Server as something was already listening on TCP Port 443. netstat -a -b just showed me that something was listening on 0.0.0.0:443 but also said that it “Can not obtain ownership information” Through some googling, a few people reported that the Routing and Remote Access service would attach to port 443. I went into Services, stopped the service and set the startup to manual and then this freed up port 443 for the web server.
Windows Service with PID 4 listening on TCP Port 443
I had an issue where I couldn't start a web server on a Windows Server as something was already listening on TCP Port 443. netstat -a -b just showed me that...
Keep This Useful
Spotted something outdated or unclear?
If a step has changed, a screenshot no longer matches, or something here just does not work the way it should, get in touch and we will take a look.