Hyper-V Manager blocked by Norton 360

Norton Security | Norton Internet Security
1

I am running Microsoft Hyper-V Manager Windows 7  and Norton 360 5.2.0.13.

 

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

 

 

  • Port 135 is open
  •  There is already an exception for vmconnect.exe

What do I need to do to make this work?

2

Hi Yogesh,

 

Thanks for your reply. I am running Norton 360 V3.5.2.11.  It turns out that most of the ports that you sited as needing to be allowed were already listed in the allowed programs list (apparently automatically when I installed Hyper-V Manager), but were not prioritized properly.  Consequently, a higher priority denial over-road the needed ports.  Once I moved the ports/programs you listed to the top, I could connect from Hyper-V Manager on my Vista PC to my virtual guests on the Hyper-V server.

 

Your mention of WUDPhost.exe must be a typo, the correct name is: WUDFhost.exe, as the program is not on my Vista PC and a search on Microsofts site returns only a reference to a blog showing how OneCare is configured for the same allowed ports.  The reference there must also be a typo.

 

Thanks again for all your help.

 

wfearn

3

I have installed the Microsoft Hyper-V Manager program on my Vista PC running the Norton 360 firewall.  The firewall has added a program exception for virtmgmt.msc which should allow Hyper-V Manager to connect to my Hyper-V server.  The Hyper-V server is on the same network and is in the same workgroup as my Vista PC.  However if I try to connect with the Norton 360 firewall enabled, I get the message "RPC server unavailable. Unable to establish communication between ... [the two systems]." When I disable Norton 360 firewall, Hyper-V Manager connects normally.  My Hyper-V server is otherwise working fine.

 

What other ports should I need to open to get Hyper-V Manager to connect?

4

Hi Thodgson,

 

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.

 

Thanks,

 

HarryP

 

5

Hi Harry,

 

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.

 

Tim

6

Can I try version 6?

7

Sure, please try to upgrade to Version 6 and let me know if the problem persists.

 

Thanks,

HarryP