Currently IiopVbServerBind performs a UDP broadcast in order to locate a VisiBroker SmartAgent, and if successful, queries the SmartAgent for an object reference. However there are instances when the SmartAgent is not on the same subnet as the client and as such a UDP broadcast will not find the SmartAgent. In these cirsumstances SilkPerformer will likely generate the following error: IiopVbServerBind(IIOP: 72 - No valid answer received upon broadcast (Cannot contact the SmartAgent)) In such circumstances the client will likely have the hostname and port of the SmartAgent in a configuration file and therefore does not experience any problems. SilkPerformer, on the other hand needs to know the host name of the SmartAgent before a successful connection can be established. In SilkPerformer 6.5 the IiopVbServerBind will allow an additional "host name" parameter so that if the SmartAgent is not on the same subnet as the client (or SilkPerformer) then a direct UDP connection can still be established. If you are currently using SilkPerformer 6.0.1 and need to have this functionality you can install a patch (IIopVbServerBind) which enhances the IiopVbServerBind function to take the host name parameter. This patch is included in SilkPerformer 6.5
↧