Problems moving Seaside to port 80 on Windows

I booted up my Windows PC, and started Seaside, which defaults to running the web-server on port 8080.

I stopped the process, and changed the port number, (action-clicking on the the top pane of the Seaside control panel, then selecting 'Port...' from the menu), then re-starting, and got an error message.

I inferred from the error that port 80 was already in use.


So, at the  Windows command prompt  (Windows Start Menu, "cmd", or "cmd" and Shift-Control-Enter from an administrator account, to run with Administrator privileges)

NETSTAT -p tcp -ano

List all (-a) the ports using the TCP protocol  (-p tcp) in numerical form (-n), and display the process id (PID) for the owning process (-o).

This was good, but it gave a PID of 4112 - which was not appearing on the list of processes and services in Windows Task Manager.

I then ran :

tasklist /FI  "PID eq 4112" /FO table

Which lists the active tasks and processes /FIlterered by process Id equal to "4112", in the /FOrmat of a table  (can also be a list or a csv).

It turned out to be Skype that had control of port 80.  I killed Skype, and everything was ticketty-boo.