STATUS CODE: 46 Connecting to the Windows Remote Administration console fails with connection errors

Article:TECH19944  |  Created: 2002-01-03  |  Updated: 2013-04-25  |  Article URL http://www.symantec.com/docs/TECH19944
Article Type
Technical Solution

Product(s)

Environment

Issue



STATUS CODE: 46 Connecting to the Windows Remote Administration console fails with connection errors


Error



server not allowed access(46)


Solution



Overview:  
The Windows Remote Administration Console can fail with the error "Unable to connect to the selected NetBackup host <hostanme>"  (Figure 1).  In older Veritas NetBackup (tm) versions,  this error can appear as "Neither the selected host <hostname> has NetBackup operating nor the current user <user name> or host have NetBackup administrative privileges on the host <hostname>."  This error will appear as a Status 46 in the bpcd log on the client.  This error indicates the server is trying to access a client but access is blocked.  This can occur when the client does not recognize the master as a valid server.  This can also occur when the name resolution is failing to properly resolve reverse name lookups.

Figure 1
 

Troubleshooting:
The following situations could cause a Status 46 when connecting.  The bpcd log on the client will show the cause for the Status 46.
1. The server is a valid server,  but is not listed in the configuration (UNIX bp.conf or Windows registry) on the client
2. Name resolution is failing to resolve reverse name lookups

Log Files:
The /usr/openv/netbackup/logs/bpcd/log.<date> will show the following when the server is not listed in the configuration on the client or name resolution is returning the wrong host name or IP address:
<2> bpcd valid_server: comparing master_server_name and name_of_admin_server
<16> bpcd valid_server: name_of_admin_server is not a server
<16> bpcd valid_server: name_of_admin_server is not a media server
<2> bpcd main: <---- NetBackup 6.5 0 ------------initiated
<2> bpcd exit_bpcd: exit status 46  ----------->exiting
<4> bpcd exit_bpcd: FTL - BPCD EXIT STATUS 46
<16> bpcd main: Server access denied

The /usr/openv/netbackup/logs/bpcd/log.<date> file will show the following errors when there is a problem with name resolution:
<2> bpcd main: setup_sockopts complete
<8> bpcd peer_hostname: gethostbyaddr failed : HOST_NOT_FOUND (1)
<16> bpcd peer_hostname: gethostbyaddr failed to return peer host, herrno = 1
<16> bpcd main: Couldn't get peer hostname

Resolution:  
There are different resolutions to this issue which depend on the type of log entries that appear in the bpcd log file.  The following sections outline how to handle the above log file examples depending on the symptoms being seen.

When the bpcd log on the client shows "Server access denied",  then verify the server name has been added to the configuration on the client.
 
- On Windows clients, add the server on the Servers tab in the Specify NetBackup Machines and Policy Type dialog box. To display this dialog box, start the Backup, Archive, and Restore interface on the client and click Specify NetBackup Machines and Policy Type on the File menu
 
- On UNIX and Macintosh clients, add a SERVER entry in the bp.conf file
 
- On NetWare target and OS/2 clients, add a SERVER entry in the bp.ini file
 

When the bpcd log on the client shows "Server access denied" and the server name has been added properly to the configuration on the client,  then verify that name resolution is returning the correct host name and IP address.  
 
The bpcd log on the client will show entries such as "comparing master_server_name and name_of_admin_server".  Ensure the "name_of_admin_server" displayed is the host name that is expected.  If the hosts file, a DNS server,  or an NIS server is configured incorrectly,  it will cause the wrong host name to be compared to the client's configuration.  Until the incorrect name resolution setting can be found and corrected use the steps in the next section to add a hosts file entry for the systems
 

When the bpcd log on the client shows "gethostbyaddr failed" errors try the following:
 
Ensure the name resolution can return correct reverse name lookup information for the master and client.  If this has already been done,  then try adding a hosts alias for the server on the client
 
- For UNIX systems, change the /etc/nsswitch.conf file on both the master and client to resolve host names by "files" first.  Then add the host name and IP entries for the master and client in their respective /etc/hosts files
 
- For Windows systems, add host name and IP entries for the master and client in their respective %System Root%\System 32\drivers\etc\hosts files
 

 

 

Supplemental Materials

Value46
Description

NetBackup Error 46: server not allowed access



Legacy ID



247114


Article URL http://www.symantec.com/docs/TECH19944


Terms of use for this information are found in Legal Notices