Articles > Storage
Problem:
Netbackup client (windows server 2012) could not connect to new master server (server 2008 R2)) [Netbackup error 46: server not allowed access]
Diagnostics:
created "bpcd" folder under c:\program files\veritas\netbackup\logs and tried the connection again. a log file was generated and it revealed that the client contacted the correct server and ip address, but that the master server responded from it's secondary IP address. The secondary IP was not on the master server list of the client.
Solution:
Install the patch (*correction, three patches) and set the "skipassource" flag via command line on the secondary IP:
How to set the primary IP address of a Windows server 2008 R2 | aip.im
http://www.aip.im/2013/01/how-to-set-the-primary-ip-address-of-a-windows-server-2008-r2/
KB2386184
KB2551090
KB2554859
Related Articles:
Enterprise Support - Symantec Corp. - Status 59 and/or 46 errors seen during backups
http://www.symantec.com/business/support/index?page=content&id=TECH141842&actp=search&viewlocale=en_US&searchid=1327907620152
STATUS CODE: 46 Connecting to the Windows Remote Administration console fails with connection errors
http://www.symantec.com/business/support/index?page=content&id=TECH19944
(46) Server not allowed access - Netbackup - Tech Tips - News and Entertainment
http://www.alihassanlive.com/e2k3/2012/2/15/46-server-not-allowed-access-netbackup.html
Enterprise Support - Symantec Corp. - NetBackup status code: 46
http://www.symantec.com/business/support/index?page=content&id=HOWTO34932
Netbackup error 46: server not allowed access
Last Updated: 8/8/13Problem:
Netbackup client (windows server 2012) could not connect to new master server (server 2008 R2)) [Netbackup error 46: server not allowed access]
Diagnostics:
created "bpcd" folder under c:\program files\veritas\netbackup\logs and tried the connection again. a log file was generated and it revealed that the client contacted the correct server and ip address, but that the master server responded from it's secondary IP address. The secondary IP was not on the master server list of the client.
Solution:
Install the patch (*correction, three patches) and set the "skipassource" flag via command line on the secondary IP:
How to set the primary IP address of a Windows server 2008 R2 | aip.im
http://www.aip.im/2013/01/how-to-set-the-primary-ip-address-of-a-windows-server-2008-r2/
KB2386184
KB2551090
KB2554859
Related Articles:
Enterprise Support - Symantec Corp. - Status 59 and/or 46 errors seen during backups
http://www.symantec.com/business/support/index?page=content&id=TECH141842&actp=search&viewlocale=en_US&searchid=1327907620152
STATUS CODE: 46 Connecting to the Windows Remote Administration console fails with connection errors
http://www.symantec.com/business/support/index?page=content&id=TECH19944
(46) Server not allowed access - Netbackup - Tech Tips - News and Entertainment
http://www.alihassanlive.com/e2k3/2012/2/15/46-server-not-allowed-access-netbackup.html
Enterprise Support - Symantec Corp. - NetBackup status code: 46
http://www.symantec.com/business/support/index?page=content&id=HOWTO34932
Keywords: Netbackup, 6, 6.5, 7, 7.5, error 46, server, not allowed access, client, windows