Avoiding BorderManager Bind Errors

Novell Cool Solutions: Tip
By Dave Simons

Digg This - Slashdot This Posted: 9 Aug 2006

Problem

I recently updated my NetWare 6 server to NetWare 6.5 SP5. The NetWare server is a member of a Novell 1.6 cluster, with Novell BorderManager 3.8 running in it. After the upgrade from NetWare 6 to NetWare 6.5, Bordermanager does not run any more on the updated cluster node. In the "Novell BorderManager Proxy Cache Server" Console Screen, you see "Bind Error 48" - this meens that some anther services is using port 48.

Solution

Most times this is a Tomcat server issue. To resolve this problem,

1. Go to the sys:\tomcat\4\conf directory and open the server.xml file.

2. Search for: port="8080" minProcessors="5" maxProcessors="75"

3. Change the 8080 to 8081.

Now BorderManager will run fine.

You can also change the proxy port under the Bordermanager Setup page in NWAdmin.

Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com