Please tell us exact NBU version on server and on client.

Which ports did you telnet on?

NBU needs forward and reverse name lookup between master and client as well as between media server and client, as well bi-directional port connectivity. NBU 6.0 - 7.0 will use vnetd (13724). NBU 7.0.1 and later will first try BPX (1556), if that fails, will try vnetd.
Correct SERVER entries on client is also needed. The client needs to resolve server's incoming IP address to hostname that appears in SERVER list.

To troubleshoot, do the following:

Create bpcd log folder on client (under ...\netbackup\logs).

Run the following from cmd on master and media server(s):
bptestbpcd -client <client-name> -debug -verbose

Check output of command as well as bpcd log for errors.

NetBackup can work without Active Directory.
To verify your configuration, please post output of following commands on both hosts.

bpclntcmd -self
bpclntcmd -pv
bpclntcmd -hn master_server_name
bpclntcmd -hn media_server_name
bpclntcmd -hn client_name
bpclntcmd -ip maser_server_IP
bpclntcmd -ip media_server_IP
bpclntcmd -ip client_IP
reg query HKLM\Software\Veritas\NetBackup\CurrentVersion\Config /v Server
reg query HKLM\Software\Veritas\NetBackup\CurrentVersion\Config /v Client_Name

thanks alot it work with me when i make entry for ip address and host name in host file for both client and server

but there is a user with it select to buckup it give me massage : cannot connect on socket

the massage also appeare when i press configure client and put host name or ip address

i am already disable firewall in both side

Apologies - I battle to understand the following:

but there is a user with it select to buckup it give me massage : cannot connect on socket

the massage also appeare when i press configure client and put host name or ip address

Please take screenshots and post as File attachments?

This shows the client to be the same server as the Master Server and that it cannot connect to itself!

Have you put the clients IP address against the Master servers name in the hosts file?

Make sure you have everything correct and then run this on the Master and client and then try again:

\program files\veritas\netbackup\bin\bpclntcmd -clear_host_cache

Let us know how it goes

Please show us output of ALL commands in Yasuhisa's post above.

Run all of the commands on the server and the client.

You never told us which ports you tried to telnet on?
Also no output from bptestbpcd command?

the port i telnet on is 13782 and 13720

and the output is:

c:\Program Files\Veritas\NetBackup\bin\admincmd>bptestbpcd -client eslam-pc -deb
ug -verbose
08:37:56.767 [5596.3476] <2> bptestbpcd: VERBOSE = 0
08:37:56.767 [5596.3476] <8> file_to_cache_item: [vnet_addrinfo.c:6555] fopen()
failed ERRNO=2 FILE=C:\Program Files\Veritas\NetBackup\var\host_cache\0c1\77fa94
c1+0,1,a,0,1,0+eslam-pc.txt
08:37:56.782 [5596.3476] <8> file_to_cache_item: [vnet_addrinfo.c:6555] fopen()
failed ERRNO=2 FILE=C:\Program Files\Veritas\NetBackup\var\host_cache\0c1\77fa94
c1+veritas_pbx,1,400,2,1,0+eslam-pc.txt
08:37:56.798 [5596.3476] <8> file_to_cache_item: [vnet_addrinfo.c:6555] fopen()
failed ERRNO=2 FILE=C:\Program Files\Veritas\NetBackup\var\host_cache\0c1\77fa94
c1+vnetd,1,400,2,1,0+eslam-pc.txt
08:37:56.798 [5596.3476] <8> file_to_cache_item: [vnet_addrinfo.c:6555] fopen()
failed ERRNO=2 FILE=C:\Program Files\Veritas\NetBackup\var\host_cache\0c1\77fa94
c1+bpcd,1,400,2,1,0+eslam-pc.txt
08:37:56.814 [5596.3476] <2> vnet_pbxConnect: pbxConnectEx Succeeded
08:37:56.829 [5596.3476] <2> logconnections: BPCD CONNECT FROM 192.168.2.7.51770
 TO 192.168.2.173.1556 fd = 436
