07-27-2014 07:32 PM
Solved! Go to Solution.
07-27-2014 08:04 PM
Is the client behind a firewall or DMZ?
Or perhaps OS hardening done on the client?
Can you see bpcd and vnetd entries on the client in /etc/inetd.conf and /etc/services?
Can you see bpcd and vnetd 'LISTENING' in 'netstat -a' output?
PS:
NBU 6.5 ran out of support almost 2 years ago.
In NBU 7.x, the above processes run as standalone processes and no longer part of inetd.
Time to upgrade!
07-27-2014 08:04 PM
Is the client behind a firewall or DMZ?
Or perhaps OS hardening done on the client?
Can you see bpcd and vnetd entries on the client in /etc/inetd.conf and /etc/services?
Can you see bpcd and vnetd 'LISTENING' in 'netstat -a' output?
PS:
NBU 6.5 ran out of support almost 2 years ago.
In NBU 7.x, the above processes run as standalone processes and no longer part of inetd.
Time to upgrade!
07-29-2014 12:36 AM
In addition to suggestions of Marianne, also check the forward and reverse name resolution with bpclntcmd comamnd as follows.
bpclntcmd -ip client_ip
bpclntcmd -hn client_name_mentioned_policy
Is this new client added to backup ?
07-29-2014 02:40 AM