Oct 20, 2017 5:04 AM
1 Posts

no network drive connection after installation of "client single logon" at "Windows 10 1709 fall creators update"

  • Category: Notes Client
  • Platform: Windows
  • Release: 9.0.1
  • Role: Administrator
  • Tags: single logon,Windows 10 1709
  • Replies: 3

Hello everybody,

after the upgrade to Windows 10 1709, the one-time logon with the operating system no longer worked.
After reinstallation of "client single logon function", the one-time logon functioned again, but no network drive connection with Windows was possible. So the "net use ...." command no longer worked.


I found out that the cause of the problem is the registry key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder".
The structure of this key has probably changed with the Windows version 1709.

The solution to the problem is the manual modification of the registry:
I created a reg file with the following content:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider]
@=""

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\HwOrder]
"ProviderOrder"="RDPNP,LanmanWorkstation,webclient,npnotes64"

[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\ProviderOrder]
"LanmanWorkstation"=dword:000007d0
"RDPNP"=dword:000003e8
"webclient"=dword:00000bb8
"npnotes64"=dword:00000fa0

 

Now "client single logon" and the network connection works again.

My request to IBM: please create a FixPack that fixes this problem.

Best regards
Matthias Luger

Oct 23, 2017 12:05 PM
171 Posts
Good catch!

 

Oct 23, 2017 3:00 PM
291 Posts
Always been an issue

This has been an issue since 8.0 days.  In your case windows update change the order of the loading of each component.   I think the only way it can really be fixed is as each company does their os updates and clients updates they see if the key is impacted and write a script to "repair" it

 

Here are some tech notes relating to the order

 

http://www-01.ibm.com/support/docview.wss?uid=swg21304525

 

 

Dec 21, 2017 7:36 AM
1 Posts
Registry change won't do the trick

Hello together,

I also upgraded two Windows 10 machines from Windows 10 version 1703 to 1709. Unfortunately the mentioned fix is not working for me. When I try to start Notes with the SSO feature enabled it says that my Windows password would not match my Notes password which isn't true. Notes offers me to change the password after logging in but this will fail as well for the same reason (Windows password would not match). 

I already tried to change my Windows 10 password but it would not help either. I also read and executed the steps mentioned here but with no success: http://www-01.ibm.com/support/docview.wss?uid=swg21304525

Had anybody else this issue and can help? I am experiencing this since every Windows 10 major Windows 10 release now (SSO would not work after upgrading to version 1703 in the past) but I could help myself always with fixing the registry or doing a clean Lotus Notes install on the machines that did not work with the registry hacks but this time I have two computers with the same issues and nothing works. On both I doublechecked the registry and on both I made a clean Lotus Notes installation but still I have to struggle with the above mentioned issue. I would be happy about some help on fixing this.