Cool Solutions

A handy network diagnostic


February 19, 2008 1:16 pm





On April 13th 2007 Novell released a new Winsock patch for NetWare, wsock6l. In that Readme, was this line:

Technical Support Information:
Included a new module called WS2NRM.NLM which is a replacement for winsock NRM diagnostics. Only needs to be loaded to troubleshoot winsock related issue through NRM.

And didn’t tell anything else about this new thing. I found out about it on a recent support call. What it does is enable a new diagnostic page in the Novell Remote Manager for NetWare to track Winsock2 issues. This is handy!

NRM menu bar

Why is it handy, you may ask? Because it has the ability to give detailed information about winsock2 sockets. In my case I was having trouble with mod_edir hammering servers with NOT_LOGGED_IN connections. With this I was able to see the state of those connections from a Winsock point of view. It manifested as a whole bunch of open sockets assigned to LIBC.

You can get to those counters by clicking on the “Winsock 2 Resources link”. It’ll list all the modules using Winsock2 resources, one of which is Libc. Click on the module to get the open sockets assigned to that module.

In this case the connections were being charged against LIBC instead of either MOD_EDIR or APACHE2 because MOD_EDIR called NXCreatePathContext to contact remote servers, a LIBC function. Therefore LIBC got charged for the connection.

In order to add it to NRM you just have to load WS2NRM.NLM, and removing it is as simple as unloading WS2NRM. I’ve found it an interesting troubleshooting tool, and it isn’t much known about. Have fun!

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.

Categories: Uncategorized


Disclaimer: This content is not supported by Micro Focus. 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 it thoroughly before using it in a production environment.