Forum Discussion

cgoliver's avatar
cgoliver
Level 5
13 years ago

Vstorage API and DFD

Hello,

We are working a problem (error 25 "cannot connect on socket) with our DMZ esx hosts. They both fail during, what I refer to as stage one.

The firewalls are not recording any drops to either the master, proxy, vcenter, or the esx host.

 

Any help would be appreciated.

 

Thanks,

Chris

  • FIxed this issue. It was an asymmetric FW problem. Open from UNIX MS to backup host, but not vice versa.

6 Replies

  • Can you ping in both directions - or at least resolve host names?

    This includes the VMWare Backup Host which needs to be able to resolve all hosted clients on the ESX Server to back them up

  • In addition to me previous post also remember that the ESX Servers themselevs have a built in firewall:

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

    Please also confirm that all other setting and authentication have been set up in NetBackup - have you tested the credentials when they were added - or does it already work and this is just your DMZ firewalled ESX Servers having issues?

  • just worked with chris...

    • switched policy over to manual instead of VIP
    • fails with status code 58
    • reverse lookup does not resolv back correctly
    • admin will work on hosts or dns fixes
  • Had one of our Windows Admin remove the forward, but they didn't remove the reverse and now we two reverse records.

  • You need to add them not remove them .. and they need to resolve according to the host name specified (VMHost name or VM Display name - which ever you have configured it for)

    Just used hosts files on the VMware Backup host  - an entry for each hosted server on the ESX Server that matches the name shown when the policy runs

    Hope this helps

  • FIxed this issue. It was an asymmetric FW problem. Open from UNIX MS to backup host, but not vice versa.