Search results for query: *

You should see one nls_lsp for each server you have upgraded with licensing services. My guess is that you have a problem with NDS. One thing I have found essential is to have a 5.1 server as the primary NDS partition and to run Dsrepair repeatedly on it before installing the NLS update on 4.x...

It does usually point to interruption of communication between novell servers, assuming you have more than one server. A bad cable is first place to check. Second is the NIC installed in the server, [are the drivers up to date?]. Third, is there chatter such that another PC is hogging the net...

Assuming that you have Novell 4.11 or greater, you can use auditing services & Auditcon to track file modifications, creations & deletions on the SYS volume. It won't tell which lines are changed, but everything else about it. Review the options carefully when setting up auditing so that your...

Definately check the NIC drivers. The Service Pak 6 may replaced them with a different ODI method driver. Try using the original drivers that came with the NIC. Or better yet, replace them with a different network NIC card.

What happens is that Novell Client 32 tries to install WINSOCK2. It is usually successful, sometimes though with lots of NIC changes it is not able to. <br> <br> One method that has worked for me is to use Microsofts WINSOCK2 upgrade in another Win95 PC that has the MS 16 bit client on it. <br>...

You can refer to Novell Support Connect Web site TID 2942570<br> which details changing mouse com port. Briefly though the instructions are as follows:<br> <br> Exit the GUI <br> <br> At Console Prompt, type NETBASIC, and SHELL.<br> <br> CD\SYS:JAVA\NWGFX.<br> <br> Either delete or rename...