PowerChute Business Edition and Hyper-V Core 2016

[Anonymous user]

I installed PowerChute (10.x) on the server core. It found the UPS and the Agent service runs fine. Now I try to (remotely) connect to the agent using a web browser https://:6547, but to no avail. Doesn't make a difference if I use the FQDN or IP-address. Restarted the Agent service a couple of times, but nope. Performed netstat -a and notice the localhost (0.0.0.0) is listening on port 6547, but it's not listening on the core's IP-address. Removed and re-installed the software, but that doesn't make a difference. How to get things going?

Simon

[BillP]

Hello,

When running netstat - a the port should be listed as TCP  Local Address 0.0.0.0:6547 Foreign Address Domain Name:0  State = Listening You should also see TCP Local Address [::]:6547 Foreign Address Domain Name:0 State = Listening

You can check the status of the firewall using Powershell The command is Get-NetFirewallProfile 

[Anonymous user · Accepted solution]

Right, I had to (manually) open port 6547 on the core firewall. When installing the Agent, it asks to add a firewall exception, but it doesn't. Executed this command on the Core Console: netsh advfirewall firewall add rule name="APC Agent 6547" dir=in action=allow protocol=tcp localport=6547 and after that, I can connect to the agent with the web browser.

Simon

[josh3]

I am having the same problem, but this is with Hyper-V Core 2019.  Started, Stopped and restarted the agent; reinstalled the agent; added the manual firewall rule and port 6547 is still not listening.