Assuming you're using the standard "vnetd" communication, port 13782 is no longer required as it was with version 5/5.1 ... just port 13724.
>From your NetBackup server(s), run "bptestbpcd -client< clientname>" for each client. Telnet on port 13724 will work, too, but the response is not as clear (as you have found ... the connection will NOT drop in 5 seconds if all is OK). If there are problems, I look at these - Are the firewalls of server and client open in both directions for port 13724? - If using DNS (why aren't you using DNS?!), make sure forward and reverse DNS lookups work. - Ensure the NetBackup server(s) is/are properly listed in the client configuration. - For Windows, ensure the NetBackup Client Service is started on the client. - For Windows, does the domain controller know of the NetBackup servers? - If multiple paths (IP addresses) are available, ensure NetBackup uses the path you want This catches nearly all setup problems I have. Cheers, Wayne On Wed, Nov 16, 2011 at 11:55 AM, rico78 <nbu-fo...@backupcentral.com>wrote: > Hi folks, > > Back again with my problems! > I've got a solaris 5.10 server with Netbackup 6.5 (which hostname is > master_server for the example) on which I'm trying to configure the clients! > > I've got one client , called for instance win2003_client1 under windows > 2003 on which I installed the netbackup client. > > From the NB java console in the host properties, I can see in the client > properties that server win2003_client1 but I can't establish a > communication. > I get error: > > socket read failed (status 23) > > Yet, from the Netbackup master server, I can ping win2003_client1! The > hostname of the client is well resolved! > I followed alos the instructions ( > http://www.symantec.com/business/support/index?page=content&id=TECH54563&key=15143&actp=LIST) > given by Netbackup on possible dns issues: > I added in /etc/hosts on the master server the hostname and ip address of > the client, and on the client, I added in > %SystemRoot%\system32\drivers\etc\hosts the master server ip address and > hostname > > From the master server: > - when I do a bpclntcmd -hn win2003_client1, it returns the correct > information on ip address and name > - a telnet win2003_client1 13782 does connect (is it normal however that > the telnet session ends after 5 sec?ie connection closed by foreign host) > > From the windows client: > - a telnet master_server 13782 does connect well > - command bpclntcmd -pn returns > 'expected response from server master_server > win2003_client1 win2003_client1 192.168.x.y 1267 > > Any other suggestion to look at why the connection can't be done? > > Thanks in advance! > > +---------------------------------------------------------------------- > |This was sent by edesam...@opentv.com via Backup Central. > |Forward SPAM to ab...@backupcentral.com. > +---------------------------------------------------------------------- > > > _______________________________________________ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu >
_______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
