Conection refused with Windows 2003 server

[pcardelli]

I'm having trouble figuring out how to allow port 2144 to receive requests. Even when I type hq-agent status I get the following message:

Unable to connect agent: Unable to connect to 127.0.0.1:2144: Connection refused : connect

I have installed the server on another administrative machine and everything works except connecting to a Win 2003 server. Windows Firewall is not active, so I'm a little stumped. Any help in the right direction would be appreciated, as I really want to use this to monitor my network.

[jtravis_hyperic]

Is your agent running, when you perform a status command? It will
need to be running before it can connect via 2144.

-- Jon


On Jul 23, 2007, at 3:51 PM, pcardelli wrote:

> I'm having trouble figuring out how to allow port 2144 to receive
> requests. Even when I type hq-agent status I get the following
> message:
>
> Unable to connect agent: Unable to connect to 127.0.0.1:2144:
> Connection refused : connect
>
> I have installed the server on another administrative machine and
> everything works except connecting to a Win 2003 server. Windows
> Firewall is not active, so I'm a little stumped. Any help in the
> right direction would be appreciated, as I really want to use this
> to monitor my network.

[pcardelli]

I rebooted and reinstalled the agent. Then ensured the agent service was running. When I ran the hq-agent.exe status everything worked. Then when I checked the HQ server things started coming to life.

[jtravis_hyperic]

So all is well?

-- Jon


On Jul 23, 2007, at 5:03 PM, pcardelli wrote:

> I rebooted and reinstalled the agent. Then ensured the agent
> service was running. When I ran the hq-agent.exe status everything
> worked. Then when I checked the HQ server things started coming to
> life.

[pcardelli]

I'm not sure what exactly happened, but all is well, and I'm ready to
test out Hyperic HQ and see what all it can do to simplify my job a
little bit. Thank you for your comments, as that could have been the
problem. It also could have also been the fact that my server was due
for a reboot for other pending patches and updates. Either way I
reinstalled and made sure that the HQ-agent service was running by
actually starting the service and then in the command prompt typed
hq-agent.exe status.

I am amazed at how fast you responded to my question, as I expected it
to take a day or two.

~Paul