Article
2378
Avoiding BorderManager Bind Errors
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.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.
Related Articles
User Comments
- Be the first to comment! To leave a comment you need to Login or Register
- 2378 reads
0