02-18-2014 10:35 PM
Host properites are no loading we can ping the server we can rdp the server
**** Edited by Marianne to insert line-breaks ****
Solved! Go to Solution.
02-18-2014 10:40 PM
system: (10061) No connection could be made because the target machine actively refused it. ; FROM 0.0.0.0
does the client is winodws or unix?
if windows does it have antivirus running?
what is the output of
bptestbpcd -client <clientname> -verbose -debug
from the Media server?
enable the bpcd log in the client with Verobse 5 and try the backup again and attach the log.
02-18-2014 10:40 PM
system: (10061) No connection could be made because the target machine actively refused it. ; FROM 0.0.0.0
does the client is winodws or unix?
if windows does it have antivirus running?
what is the output of
bptestbpcd -client <clientname> -verbose -debug
from the Media server?
enable the bpcd log in the client with Verobse 5 and try the backup again and attach the log.
02-18-2014 11:10 PM
Is this a client that has worked before?
Or new client that has never worked?
Please provide all relevant info:
OS version on client.
NBU version and patch level on client.
Have you checked that NBU is up and running on the client?
OS firewall disabled on client?
Company firewall between client and server? Port 1556 open in both directions?
PS:
In future, please start opening post with description of issue, not just Activity Monitor extract.
You may also want to paste the text in Notepad first so that it is properly formatted....
Thanks!
02-19-2014 12:45 AM
Look like the Netbackup client is not running or firewalled off by the Windows firewall.
02-24-2014 12:14 PM
Nicolai has what I se is the solution.
NBU client services need to be running on the client. Use "bpps" on the client to see them.
That would be "bpcd -standalone" and "vnetd -standalone".
That then just leaves the firewall, which for me is almost always the guilty party.
Another possible check of connectivity is (from the client):
bpclntcmd -pn
That should show "Expecting response from <master_server_name>"
followed by what the Master thinks the local client is. That is a good way to tie client to Master and Master to client. If the command has a failure, look at the reported NBU status code with "echo %ERRORLEVEL%" on Windows, and "echo $?" on Unix/Linux.
02-24-2014 09:44 PM
Cannot be too much of an issue - there has been no response from @knarra since 19 Feb.
I have also asked these questions on the same day:
Have you checked that NBU is up and running on the client?
OS firewall disabled on client?Company firewall between client and server? Port 1556 open in both directions?