This documentation supports the 20.02 (12.0) version of BMC Discovery.

To view an earlier version of the product, select the version from the Product version menu.

Troubleshooting Windows proxies

If you have installed a Windows proxy and it fails to connect, there are a number of checks that you should make before contacting Customer Support.

Checking the keys and certificates

The appliance and Windows proxy communicate through an encrypted channel. In order for the Windows proxy to communicate with the appliance, each end requires the certificate of the other end. Visit the appliance user interface, from the main menu, click Manage > Credentials. The Credentials page displays. Click Windows Proxies to see status information from the appliance point of view, and visit the Proxy Manager Edit > Known Appliances dialog. Ensure that both ends have correct certificate fingerprints and have approved the connection.

Checking for an omniORB.cfg file

The communication between appliance and Windows proxy uses the omniORB CORBA implementation. Configuration of omniORB can affect communication. omniORB's configuration is stored in C:\omniORB.cfg. In a normal Windows proxy install, that file is not present. If it is present, its contents might prevent communication with the Windows proxy, or might cause other problems.

Restricting appliances that can connect

omniORB can be configured to only permit connections from particular IP addresses. This is achieved by adding lines of this form in C:\omniORB.cfg:

serverTransportRule = <ip address> ssl
serverTransportRule = localhost tcp

Add one line for each appliance IP address with the ssl qualification, and one single line for localhost tcp.  If multiple appliances are to use the same Windows proxy, one serverTransportRule line for each appliance should be added.

Only the specified IP addresses can connect with SSL, and internal communication between components of the Windows proxy is permitted over TCP. 

Was this page helpful? Yes No Submitting... Thank you