If you have installed a new BorderManager 3.9 on a NetWare 6.5 SP6.

BorderManager was installed with DNS, HTTP/S, Real Player/RTSP proxies and not the VPN option, but when trying to access any of the BM settings in iManager, the browser doesn’t show anything.

iManager works fine for all other products and configurations.


  • Restarted Apache/Tomcat.
  • Reinstall BorderManager.
  • Uninstall/reinstall the iManager plugins.
  • Ran the fillattr process.
  • Put a eDirectory replica on the server.
  • Ran dsrepair on the Master and R/W replicas and didn’t get any errors.
  • Check timesync for all server and didn’t get any errors.

But…the problem still remains.

Try this.

First Phase

  • With ConsoleOne check all BM´s attributes in the server, specially BDRSRVR: PROXY Info DeviceXLM attribute.
  • If you see a lot of zeros (0) into BDRSRVR: PROXY Info DeviceXLM attribute, follow to next step — if not go to Second Phase.
  • The BDRSRVR: PROXY Info DeviceXLM attribute has a long configuration in this attrib, something like this:
<romaAGDevice ConfigUserName="config.ics.ics_tree" ManagementAddress="" ManagementPort="1443" ConfigPassword="Hd93k01@3fdKh3" DeviceDescription="" DeviceLocation="" DisplayName="" DeviceVersion="1.5.0000.DEV" DeviceType="ag" exA>

  • With any LDAP Administrator software (Softerra LDAP Administrator is well), replace this attribute or copy it from another BorderManager 3.9 server.
  • Run a DSrepair and check for any messages.

Second Phase

  • Through an old NWadmin with BorderManager 3.8 snapins, modify the configuration of the BM server. (This wrote the configuration in format 3,8 or lower in the server object).
  • In the Logger (server console) see a message reporting something like “the change should be made with iManager”.
  • Import the configuration with the FILLATTR utility.
  • ¡Ready! iManager can read the configuration in the proxy section.

I hope this helps.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Tags: ,
Categories: Uncategorized

Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment.  It just worked for at least one person, and perhaps it will be useful for you too.  Be sure to test in a non-production environment.

Leave a Reply

Leave a Comment

  • chirock says:

    This is clearly a good answer, but some people might not interpret some of it the same way the writer does. Also, some people may need to have some steps included that the writer naturally assumes they will know to take, so those steps are skipped over.

    If you are going to document, please document completely. And assume nothing, as far as your readership is concerned.

  • crivera says:

    Thanks Chirock by your suggestion.

By: crivera
Jun 19, 2008
12:32 pm
Active Directory Authentication Automation Cloud Computing Cloud Security Configuration Customizing Data Breach DirXML Drivers End User Management Identity Manager Importing-Exporting / ICE/ LDIF Intelligent Workload Management IT Security Knowledge Depot LDAP Monitoring Open Enterprise Server Passwords Reporting Secure Access Supported Troubleshooting Workflow