Novell Home

My Favorites

Close

Please to see your favorites.

Troubleshooting BorderManager snapin issues

(Last modified: 06Feb2003)

This document (10052580) is provided subject to the disclaimer at the end of this document.

goal

Troubleshooting BorderManager snapin issues

fact

Problems with BorderManager snapin modules

Problems configuring BorderManager

symptom

BorderManager Snappins

BSMON, RESTRICT, BSCOV errors when launching NWADMN32

Previous version of BorderManager has been installed.  These snapins only administer BorderManager 3.0

The dynamic link library Z:\public\win32\snapins\BSMON.DLL cannot be located or is corrupted. Your path variable is invalid or your DLLs were not installed correctly

No BorderManager license installed

No BorderManager tabs showing up

BorderManager is not installed or is not available on this server

cause



I. NWADMN32 client server communication when BorderManager tab is enabled and selected

1.        For all BM component licenses, the following NDS transactions occur between the client and the BorderManager server ' make sure that no communication problems exist between client and server as functionality and performance issues will be experienced:
a.        make an NCP 'get NCP extension' info call for the BRDSRV_AGENT and gets a response from the BRDSRV.NLM if that attribute found in NDS that includes all the BRDSRV NDS objects. This verifies that BorderManager is installed on the server.
b.        send a request with Product name, and version to server it's running NWADMN32 off of. This verifies that we're trying to administer the correct version of BorderManager.
c.        check to see if NLS services are running on that server
d.        query BM component license and get the serial number back
e.        get details about that serial number The server reads all the BorderManager NDS information and sends back the object and attributes information for the client to display.

2.        The client then tries to do the following:
a.        Locate and open Sys:\public\win32\proxycfg.dll. This will read Proxy specific info from NDS and display that information
b.        Locate and open Sys:\public\win32\vpn.dll. This will read VPN (Client and Server) specific info from NDS and display that information
c.        Locate and open Sys:\public\win32\nls\English\proxycfg.lg (contains all Proxy messages that can be displayed in NWADMN).
i.        If it fails to locate this file, it tries to find it in the sys:\public\win32 directory.
ii.        If it doesn't exist here, it reads the subdirectories under sys:\public\win32\nls and starts checking all the <language> subdirectories for the proxycfg.lg file.
iii.        If it fails to find the file in any subdirectory, it uses default messages (this will not impact behavior in any way)
iv.        If you are running a localized version of NWADMN32 with BorderManager and are experiencing problems, try deleting this file from your NLS\<Language> directory.
d.        Locate and open Sys:\public\win32\nls\English\bdr_sec.hlp (contains information about SSL/security setup within Proxy as well as other Proxy information)
e.        Locate and open Sys:\public\win32\nls\English\vpn.lg (contains all VPN messages that can be displayed in NWADMN).
f.        If it fails to locate this file, it tries to find it in the sys:\public\win32 directory.
i.        If it doesn't exist here, it reads the subdirectories under sys:\public\win32\nls and starts checking all the <language> subdirectories for the vpn.lg file.
ii.        If it fails to find the file in any subdirectory, it uses default messages (this will not impact behavior in any way)

Note:

1.        If you are running and have configured rules that reference the CyberPatrol (CPFILTER modules), a search for the sys:\etc\border\English\cpfilter.acl file is also made by the client when the 'BorderManager Access Rule' TAB is enabled. This will generate a read of the CyberPatrol allow and deny lists and display the info in NWADMN32.

2.        The BorderManager SETUP and Acess Control TABs both generate a request to get the Version and License information before reading NDS information. The Alert tab simply gets the version before reading NDS and does not reference the licenses at all.


II. Troubleshooting tips:

1.        Verify that the BorderManager server is patched to the latest patch level. Below is a matrix of current core OS and BorderManager patches that impact NWADMN32 functionality and therefore need to be applied (Certain component issues may require newer versions of specific modules that are not mentioned here):

BM 3.0 running on NetWare 4.x: nw4sp8a.exe, bm3sp2.exe, bm3licfx.exe, nlslsp4b.exe, admn519f.exe
BM 3.5 running on NetWare 4.x: nw4sp8a.exe, bm35sp1.exe, nlslsp4b.exe, admn519f.exe
BM 3.5 running on NetWare 5.x   nw5sp4a.exe, bm35sp1.exe, nlslsp4b.exe, admn519f.exe