08:37:56.829 [5596.3476] <2> vnet_pbxConnect: pbxConnectEx Succeeded
08:37:56.892 [5596.3476] <8> vnet_pop_byte: [vnet.c:1168] errno 10054 0x2746
08:37:56.892 [5596.3476] <2> vnet_pop_byte: vnet.c.1170: 0: Function failed: 43
0x0000002b
08:37:56.892 [5596.3476] <2> vnet_pop_string: vnet.c.1250: 0: Function failed: 4
3 0x0000002b
08:37:56.892 [5596.3476] <2> vnet_pop_signed: vnet.c.1293: 0: Function failed: 4
3 0x0000002b
08:37:56.907 [5596.3476] <2> vnet_version_connect: vnet_vnetd.c.1664: 0: Functio
n failed: 43 0x0000002b
08:37:56.907 [5596.3476] <8> do_pbx_service: [vnet_connect.c:2088] vnet_version_
connect failed 43 0x2b
08:37:56.907 [5596.3476] <8> async_connect: [vnet_connect.c:1630] do_service fai
led 43 0x2b
08:37:56.938 [5596.3476] <8> vnet_pop_byte: [vnet.c:1168] errno 10054 0x2746
08:37:56.938 [5596.3476] <2> vnet_pop_byte: vnet.c.1170: 0: Function failed: 43
0x0000002b
08:37:56.938 [5596.3476] <2> vnet_pop_string: vnet.c.1250: 0: Function failed: 4
3 0x0000002b
08:37:56.954 [5596.3476] <2> vnet_pop_signed: vnet.c.1293: 0: Function failed: 4
3 0x0000002b
08:37:56.954 [5596.3476] <2> vnet_version_connect: vnet_vnetd.c.1664: 0: Functio
n failed: 43 0x0000002b
08:37:56.954 [5596.3476] <8> do_vnetd_service: [vnet_connect.c:1905] vnet_versio
n_connect failed 43 0x2b
08:37:56.954 [5596.3476] <8> async_connect: [vnet_connect.c:1630] do_service fai
led 43 0x2b
08:37:56.954 [5596.3476] <16> connect_to_service: connect failed STATUS (18) CON
NECT_FAILED
        status: FAILED, (43) CONNECT_RESET; system: (10036) A blocking operation
 is currently executing. ; FROM 0.0.0.0 TO 192.168.2.173 192.168.2.173 vnetd VIA
 pbx
        status: FAILED, (43) CONNECT_RESET; system: (10036) A blocking operation
 is currently executing. ; FROM 0.0.0.0 TO 192.168.2.173 192.168.2.173 vnetd VIA
 vnetd
08:37:56.970 [5596.3476] <8> vnet_connect_to_vnetd_ipi: [vnet_connect.c:258] con
nect_to_service() failed 18 0x12
08:37:56.970 [5596.3476] <16> bpcr_vnetd_connect_forward_socket_begin: vnet_conn
ect_to_vnetd_ipi(192.168.2.173) failed: 18
08:37:56.970 [5596.3476] <2> local_bpcr_connect: bpcr_vnetd_connect_forward_sock
et_begin failed: 25
08:37:56.985 [5596.3476] <2> ConnectToBPCD: bpcd_connect_and_verify(eslam-pc, es
lam-pc) failed: 25
<16>bptestbpcd main: Function ConnectToBPCD(eslam-pc) failed: 25
08:37:56.985 [5596.3476] <16> bptestbpcd main: Function ConnectToBPCD(eslam-pc)
failed: 25
<2>bptestbpcd: cannot connect on socket
08:37:56.985 [5596.3476] <2> bptestbpcd: cannot connect on socket
<2>bptestbpcd: EXIT status = 25
08:37:57.001 [5596.3476] <2> bptestbpcd: EXIT status = 25
cannot connect on socket

As Marianne wrote, you have to open port 1556 and 13724.

On which host 192.168.2.7 is UP?
Please post output of other commands. And in addition, run this command.

reg query HKLM\Software\Veritas\NetBackup\CurrentVersion\Config /S

thanks for help

the master and media server are the same server

server 192.168.2.7 output:

c:\Program Files\Veritas\NetBackup\bin>bpclntcmd -self
gethostname() returned: backup.symatec.local
host backup.symatec.local: backup.symatec.local at ::1
host backup.symatec.local: backup.symatec.local at 192.168.2.7
aliases:     backup.symatec.local     ::1     192.168.2.7
getfqdn(backup.symatec.local) returned: backup.symatec.local

c:\Program Files\Veritas\NetBackup\bin>bpclntcmd -pn
expecting response from server backup.symatec.local
backup.symatec.local backup.symatec.local 192.168.2.7 58783

c:\Program Files\Veritas\NetBackup\bin>bpclntcmd -hn backup.symatec.local
host backup.symatec.local: backup.symatec.local at ::1
host backup.symatec.local: backup.symatec.local at 192.168.2.7
aliases:     backup.symatec.local     ::1     192.168.2.7

c:\Program Files\Veritas\NetBackup\bin>bpclntcmd -hn eslam-pc
host eslam-pc: ESLAM-PC at 192.168.2.150
aliases:     ESLAM-PC     192.168.2.150

