03-02-2012 07:54 AM
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
Solved! Go to Solution.
03-19-2012 01:29 PM
FIxed this issue. It was an asymmetric FW problem. Open from UNIX MS to backup host, but not vice versa.
03-02-2012 08:17 AM
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
03-02-2012 09:02 AM
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?
03-02-2012 11:35 AM
just worked with chris...
03-02-2012 12:07 PM
Had one of our Windows Admin remove the forward, but they didn't remove the reverse and now we two reverse records.
03-02-2012 02:15 PM
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
03-19-2012 01:29 PM
FIxed this issue. It was an asymmetric FW problem. Open from UNIX MS to backup host, but not vice versa.