PowerChute cannot communicate with the Management Card (windows 2008 x64)

[Anonymous user]

Hello,

we just bought APC UPS Smart-ups 3000 rx and management card ap9617

i connected my server with windows server 2008 x64 and when i try to shut it down with PowerChute
I ran into some dificoulties.

Powerchute on client says:
PowerChute cannot communicate with the Management Card

I disabled firewall and second network card, but it's still not comunicating.

I installed 32 bit version of pcns.
64 bit version is only for itanium (I asume) and it won't compile (it says exception in thread "main" ...)

i hope anyone has any idea

Boris Koscak

[Techie_apc]

PowerChute Network Shutdown utilizes the following TCP/IP ports: tcp/udp 3052 and tcp/udp 80. Versions 2.2.3 utilizes port 6547 for instance 1, 6548 for instance 2, and 6549 for instance 3. Please make sure that these ports are not blocked while installing the software. Click on the below link to view the Power Chute Network Shutdown compatibility chart:
http://www.apcmedia.com/salestools/SJHN-7AYQNP_R11_EN.pdf

I hope that this helps to determine if you have the right PCNS software.

Secondly, The default administrator authentication phrase used by PowerChute Network Shutdown is: admin user phrase
The Authentication Phrase must be at least 15, but no more than 32 characters.
If you change the Authentication Phrase, you must also change it on the Web Management Card. Otherwise, PowerChute Network Shutdown and the Web Management Card will not be able to communicate.

[BillP]

also, you said you disabled the firewall on server 2008, correct? rather than trying to open ports through it? i have seen issues specifically with server 2008 where disabling the firewall and turning it completely off needed to be done. also, make sure you dont have a group policy that forces it to run in the background even if you turn it off.

other things ill throw out there:

-NIC binding order - PCNS binds to the first network card
-Subnet mask - we have seen a card be reachable yet the subnet be incorrect and cause this issue

also, PCNS communicates with the NMC on whatever HTTP port you have set in the NMC, even if you are using HTTPS as the access method to it, so if that has changed from the default of 80, make sure that port is open.

lastly, you could always try directly connecting the NMC to the computer if possible to rule out a network issue.

[Anonymous user · Accepted solution]

And I have identical problem on Windows XP.

ap9617 detects my computers and adds Ip in PowerChute Clients menu.