01-23-2013 08:19 AM
Hi All,
In SSR 2013 Monitor, I am unable to connect to Windows 7 clients running SSR 2013 (or SSR 2011). XP is fine and both have the same firewall policy in SEP 12.1.2.
When trying to connect to a Win7 Console I am given the following possibilities for not connecting (I suspect the last option): Any advice?
I will disable UAC on one system to test connection - but this wouldn't be desireable!
Possible Causes:
1)Computer is not connected to the network.
2)Firewall of the target computer is ON.
3)Supported Backup Exec System Recovery or Symantec System Recovery client is not installed on the target computer.
4)User credentials are incorrect.
5)UAC (User Access Control) security policy is enabled on the computer.
Solved! Go to Solution.
01-24-2013 12:40 AM
01-23-2013 11:51 PM
01-24-2013 12:40 AM
01-24-2013 08:13 AM
Well I did the test on one Windows 7 client to disable UAC and that allowed communication from the 2013 Monitor (Restoring the defaul UAC setting disabled communication again).
I have the Symantec Protection Suite Small Business Ed. v4.0 bundled product so I also use SEP 12.1.2 for managing the client firewalls (on both XP and 7 - which is the same policy).
XP clients communicate fine, Win 7 clients with UAC enabled don't.
Do you think there's a way to trust the remote monitor process and work "with" UAC enabled?
01-25-2013 11:54 AM
OK, I spoke too soon...
Disabling UAC allowed me to use SSR 2013 Monitor to communicate with my own workstation (SSR 2013 and SSR Monitor installed on the same Windows 7 System). With UAC set to default, I couldn't even communicate with myself through the SSR 2013 Monitor.
I still cannot communicate with networked SSR 2013 Win7 clients in SSR Monitor 2013 even if all firewalls are disabled and UAC is also disabled.
Now I need to confirm that the agent is properly installed.
So in summary:
With my workstation firewalled and UAC enabled, I can communicate with XP32/64 clients with SSR 2011 or SSR 2013 installed. These clients are configured with the "default" Symantec Firewall policy through SEPM.
From my Win7 workstation, I cannot use SSR 2013 Monitor to communicate with Win 7 clients (2011 or 2013) regardless whether firewall and or UAC is on or off.
01-25-2013 04:16 PM
01-28-2013 03:44 PM
Thanks to everyone's help I've been able to pinpoint my problem.
It was indeed Firewall related and requires enabling a firewall allow rule for "Vprosvc.exe".
Since I use Symantec Endpoint Protection Small Business for firewall configuration, I was unable to configure a new "program" allow rule in order to allow unblocked communication to "Vprosvc.exe" remotely.
I temporarily disabled SEP, then looked at the Windows Firewall and temporarily turned it off too to test.
I was then able to communicate with the client in the 2013 Monitor program!
I added the "Vprosvc.exe" allow rule in Windows Firewall then turned it on again.
Monitor communication was still good!
After re-enabling SEP too, I was pleased to see that I can still communicate to the client using the Monitor program.
My next task is to see how to modify the SEP Firewall Policy to enable this communication without having to take it down and add the exception to Windows Firewall.
Can you add "Program" rules to the SEP firewall policy? I'm not able to find it, just "port" defined rules.
Thanks for all input!
01-28-2013 09:54 PM
Lucky you - please mark this post as solved !