Unable to push NetBackup client

What happens when you telnet from the client to the Master the following ports (may need to install telnet client first):
telnet master.fqdn 1556
telnet master.fqdn 13724

If successful, then the console should turn blank. If they return with connection error/fail, then you will need to troubleshoot that before attempting to install the NetBackup client.

Speaking of ports, I recall a very strange issue with Windows server firewall in the past. It was completely switched off (as in your case). The Domain Profile, Private Profile and Public Profile, all three of them off.
But still, some ports were blocked.
We manually added some Inbound/Outbound Rules to explicitly open the ports and the whole thing started working, strangely. The firewall on/off switch seemed to have gone busted.

If the above telnet test failed, then just for a test, on the client try adding the following ports in both Inbound and Outbound Rules list for both TCP and UDP, for all three Profiles:
111,1556,2049,2821,4032,7394,10082,10102,13701,13702,13705,13711,13713,
13716,13717,13720,13721,13722,13723,13724,13782,13783,13785
Inside a rule, on the "Protocals and Ports" tab, use the "Specific Ports" drop down for both local and remote, then just copy and paste that whole list of ports (You don't really need them all, but when all else fails, use a shotgun.)
 

Hi RLeon,

Thanks for your reply and your time. I got the issue resolved a bit ago and you were right on track. The issue was with the corporate firewall though, not the local Windows one.

When the network engineer opened up the ports for me he did it manually rather than using the already existing NetBackup template used in other subnets. Turns out he missed 3 ports. Thats why I could push the install files and actually run them but when the client tried to communicate back to the master server it failed. Once he corrected this all worked like a charm.

Thanks again to all who assisted.