BE 2014 on Windows 2012 R2 not connecting to CASO on Windows 2008 R2

[Sujith_Mohammed]

Hi All,

We have a new Server installed with Windows 2012 R2. Also, have an existing Backup Exec 2014 environment with CAS running in Windows 2008 R2. When configuring this server as a managed server it fails to connect to the central server saying that it was unable to contact the SQL Server on the cental server. I suspect this is to do with the firewall settings in Windows 2012 R2. Can any one please guide me with what ports/rules etc to be enabled for this communication to happen.

[AmolB]

Could you post the exact error message?

Also check if there are any errors in the Windows Event Viewer.

[Sujith_Mohammed]

Error message is as below . Service account has all required rights.

There is no log in the eventlog

Installation log shows the following error :

07-10-2014,14:21:37 : DRIVER={SQL Server};SERVER=c0919s004\BKUPEXEC;Trusted_Connection=Yes

+ 07-10-2014,14:21:52 : V-225-206: Connection attempt 3 failed: Login timeout expired ***To search for information about this error,

[CraigV]

Hi sujith,

For some reason your query about ports used by Backup Exec wasn't answered, so here are 3 TNs dealing with this:

http://www.symantec.com/business/support/index?page=content&id=TECH49563 (List of ports used by BE)

http://www.symantec.com/business/support/index?page=content&id=TECH43579 (Configuring BE with firewalls)

http://www.symantec.com/business/support/index?page=content&id=HOWTO22990 (Using BE with firewalls)

Thanks!

[VJware]

Can't really see the image, though do ensure remote connections to the SQL instance (specifically TCP/IP and Named Pipes protocols) are enabled.

[Sujith_Mohammed · Accepted solution]

Hello All,

It turned out that the issue was related to Hyper-v network settings for Windows 2012 Hyper-v host and not a Symantec 2014 related issue . Thanks for all the comments and responses.

Regards,

Sujith