Video Screencast Help

A read operation from a socket Failed

Created: 14 May 2010 | 15 comments
Anderson R. Gomes's picture

Helo gaise,

I have this enviroment.

Two Netbackup server

                      SRVNETBKP1 (windows)
                      SRVNETBKP2 (linux)

One Media Server

                     SRVMEDIA SERVER (windows)

the connection from SRVNETBKP2 to SRVMEDIASERVER don't work. the message below appears

below, i have more informations

I have connectivity on host and don't work.

what more I can make? angry

Comments 15 CommentsJump to latest comment

lu's picture

You should check that the name of the media server is resolved properly on the Linux server (check with 'host' or 'nslookup')

Anderson R. Gomes's picture

Yes. i can connect to the host by name or IP.

And i can cannect to the host by console java.


lu's picture

Yes but what happens if your run 'host mediaservername' on SRVNETBKP2 ?

Anderson R. Gomes's picture

when i run host mediaserver on srvnetbkp2 that is work!!!

Nicolai's picture

If you have multiple NIC on master and media, the traffic may select interfaces you don't expect. A update on bp.conf & vm.conf with those interface name will resolve the issue.

You may also set the REQUIRED_INTERFACE to force traffic thru a NIC.

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Anderson R. Gomes's picture


i have a only one NIC on the booth hosts.

Nicolai's picture

One thing to leave out then :-)

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Nicolai's picture

Are you sure the domain name of the server should be lab.local ?.

You need to check the lab.local name is used in all configuration files and can be resolved both forward and reverse from the master server. Else you might confuse Netbackup.

The master server uses short name, can you use sort name for the media server as well  (KISS Principe) ?

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.

Marianne's picture

I agree with Nicolai - rather use short names everywhere.
If you are using hosts files for name lookup and If FQDN is used, checked that hosts entries match on media and master servers.
For example:
On master: master loghost media

Media Server: media loghost master

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Anderson R. Gomes's picture


i test by hostname and dont work again.

thanks. i don't know what i do!angry

K Miller's picture

Is there a firewall running on the Windows Server... This will also cause the stataus 23... If on, try disabling!



I take it you checked hosts file entries on all servers and not only the media server.

Also confirm subnet and gateway on media server -

Do you have 2 master servers: SRVNETBKP1 (windows) as on the GUI you are using SRVNETBKP2.local.lab?

If this post is helpful in any way, please vote or mark as solution.
A thumbs UP will do as well....

Anderson R. Gomes's picture

Ok Mohamed, Tomorrow i try to do it and post the results here.


Rajesh_s's picture

Add ip's with fully qualified domain name in both the servers host files and then verify the connectivity.

I think you have one linux and one windows master server . Why you are trying to connect windows server as media server . please confirm