Environment:
Master Server Windows 2003 Server, Standard /w NBE 6.0MP5
Client: RHL 2.4 (really a load from VMware 3.0.1)
Loaded the RHL 2.4 client from the 5.1 media kit and listed below are the changes I made in order to get the master server to communicate with the client because the client is behind a firewall.
Modified the services.xml as suggested at the bottom of this message in the vmware community:
Added the client to the master server through the Admin GUI per:
http://seer.support.veritas.com/docs/251630.htm
reviewed /etc/services file on client
--snip--
bprd 13720/tcp # BPRD (VERITAS NetBackup)
bprd 13720/udp # BPRD (VERITAS NetBackup)
bpdbm 13721/tcp # BPDBM (VERITAS NetBackup)
bpdbm 13721/udp # BPDBM (VERITAS NetBackup)
bpjava-msvc 13722/tcp # BP Java MSVC Protocol
bpjava-msvc 13722/udp # BP Java MSVC Protocol
vnetd 13724/tcp # Veritas Network Utility
vnetd 13724/udp # Veritas Network Utility
bpcd 13782/tcp # VERITAS NetBackup
bpcd 13782/udp # VERITAS NetBackup
vopied 13783/tcp # VOPIED Protocol
vopied 13783/udp # VOPIED Protocol
--snip--
Rebooted the client and restarted the NB services on the Master Server. Still no joy when trying to connect to the client. Client connection times out. The bad thing here is that I was able to communicate with it after working through the problem the first time. I believe I am missing a step where I changed a configuration file. Yes, i was able to get through the problem, but then we reloaded this system and now I cannot get it to communicate....shame on me for not documenting it. Anybody know the missing step here or have any suggestions?
Thanks!