NWADMN519F.EXE fixes a huge number of generic NWADMN32 issues (see TID #2955955)

2.        Make sure that the BorderManager snapins are located in the correct directories. A tool exists called Handlex.exe (available at http://www.sysinternals.com/listdlls.htm) that allows you to dump all DLLs associated with a running Windows application. With SnapIns issues, it's a great way of verifying that the correct versions of the NWADMN32 BM snapin DLLs are running, and that they are being loaded from the correct directories.

Here is a list of the BorderManager related DLLs along with their directory placement:

M:\public\win32\snapins\ALERT.DLL         
M:\public\win32\snapins\BSCOV.DLL         
M:\public\win32\snapins\RESTRICT.DLL        M:\public\win32\snapins\NWCADM32.DLL

M:\public\win32\BRDEXT.dll
M:\public\win32\VPNA.dll                 // Used by VPN.DLL
M:\public\win32\VPN.dll                 // Used by BSCOV.DLL
M:\public\win32\PROXYCFG.dll         // Used by BSCOV.DLL
M:\public\win32\GSJPG32.DLL                // Used by BSMON.DLL
M:\public\win32\GSWAG32.DLL        // Used by BSMON.DLL
M:\public\win32\GSWDLL32.DLL        // Used by BSMON.DLL

The key to NWADMN32 operating correctly is in getting the appropriate DLLs copied over to the sys:\public\win32 and sys:\public\win32\snapins directories. Assuming that all the files can be found there, NWADMN32 will load successfully.
NWADMN95 and NWADMNNT used a different approach in that they would search the Windows registry for the location of the BorderManager snapin files and load them from this defined location.

3.        Make sure that no licensing issues exist with your BorderManager installation.  The easiest way of verifying this is to check to see if the 'BorderManager Alert' Tab generates the same problems that the BorderManager setup and access control tabs display.

From the algorithm described in step 1 above, the client running NWADMN32 will initially check to see whether or not licensing is installed and valid before displaying any information.

4.        Make sure that no mismatch exists with the BorderManager DLLs. Many of the DLLs have dependencies (e.g. BSCOV.DLL dependent on PROXYCFG.DLL and VPN.DLL) and as such, there should be no mixing up of older versions with newer versions.

5.        Make sure that the BorderManager DLL's have not become corrupted in any way. The easiest way of doing this is to reinstall the BorderManager DLLs and verify whether the problem continues. This can be done by

a.        Deleting the DLLs mentioned in step 2 above and;
b.        Re-running SYS:\PUBLIC\BRDRMGR\SNAPINS\SETUP.EXE on the BorderManager server so that the SNAPIN DLLs get recopied to the appropriate directory.


III. Information required when escalating call to Novell NTS

1.        Send in the output of the HandleEx tools described in step2 above. This will allow us verify that the correct directory structure for NWADMN32 exists.
2.        Send in any error messages that are being displayed in the NWADMN32 screen when the problem occurs

IV. Common BorderManager SnapIn issues.

1.        "No BorderManager license installed" error messages at the server console ' see TID #10050458

2.        After upgrading from BM30 to BM35, the following message occurs in NWADMN32 when trying to administer BorderManager: 'Previous version of BorderManager has been installed.  These snapins only administer BorderManager 3.0' ' see TID #2949429

3.        No BorderManager tabs showing up because BorderManager snapin modules not installed ' see TID #10018017

4.        NDS Objects showing up with question marks when running NWADMN32 from the BorderManager server ' see TID #10026308

5.        BSMON, RESTRICT, BSCOV errors when launching NWADMN32

Not able to launch NWADMIN to administer BorderManager
Error:  "The dynamic link library Z:\public\win32\snapins\BSMON.DLL cannot be located or is corrupted. Your path variable is invalid or your DLLs were not installed correctly"
Error:  "The dynamic link library Z:\public\win32\snapins\BSCOV.DLL cannot be located or is corrupted. Your path variable is invalid or your DLLs were not installed correctly"
Error:  "The dynamic link library Z:\public\win32\snapins\RESTRICT.DLL cannot be located or is corrupted. Your path variable is invalid or your DLLs were not installed correctly"

See TID # 10012751 and TID # 2947124

6.        Having too many Snapins on a server can cause the NetWare Administrator process to run out of "Thread Local Storage"  - see TID #10017335

7.        An explanation of the major BorderManager DLLs is available in TID #10024425
.

fix

Sometimes it is necessary to remove "Novell BorderManager" from the workstation and reinstall the snapins.
1) Add/Remove programs
2) remove "Novell BorderManager
3) reboot
4) Use Regedit to confirm it is out of the registry or use REGCLEAN from Mircosoft
ftp://ftp.microsoft.com/Softlib/MSLFILES/
http://support.microsoft.com/download/support/mslfiles/regclean.exe
5) Run Public\win32\nwadmn32.exe

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10052580
  • Solution ID: NOVL9180
  • Creation Date: 02May2000
  • Modified Date: 06Feb2003
    • NovellNetWare

      BorderManager Services

Did this document solve your problem? Provide Feedback