c:\Program Files\Veritas\NetBackup\bin>bpclntcmd -ip 192.168.2.7
host 192.168.2.7: backup.symatec.local at ::1
host 192.168.2.7: backup.symatec.local at 192.168.2.7
aliases:     backup.symatec.local     ::1     192.168.2.7

c:\Program Files\Veritas\NetBackup\bin>bpclntcmd -ip 192.168.2.150
host 192.168.2.150: ESLAM-PC at 192.168.2.150
aliases:     ESLAM-PC     192.168.2.150

c:\Program Files\Veritas\NetBackup\bin>reg query HKLM\Software\Veritas\NetBackup
\CurrentVersion\Config /v Server

HKEY_LOCAL_MACHINE\Software\Veritas\NetBackup\CurrentVersion\Config
    Server    REG_MULTI_SZ    backup.symatec.local

c:\Program Files\Veritas\NetBackup\bin>reg query HKLM\Software\Veritas\NetBackup
\CurrentVersion\Config /S

HKEY_LOCAL_MACHINE\Software\Veritas\NetBackup\CurrentVersion\Config
    CONNECT_OPTIONS    REG_SZ    localhost 1 0 2
    Port_BPCD    REG_DWORD    0x35d6
    VXDBMS_NB_CONF    REG_SZ    C:\Program Files\Veritas\NetbackupDB\conf
    Port_BPRD    REG_DWORD    0x3598
    Browser    REG_SZ    backup.symatec.local
    Client_Name    REG_SZ    backup.symatec.local
    Exclude    REG_MULTI_SZ    C:\Program Files\Veritas\NetBackup\bin\*.lock\0C:
\Program Files\Veritas\NetBackup\bin\bprd.d\*.lock\0C:\Program Files\Veritas\Net
Backup\bin\bpsched.d\*.lock\0C:\Program Files\Veritas\Volmgr\misc\*\0C:\Program
Files\Veritas\NetBackupDB\data\*
    Server    REG_MULTI_SZ    backup.symatec.local
    EMMSERVER    REG_SZ    backup.symatec.local
    EMMPORT    REG_DWORD    0x614
    TELEMETRY_UPLOAD    REG_SZ    NO
    USE_VXSS    REG_SZ    PROHIBITED
    LIST_FS_IMAGE_HEADERS    REG_SZ    NO

HKEY_LOCAL_MACHINE\Software\Veritas\NetBackup\CurrentVersion\Config\NTIO
    UseNTIO    REG_DWORD    0x0

client 192.168.2.150 output:

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -self
gethostname() returned: eslam-pc
host eslam-pc: eslam-pc at 192.168.2.150
aliases:     eslam-pc     192.168.2.150
getfqdn(eslam-pc) returned: eslam-pc.symatec.local

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -pn
expecting response from server backup.symatec.local
ESLAM-PC *NULL* 192.168.2.150 49284

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -hn backup.symatec.local
host backup.symatec.local: backup.symatec.local at 192.168.2.7
aliases:     backup.symatec.local     192.168.2.7

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -hn eslam-pc
host eslam-pc: eslam-pc at 192.168.2.150
aliases:     eslam-pc     192.168.2.150

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -ip 192.168.2.7
host 192.168.2.7: backup.symatec.local at 192.168.2.7
aliases:     backup.symatec.local     192.168.2.7

C:\Program Files\Veritas\NetBackup\bin>bpclntcmd -ip 192.168.2.150
host 192.168.2.150: ESLAM-PC at 192.168.2.150
aliases:     ESLAM-PC     192.168.2.150

C:\Program Files\Veritas\NetBackup\bin>reg query HKLM\Software\Veritas\NetBackup
\CurrentVersion\Config /v Client_Name

HKEY_LOCAL_MACHINE\Software\Veritas\NetBackup\CurrentVersion\Config
    Client_Name    REG_SZ    eslam-pc

C:\Program Files\Veritas\NetBackup\bin>reg query HKLM\Software\Veritas\NetBackup
\CurrentVersion\Config /S

HKEY_LOCAL_MACHINE\Software\Veritas\NetBackup\CurrentVersion\Config
    CONNECT_OPTIONS    REG_SZ    localhost 1 0 2
    Port_BPCD    REG_DWORD    0x35d6
    Port_BPRD    REG_DWORD    0x3598
    Browser    REG_SZ    eslam-pc
    Client_Name    REG_SZ    eslam-pc
    Exclude    REG_MULTI_SZ    C:\Program Files\Veritas\NetBackup\bin\*.lock\0C:
