Tuesday, July 17, 2012

IBM Sametime Community server - with tunneling. Port 80 already in use. Issue & Solution

When you have a "tunelled enabled" Sametime Community server, port 80 is used by the Sametime MUX and port 8088 is usually in use by the Domino HTTP server.

I got a call this morning from a customer that had issues where port 80 did not work for their Sametime Community server anymore, and port 8088 was working just fine.

After a lot of debugging (checking if firewall was blocking the traffic, checking if IIS was installed and allocating port 80, etc etc. Nothing seemed to be out of order.

I then shut the Domino server down, and did a "netstat -ano" in the Command Prompt on the Windows server.
At the top it said that the server was listening to port 0.0.0.0:80 and the pid #4 pointed me to the process called "System" in the task manager.

C:\Users\administrator>netstat -ano

Active Connections

Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 904


Hmmm.

I also noticed this in the Sametime Trace log:



Already in use?? Ok, then I seeked out to my dear friend Google, and found this article:
http://techie.prepys.com/archives/2009/08/05/windows-2008-port-80-in-use/

Aha!!!

So I opened up the Windows services console and shut the service down, started up Domino and voila.






After chatting with the customer, they had not done any changes to the server that might have caused this... They had "only" done an upgrade to Windows 2008 R2 service pack 1. So somewhere, somehow, the WinRM service got enabled. I´m uncertain whether the service already existed prior to SP1 or if it got installed with SP1, but anyhow, now it´s disabled and Domino is a´OK again.

Remember to set the service to "Manual" or "Disabled" so that it won´t cause the same issue after a windows restart :-)

Cheers