Netlogon is not accessible

[Unregistered]

I am trying your product on a laptop that is not in a domain. When I go to login I get this error:

\\%COMPUTERNAME%\Netlogon is not accessible...

The Network path was not found.

I know the error os becasue the there is no netlogon share on the this PC. Is there a way to configure Dekart Logon to not try and login to a domain?

[Alex Railean]

This could happen because you have a startup script which either resides on the share, or uses it somehow.

Make sure you don't have such a startup script.

You can check that by running the group policy editor (gpedit.msc), then navigate thru the menus (see the attached image).

[Unregistered]

I checked and I have nothing in listed in the logon script section. This is not start happening until install Dekart Logon.

[Alex Railean]

There is another location where startup scripts are listed:

A. The one mentioned in the previous message
B. Same location, but in the Computer Settings section
C. User management applet:

Start\Run -> compmgmt.msc
Select Local users and Groups\Users
Double-click your user
Switch to the Profile tab

Do you see anything in the Logon Scriptfield?

[Unregistered]

Nothing located there either. Again, its kinda strange that it only started after I installed Dekart logon. Would it have written this to the policy? Is there something in the code of Dekart that tries to run a script? ??????? Very strange and very frustrating. I love the product but I need to get this fixed before I consider buying?

[Alex Railean]

In that case, there are some alternative steps that should be tried. [Provided that you do not use Novell eDirectory]

<a> Delete the following registry key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run]
"RunLogonUtility"


This tool is responsible for executing scripts, and is not needed if you do not use Dekart Logon with Novell.
Once you perform this operation, restart the system and see whether the problem persists.

We will review the code of the program and see what could be causing the problem.

In the meantime, there is another temporary solution:
<b> Install Dekart Logon 2.20 (ftp://ftp.dekart.com/pub/products/Logon/2.20/English/logon.exe)
- You'll have to remove the current version first
- Then delete these files from Windows\System32 :dkar.dll, versnum.dll, dk_bioapi.dll
- Then install the new version

[Unregistered]

editing the registry still didn't work. Wht does the RunLogonUtility do? I will just wait until you guys can check your code out and see it there is anything in there that might be casuing the problem. Thanks

[Unregistered]

actually the funny thing is that I deleted that key but it showed back up after I rebooted. When I run ltool.exe it gives me that error so that is the problem for me... but how can I remove it if it comes back after reboot?

[Alex Railean]

Indeed, Ltool.exe will keep adding itself to the registry start-up section. The only way to disable that is too delete this file; though I advice you to rename it to something like _Ltool.ex, so that you could revert to the previous state without having to reinstall Dekart Logon.

The file is located in C:\WINDOWS\system32\

[Unregistered]

Great, thanks. That did the trick. I hope you guys come up with a solution so that I can fully test your app on several environments. I know that I will have atleast 3 domain environments and 4+ non-domain environments.

[Alex Railean]

We've released a beta that could fix this issue, and it would be great if we could get some feedback on it.
It can be obtained from this location: http://files.dekart.com/tools/logonb.exe