08-12-2012 11:23 AM
I am running Microsoft Hyper-V Manager Windows 7 and Norton 360 220.127.116.11.
When trying to connect in Hyper-V Manager, I receive the error message: "RPC server unavailable. Unable to establish communication between ... [the two systems]." When I disable Norton 360 firewall, Hyper-V Manager connects and functions normally.
I saw another post where this issue was resolved on a system with Windows Vista and Norton 360 v3; however, it does not work for my newer versions.
Here is the resolution that DOES NOT WORK:
You may have to open Port 135 for RPC, and change the access for the following executable files in the Program Rules to Allow all communications:
C:\Windows\System32\wbem\unsecapp.exe C:\Windows\System32\WUDPhost.exe C:\Program Files\hyper-v\vmconnect.exe
What do I need to do to make this work?
08-12-2012 01:06 PM - edited 08-12-2012 01:07 PM
Welcome to Norton Community Forums!!
Did you create a new firewall rule to open Port 135 for RPC?
Did you move the firewall rule(traffic rule) to open Port 135 to the top of the list of rules for priority?
Did you try removing the unsecapp.exe, WUDPhost.exe & vmconnect.exe from Program Rules and then manually add it back?
If you are using Norton 360 Version 5.2, you can very well upgrade your Norton 360 for free of cost to the latest version - Norton 360 Version 6.0.
08-13-2012 12:13 PM
I have a firewall rule for port 135 open to any computer inbound and outbound. This rule is at the top of the list.
The programs unsecapp.exe and WUDPhost.exe exist in C:\Windows\system32\wbem and c:\windows\system32 respectively; however, when I try to add them to the Program Rules, Norton complains that it cannot find them.
VMconnect.exe was removed and added to no effect.