Backup Archive Restore console on Windows client gives "cannot connect on socket" error

[WayneLackey]

This one is kind of strange. I have a Windows client running the NBU 7.0 client, and backups have been running great for this particular client, no issues. But when you launch the Backup, Archive, and Restore console on the desktop of the client, it launches, tries to open up a restore window inside the console, and then pops up an "Error: cannot connect on socket" message. The same thing happens when you close that interior window, then click the "select files for restore" option from the file menu, or the "restore" button underneath the menu bar. Any suggestions?

[Nicolai]

If host is win2008 or newer you must right click on the Netbackup icon and select "Run as administrator".

Try to Disable reverse name lookup:  bpclntcmd -reverse_name_lookup prohibited

Check name is correctly entered in the GUI, check software firewall allow traffic on 1556 both incoming and outgoing. Check name resolution is working as intended.

bpclntcmd command usage

http://www.symantec.com/docs/HOWTO72641

[Pritesh_Pisal]

Hi,

Please verify the entries in specify backup Macnine and policy type..

[sksujeet]

If you open the BAR on media or master server I am pretty sure you will able to see the restore for the client. As per Nicolai excellent post it is the issue with the nameresolution. Try to do nslookup to client from master server/media server and then from client.

[Karthikeyan_Sun]

Master:

Telnet CLINETNAME 13782

bpclntcmd -hn CLIENTNAME

bpclntcmd -ip CLIENTIP

bptestbpcd -client CLIENTNMAE -verbose

CLINET:

bpclntcmd -hn MASTERNAME

bpclntcmd -ip MASTERIP

bpclntcmd -pn

[WayneLackey]

@Karthikeyan, what kind of output should I be expecting from these commands?

[revarooo]

Master:

Telnet CLINETNAME 13782

- You'd expect to see a message saying "connected"

bpclntcmd -hn CLIENTNAME

- This should give you the hostname of the client and an IP. This is what the Master thinks is the IP

bpclntcmd -ip CLIENTIP

- This should show what the IP resolves the hostname as - it should be the name of the client

bptestbpcd -client CLIENTNMAE -verbose

- You should see  a response without an error similar to this (IPs here are just an example):

10.10.10.1:54224 -> 10.10.10.2:13724

CLINET:

bpclntcmd -hn MASTERNAME

- Same as above but for the Master server

bpclntcmd -ip MASTERIP

- Same as above but for the Master server

bpclntcmd -pn

- This will show you what the master thinks the hostname / IP is.