2 HyperV windows servers won't communicate with NMC while all the others do...

[Anonymous user]

Hi,

I've just installed a new ups (Smart-UPS X 3000 with network card) and have installed the Powerchute network shutdown successfully onto 7 servers, 5 physical servers including a hyper-v server 2008 box and 2 hyper-v virtual machine on this physical box. There are 2 other virtual machines (an exchange 2010 server and fileserver both running on server 2008 r2 enterprise) but for some reason they don't communicate correctly. I've added firewall rules for udp port 3052 and 6547 and can browse to the ups ip from the server successfully and I'm out of ideas as to why these two would not work when all the others are fine.

The strange thing is that they get added to the ups but in group 1 when all the rest are in group 2.... Any ideas?

[BillP · Accepted solution]

First thing I know I'd do compare the subnet mask on everything - is there anything specific to these two devices? While the NMC can communicate to PowerChute clients over different subnets, perhaps one of the TCP/IP settings is incorrect.

Also, we can run through this (which I know you checked some of it)-> Communication lost with PowerChute Network Shutdown Flowchart. | FAQs | Schneider Electric US

The flowchart for your situation refers to article ID 7711 which is an old ID and the new link for that is here -> Communication lost with Powerchute Network Shutdown | FAQs | Schneider Electric US

And for some references to application notes, those are referenced here -> http://www.apc.com/prod_docs/results.cfm?DocType=App%20Note&Query_Type=163