FAQShop.com : "Error: Unable to convert NAL path "\SITES\PER\caplist.ini" to NOS specific path..."

"Error: Unable to convert NAL path "\SITES\PER\caplist.ini" to NOS Specific Path...

I'm having difficulty getting the Client installed on one of our Regional CAP's on a resource Domain Controller. This is driving me nuts and I really need to Remote Control to that Server. It comes up with the error below from the "WN_LOGON.Log":

"ERROR: Unable to convert NAL path "\SITES\PER\caplist.ini" to NOS specific path - The parameter is incorrect. $$<CliEx32.dll><Thu Aug 31 13:48:02.656 2000 Syd2000 Standard Time><thread=128 (0x80)> The caplist.ini does exist, has enough permissions and contains
[Site]
Site Code=PER
NumServers=1
Server1=Server1
[Server1]
NAL Path=MSWNET:["SMS_SITE=PER"]\\AUPER002\CAP_PER\
NAL Resource Type=Windows NT Server

[IDENT]
TYPE=Base Config File Type"

This problem can be caused by a corrupt "NAL" path in the registry on your Site server(s). To resolve this problem you'll need to delete the NAL path Registry keys and rebuild them by re-registering DLLs manually as follows:

Stop the "SMS_Site_Component_Manager" and "SMS_Executive" services.
Add a value to the registry key "HKLM\Software\Microsoft\NAL\Server\Providers" called "Active Order". This key should be a "Reg_Multi_SZ" with the string values: "LOCAL, MSWNET, NWNDS", and "NWBIND".
Run "Regsvr32 -u" on "abnwsvr.dll, falsvrn.dll, mslmsvrn.dll, ndssvrn.dll", and "bindsvrn.dll".
Run "Regsv32" on "abnswvr.dll, falsvrn.dll, mslmsvrn.dll, ndssvrn.dll", and "bindsvrn.dll" in that order.
Restart the "SMS_Site_Component_Manager" service. These DLL files are located in the "\sms\bin\<platform>" folder (where "<platform>" is "i386" or "alpha"). You can re-register all of the DLL's. The NetWare ones will not be invoked if there are no NetWare redirectors on the machine.

During Step 4 when re-registering the NAL DLL's, the "NAL\Server" key should be rebuilt on the site server where: "mslmsvrn.dll (MSWNET) falsvrn.dll (LOCAL) bindsvrn.dll (NWBIND) ndssvrn.dll (NWNDS)" and "abnwsvr.dll (ABEXPRT)". This should manually get the "NAL" key recreated and get the Site server operational again.