Installing Netbackup Client 6.5.5 on Windows 2008 R2 server

I am attempting to install Netbackup 6.5 and then 6.5.5 on a Windows 2008 R2 server for the first time.  I've done this with Windows 2003 many times before.  
This time, during the install of Netbackup client, I get the error message "cannot communicate with the master server....  Do you wish to proceed"
I have the master server listed in the windows server's host file because it is not in the windows domain.  I can ping the master server from the windows server.  (My master server is a Solairs 9 server.
The firewall on the windows server is the only firewall between the two servers.  I've added the 2 required ports for Netbackup for both inbound and out bound traffic.
This was my first install and use of Windows 2008.
Jack SeamanAsked:
Who is Participating?
 
Jack SeamanAuthor Commented:
Found the issue.  I had the wrong IP address for the master server in the Windows 2008 R2 host file.  Once that was corrected, I was able to connect thru to the master server.
So,  when installing NB Client 6.5.5 on a Windows 2008 R2 server, you must:

1.  Install NB6.5.4 Clilent 64bit
2.  Install NB6.5.5 Client 64 bit.
3.  Open NB ports on client thru firewall
0
 
Justin DurrantSr. Engineer - Windows Server/VirtualizationCommented:
Did you try turning the firewall off completely?
0
 
Jack SeamanAuthor Commented:
Yes, I tried that.  We are using Symantec Endpoint Protection on the server.  So we must controll the windows firewall settings thru SEP.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Justin DurrantSr. Engineer - Windows Server/VirtualizationCommented:
Right.. try disabling the SEP services?
0
 
Jack SeamanAuthor Commented:
Disabled SEP services.  Tried to install NB, same results:  Unable to communicate with master server
0
 
Justin DurrantSr. Engineer - Windows Server/VirtualizationCommented:
Is there in error code.. like -42
0
 
Jack SeamanAuthor Commented:
The error occurs in the actual install of NB 6.5.  It says in a pop up window:
Could not communicate properly with the master server.
Backups may not properly function.
Proceed anyway?

There are the yes or no buttons.

I tried to continue once, and it installed but I could not install the NB 6.5.5 patch.  

When only the NB 6.5 client was on the server, I tried to add it to a NB policy to test communications and go a 25 connot connect on socket error.
0
 
Justin DurrantSr. Engineer - Windows Server/VirtualizationCommented:
Hmm.. ok. Should work, we have 2008 R2 clients working with 6.5.5.
0
 
Jack SeamanAuthor Commented:
Is your master server in the same domain or trusted domain as your 2008 R2 clients?  In my case, my master server is a SUN box and it is not in the domain of the 2008 R2 clients.  However, I've had no issues with our 2003 server clients with the master server not in the domain.  Could it be a new "security feature" for 2008 R2 that prevents communication?
0
 
Justin DurrantSr. Engineer - Windows Server/VirtualizationCommented:
Our master server is Unix.. we have the firewall off on all 2008 servers.. we also run SEP but only the AV portion not firewall.
0
 
Jack SeamanAuthor Commented:
Is your master server in the same domain as your 2008 servers?
0
 
Justin DurrantSr. Engineer - Windows Server/VirtualizationCommented:
Yes it is
0
 
Jack SeamanAuthor Commented:
I think the issue is making the 2008 R2 server talk to the master server that is not in the domain.  Beyond putting the master server in the host file of the 2008 R2 server, I don't know what else to do.
0
 
Justin DurrantSr. Engineer - Windows Server/VirtualizationCommented:
Yeah.. I actually took my master server out of the domain in my lab and I could no longer communicate.
0
 
Jack SeamanAuthor Commented:
Something with 2008R2 prevents communication with non-trusted nodes (i.e., outside domain or trusted domain).
So I guess the question refined is "What prevents Windows 2008 R2 communication with non-trusted nodes?  Simply added the master server's IP address to the hosts file does not works like with a Windows 2003 server.
0
 
Justin DurrantSr. Engineer - Windows Server/VirtualizationCommented:
Yeah, I am not sure what though.. can you add the master server to the domain and test?
0
 
Jack SeamanAuthor Commented:
Not a chance.  We are a very "stove piped" organization.  I would never be allowed to add a Unix server to a windows domain.
0
 
Justin DurrantSr. Engineer - Windows Server/VirtualizationCommented:
I understand. Not sure what else to recommend.. have you talked to Symantec?
0
 
Jack SeamanAuthor Commented:
Called support.  Was told that 2008 R2 was not supported by NB6.5.  Needed to install NB6.5.4 then NB6.5.5.  Just got through trying to install 6.5.4 and it failed as before.  Will be contacting support again.
0
 
Justin DurrantSr. Engineer - Windows Server/VirtualizationCommented:
Right.. your title says you are on 6.5.5
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.