STATUS CODE 59 is received on all Windows clients after the master server and clients have received new IP addresses.

Problem

STATUS CODE 59 is received on all Windows clients after the master server and clients have received new IP addresses.

Error Message

<2> hosts_equal: gethostbyname failed for : The requested name is valid and was found in the (0)
<16> bpcd valid_server: is not a server
<4> bpcd exit_bpcd: FTL - BPCD EXIT STATUS 46

Solution

Overview:

A Status 59 can occur on all Windows clients after the master server and Windows clients have received new IP addresses, even once the new IP addresses have been assigned properly and appear in DNS.  Windows clients can cache the old host names as well as the new host names.  This will cause a Status 59 when attempting to back up the clients.

Troubleshooting:

Run the following command in a command prompt on one of the Windows clients:
 

% <install_path>\VERITAS\NetBackup\bin\bpclntcmd -hn <Master_name>

This should return the correct hostname information for the master server.

Then run the following command from a shell window on the master server:
 

# /usr/openv/netbackup/bin/bpclntcmd -hn <client_name>

This may return both the old and the new IPs for each of the clients.

Master Server Log Files:

The /usr/openv/netbackup/logs/bpsched/log.<date> file on the master server will show the message:
Exit Status 59: access to client not allowed


Client Log Files:

The <install_path>\VERITAS\NetBackup\logs\bpcd\<date>.LOG file on the client will show the following errors:
<2> hosts_equal: gethostbyname failed for <Master_name>: The requested name is valid and was found in the  (0)
<16> bpcd valid_server: <Master_name> is not a server
<4> bpcd exit_bpcd: FTL - BPCD EXIT STATUS 46

Resolution:

To fix this issue, follow these steps:

1. Check both the hosts and lmhosts files on the client for misspelled, outdated, or decommissioned server names or IP address entries

For Windows 95/98/ME clients,  check the files:
 

C:\WINDOWS\hosts
C:\WINDOWS\lmhosts
For Windows NT, 2000, XP, 2003 clients,  check the files:

%SystemRoot%\system32\drivers\etc\hosts
%SystemRoot%\system32\drivers\etc\lmhosts
      
2. Purge the host names in the client cache after making any hosts or lmhosts file changes

Bring up a command prompt and issue the following command to clear any cached hosts file changes:

% ipconfig /flushdns
"Successfully flushed the DNS Resolver Cache"
Bring up a command prompt and issue the following command to clear any lmhosts file changes:

% nbtstat -R
"Successful purge and preload of the NBT Remote Cache Name Table."

3. Verify name resolution and IP resolution with article  https://www.veritas.com/docs/000026124