🚀 go-pugleaf

Ulli wrote:

> my WebServer is most ready now. But now I tried to use it on a Win XP 
> Home system. First start is ok but on second start I get error message 
> "Could not bind socket. Adress and Portnumber are alredy in use". Does 
> XP home use IP Adress and Port in an other way then XP Professional? 
> Because this is not on XP Professional. Any idea?

Can you confirm that after every reboot the first start is ok
and the second finds the port in use ?

What I have here on XP-Home since some months that webservers
complain in the same way.

Now when you open a console window and type
netstat -nab
you will find a list of all ports in use including the executable
who has opened it.

(If the list is too long the command will disappear and you will
not see the top of the list. In that case try
netstat -nab > c:\netstatout.txt
and inspect netstatout.txt

Here at the beginning of the list I get:

   Proto  Lokaal adres          Extern adres        Status           PID
TCP    0.0.0.0:80             0.0.0.0:0              listening    2020
   [lsasss.exe]

TCP    0.0.0.0:135            0.0.0.0:0              listening     1216
   c:\windows\system32\WS2_32.dll
   C:\WINDOWS\system32\RPCRT4.dll
   c:\windows\system32\rpcss.dll
   C:\WINDOWS\system32\svchost.exe
   -- parts unknown --
   [svchost.exe]

So lsasss.exe is to blame.

Now with <Ctrl><Alt><Delete> the taskmanager shows this instance
of lsasss.exe. When I kill it then a webserver can be started
on the http-port 80.

There is also a lsass.exe.

Why XP does start lsasss.exe and what it is doing I don't know.
Once when trying to connect with the browser I got a message that I did
not have enough permissions.

Had a deeper look now. lsass.exe is from microsoft. But lsasss.exe not.
What is on my computer ?

Would be glad to here from someone.

Hans.