Hi Kent - I have cloudflare SSL and ports 443/8443 on my server. Server was running fine.
Recently told by server support that we were getting attacked on port 389 so I closed it.
Now, I get the dreaded "Could not bind socket" message when I try to start the server.
Auto start server is set to OFF. Keep alive connections is set to YES.
Not sure what to try now.
"Could not bind socket" after closing port 389
-
- Site Admin
- Posts: 5880
- Joined: Wed Mar 19, 2008 8:47 pm
Re: "Could not bind socket" after closing port 389
Bring up the Windows Task Manager (right-click the Windows taskbar at the bottom of the screen) and look for PMServer.exe on the Processes tab. If it's running under a different Windows login then you'll need to check the "Show processes from all users" option. There you can force-close it.
Re: "Could not bind socket" after closing port 389
Oddly enough, there's only one instance running. This is on Windows Server 2016 DC. The Task Manager looks a little different.
-
- Site Admin
- Posts: 5880
- Joined: Wed Mar 19, 2008 8:47 pm
Re: "Could not bind socket" after closing port 389
Close that copy and then look on the Details tab in the task manager and see if there is another PMServer.exe running.
Re: "Could not bind socket" after closing port 389
There is not. I just tried starting PMserver after checking that it was not currently running, and the same thing happens. So odd. Only change was the firewall rule add for port 389 - grrrrKent Briggs wrote:Close that copy and then look on the Details tab in the task manager and see if there is another PMServer.exe running.
-
- Site Admin
- Posts: 5880
- Joined: Wed Mar 19, 2008 8:47 pm
Re: "Could not bind socket" after closing port 389
Have you tried a reboot?
Re: "Could not bind socket" after closing port 389
Several tiimes.Kent Briggs wrote:Have you tried a reboot?
I've started the process of reinstalling on a new cloud image. I'll let you know how it went when done.
-
- Site Admin
- Posts: 5880
- Joined: Wed Mar 19, 2008 8:47 pm
Re: "Could not bind socket" after closing port 389
Are you sure the Microsoft IIS webserver isn't running? It would bind 80 and 443 for itself.
-
- Site Admin
- Posts: 5880
- Joined: Wed Mar 19, 2008 8:47 pm
Re: "Could not bind socket" after closing port 389
Also see this link for how to hunt down which process is using a particular port:Kent Briggs wrote:Are you sure the Microsoft IIS webserver isn't running? It would bind 80 and 443 for itself.
https://www.printsupportcenter.com/hc/e ... cks-a-port