Openfire running as a service, but can't connect

We just installed Openfire on a Windows Server 2003 system hitting an SQL Server 2005 database on a seperate system. When the GUI server is running, the Spark clients can connect fine, until you log off the server, terminating the GUI server. I have run the openfire-service installer as indicated in the documentation and have started it. It shows as started in the ‘Services’ console. However, we cannot connect with any clients when the GUI server is not running.

Any ideas?

Can you connect to the admin site for your openfire server from a web browser from a different computer?

Yes, I can. I did have to open that port up when I installed it though.

Does Openfire use a different port if it is running as a service than if it is running in GUI?

No it still uses port 9090 for the admin site.

So with only the service running, the client gives a Login Error - ‘Can’t connect to server: invalid name or server not reachable.’

If I remote into the server, and start the GUI server, it states this when initialising:

Error creating server listener on port 5269: Address already in use: JVM_Bind

Openfire 3.6.0 [Oct 1, 2008 10:03:30 AM]

Admin console listening at:

http://*013..*****.:9090

https://*013..*****.:9091

Starting Fastpath Server

Error starting server listener on port 5269: null

(server name obscured for security)

But it now works fine and the client can connect straight away.

Is the service set to automatic? If it is restart the entire computer. Do not login. Try to access the opefire admin site via a web browser form another computer.

I just wanted to say thanks Todd. This helped me out tremendously.

Is this still an issue for the original poster?