XAMPP & NOD32 Confliction?

[James]

I've just installed the latest XAMPP (1.7.4 - previously used 1.7.3) and now the apache server won't start.

I did netstat -anobv and found that the process ekrn.exe is using port 80 (xx.xxx.xxx.xxx:80). The problem I have is that it is a mandatory service that cannot be stopped.

I tried disabling all protection on my anti-virus but apache still doesn't want to start.

Is there a resolution to this that anyone is aware of?

 

[Paul B]

I had the same problem with Skype and IIS.

There is a way of forcing XAMPP to use another port, I'll see if I can find it.

Edit: Try this - http://veerasundar.com/blog/2009/07/how-to-change-xampp-server-port/

Or possibly this - http://varunkrish.com/making-apachexampp-and-iis-work-together.html

 

[Enigma]

There is most likely a setting in ESET NOD32 to tell it not to camp out on port 80. For the Skype conflict, just tell it not to use port 80 in Tools => Options => Advanced => Connection => Use port 80 and 443 as alternatives for incoming connections.

 

[Paul B]

Changing ports in Skype didn't work for me.
I had to uninstall it, install XAMPP, then reinstall Skype.

I never found a way around IIS though, that did require changing the port for XAMPP.

 

[Enigma]

No need to change Skype's port. Unchecking "Use port 80..." and maybe restarting Skype/the box should do it. Works for me anyway.

 

[bambua]

Changing ports in Skype didn't work for me.
I had to uninstall it, install XAMPP, then reinstall Skype.

I never found a way around IIS though, that did require changing the port for XAMPP.

It depends on the version of IIS, but for all of them you can set the port bindings for the Default Web Site and as long as you do an iisreset after the change it will free up the port binding.

 

[James]

Changing the ports in the 2 areas in the httpd.conf didn't work - xampp still boots apache on 80.

I haven't got Skype running but it doesn't use port 80 anyway.

 

[James]

OK I've managed to disable port 80 being used (disabling nod32's http checking).

 

[James]

But still Apache isn't working, even after a restart...

perhaps reinstalling it.