\Program Files\Veritas\NetBackup\bin\bprd.d\*.lock\0C:\Program Files\Veritas\Net
Backup\bin\bpsched.d\*.lock\0C:\Program Files\Veritas\NetBackupDB\data\*\0C:\Pro
gram Files\Veritas\Volmgr\misc\*
    Server    REG_MULTI_SZ    backup.symatec.local
    BPBACKUP_POLICY    REG_SZ    any
    BPBACKUP_SCHED    REG_SZ    any
    BPARCHIVE_POLICY    REG_SZ    any
    BPARCHIVE_SCHED    REG_SZ    any
    VERBOSE    REG_DWORD    0x0
    RESTORE_RETRIES    REG_DWORD    0x0
    LIST_FILES_TIMEOUT    REG_DWORD    0x12c
    DISALLOW_SERVER_FILE_WRITES    REG_SZ    NO
    ALLOW_NON_RESERVED_PORTS    REG_SZ    YES
    CRYPT_OPTION    REG_SZ    ALLOWED
    CRYPT_STRENGTH    REG_SZ    DES_40
    Debug_Database    REG_DWORD    0x0
    KEEP_LOGS_DAYS    REG_DWORD    0x3
    LOTUS_NOTES_LOGCACHESIZE    REG_DWORD    0x0
    CLIENT_RESERVED_PORT_WINDOW    REG_SZ    512 1023
    CLIENT_PORT_WINDOW    REG_SZ    0 0
    Time_Overlap    REG_DWORD    0x3c
    Buffer_Size    REG_DWORD    0x80
    Use_Archive_Bit    REG_SZ    YES
    Perform_Default_Search    REG_SZ    YES
    Accumulate_Files    REG_SZ    NO
    User_Directed_Timeout    REG_DWORD    0x3c
    Announce_DHCP_Interval    REG_DWORD    0x0
    Clear_Archive_Bit_Incr_Wait    REG_DWORD    0x12c
    Debug_Flush    REG_DWORD    0x0
    Debug_Heap    REG_DWORD    0x0
    Debug_Level    REG_DWORD    0x0
    Debug_TCP    REG_DWORD    0x0
    Error_Messages_Max    REG_DWORD    0xa
    Policy_Type    REG_DWORD    0xd
    Client_Version    REG_DWORD    0x1f4
    Case_Sensitive_Exclude_List    REG_SZ    NO
    Compress_Use    REG_DWORD    0x0
    Compress_Buffer_Size    REG_DWORD    0x3e
    Compress_Minimum_Size    REG_DWORD    0x200
    Cluster_Database_Force_Restore    REG_SZ    NO
    ChangeJournalUse    REG_SZ    NO
    GENERATE_ENGLISH_LOGS    REG_SZ    NO
    EXCHANGE_ENABLE_SIS    REG_SZ    NO
    REVERSE_NAME_LOOKUP    REG_SZ    ALLOWED
    AUTO_LOGOFF_TIMEOUT    REG_DWORD    0x0
    EXCHANGE_PERFORM_CONSISTENCY_CHECK    REG_SZ    YES
    EXCHANGE_IGNORE_CC    REG_SZ    YES

HKEY_LOCAL_MACHINE\Software\Veritas\NetBackup\CurrentVersion\Config\NTIO
    UseNTIO    REG_DWORD    0x0

the firewall in both server and client disable

In an earlier entry you had this error:

status: FAILED, (43) CONNECT_RESET; system: (10036) A blocking operation
 is currently executing. ; FROM 0.0.0.0 TO 192.168.2.173 192.168.2.173 vnetd VIA
 pbx

In the latest out put the master/media is 192.168.2.7 and the client is 192.168.2.150

So what is 192.168.2.173 that appeared originally?

On the client and master setup the program files\veritas\netbackup\logs\bpcd directory and then from the master server, via the NBU admin console, try and connect to that client.

Then attach the bpcd logs from both as text files

The first does say that a blocking operation is in progress - if you do not have firewalls do you have anti-virus or application protection (such as McAfee) that could be causing the issue

i change the ip address of client from 192.168.2.173 to 192.168.2.150 because of dhcb confliect

no it is  kasper but i disable the firewall in it

this is the client and server log files

OK - looking at those there are still problems - i would run bpclntcmd -clear_host_cache on master and client and reboot them both and then try again

You have to run "bpclntmd -clear_host_cache" after you make any change in IP address and host name.
Follow Mark's suggestion - it is better to stop NetBackup on both host first, then clear host cache and start NetBackup. If failed again, please post bpcd and vnetd logs on client of level 5.

bpcd and vnetd logs