GENERAL ERROR: Windows Remote Administration console fails to connect, with the error "<host> does not have BPRD operating. (Error 25)"

Article:TECH29783  |  Created: 2003-01-24  |  Updated: 2013-10-24  |  Article URL http://www.symantec.com/docs/TECH29783
Article Type
Technical Solution

Product(s)

Environment

Issue



GENERAL ERROR: Windows Remote Administration console fails to connect, with the error " does not have BPRD operating. (Error 25)"

Error



The selected host "host.domain.com" does not have BPRD operating. (Error 25) Make sure all the services are running on the host.

Solution



Overview:
The following errors can occur when the Windows Client cannot connect to the bprd port on the master server:
The <host> does not have BPRD operating. (Error 25)
The selected host <host> does not have the service BPRD operating. (Error 25).  Make sure all the services are running on the host.

Troubleshooting:
To verify there is a network connection to the bprd port on the master server, from the client run the following command:
# telnet <master_server_hostname> 13720

This should connect and display a blank screen. To return to the prompt press <Ctrl + ]> and type quit at the telnet prompt.

If the connection is refused or cannot be established, this indicates bprd is not running on the master or a network problem or firewall configuration is preventing access to the bprd port on the master server.


Resolution:
1. To verify that bprd is running, use the bpps command

On the master run the command:
# /usr/openv/netbackup/bin/bpps -a

This should return:
root <pid> 1  0 <time> ? 0:01 /usr/openv/netbackup/bin/bprd

If bprd is not running, then restart the NetBackup (tm) processes.
# /usr/openv/netbackup/bin/goodies/netbackup stop
# /usr/openv/netbackup/bin/goodies/netbackup start

If bprd starts up, then try to connect with the Windows Remote Administration console again.

2. Verify that bprd is listed in /etc/services. This is required for bprd to start.  

On the master, run the command:
# grep bprd /etc/services

This should return:
bprd    13720/tcp       bprd

If not, then check to make sure that the NetBackup daemons are listed in /etc/services. Otherwise, add this entry to the /etc/services file and then try to connect with the Windows Remote Administration console again.

3. Verify that bprd is listening in netstat. This is required in order for the bprd daemon to accept incoming connections.

On the master, run the command:
# netstat -a |grep bprd

This should return:
  *.bprd       *.*       0      0 49152      0 LISTEN

If not, then restart the NetBackup processes
# /usr/openv/netbackup/bin/goodies/netbackup stop
# /usr/openv/netbackup/bin/goodies/netbackup start

Then try to connect with the Windows Remote Administration console again.

4. To verify there is a network connection to the bprd port on the master server, from the client run the following command:
# telnet <master_server_hostname> 13720

This should connect and display a blank screen. To return to the prompt press <Ctrl + ]> and type quit at the telnet prompt.

If the connection is refused or cannot be established and bprd is running and in LISTEN status on the master, then there is most likely a network problem or firewall configuration preventing access to the bprd port on the master server.

5. Verify that the server has not run out of system ports
#  netstat -a | grep TIME_WAIT | wc -l

If there is a value above 50, check and reduce the system tcp_time_wait_interval per Technote 230050 below

Supplemental Materials

SourceError Code
Value25
DescriptionNetBackup Error 25: cannot connect on socket


Legacy ID



264880


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


Terms of use for this information are found in Legal Notices