Network access issue on NT4 network drive
Solved
Treza88
-
Treza88 -
Treza88 -
Hello everyone,
I'm reaching out for your help because I'm in a real bind. After a power outage (at least I think that’s what caused it), I have 2 computers running Windows 10 and one running Windows 8.1 that can no longer access my server running NT4, and consequently, I'm not allowed access to the network drive on this server.
When I click on the server in my network favorites (where I see all my other PCs and my server), it prompts me to log in and enter a password, which wasn't the case before. Moreover, the password and login don't work.
My network was functioning properly for years before this outage.
Do you have any suggestions for what to investigate, because I'm really in the dark here; everything seems correct with my configurations, and nothing is working.
Additionally, I have a virtual machine with Windows XP on my computer running Windows 8.1 that accesses the server without any issues.
Thank you in advance to anyone who can lend a hand.
I'm reaching out for your help because I'm in a real bind. After a power outage (at least I think that’s what caused it), I have 2 computers running Windows 10 and one running Windows 8.1 that can no longer access my server running NT4, and consequently, I'm not allowed access to the network drive on this server.
When I click on the server in my network favorites (where I see all my other PCs and my server), it prompts me to log in and enter a password, which wasn't the case before. Moreover, the password and login don't work.
My network was functioning properly for years before this outage.
Do you have any suggestions for what to investigate, because I'm really in the dark here; everything seems correct with my configurations, and nothing is working.
Additionally, I have a virtual machine with Windows XP on my computer running Windows 8.1 that accesses the server without any issues.
Thank you in advance to anyone who can lend a hand.
10 answers
Another interesting link related to the first one: https://support.microsoft.com/en-us/help/982734/you-cannot-access-a-shared-folder-that-is-located-on-a-windows-2000-or
What is interesting to note:
Cause:
Windows 7 and later use NTLM version 2 (NTLMv2) authentication. By default, NTLMv2 authentication is not enabled in Windows 2000 or Windows 98. Consequently, this problem occurs.
Resolution
To resolve this issue, enable NTLMv2 authentication on the Windows 2000 (or NT4) or Windows 98 machine. To do this, follow these steps:
Start the Registry Editor. To do this, click Start, click Run, type Regedit, and press ENTER.
Locate and click on the following registry subkeys:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA
Find the registry value LmCompatibilityLevel.
If the registry value is not present, follow these steps to create it:
Select the registry subkey listed in step 2.
In the Edit menu, point to New, and then click DWORD Value.
Type LmCompatibilityLevel and press ENTER.
Set the DWORD value to 1. To do this, click Modify in the Edit menu, type 1 in the Value data box, and then click OK.
Exit the Registry Editor and restart the computer.
"Alea jacta est: they are talkative at the Gare de l'Est." (P.Desproges)
What is interesting to note:
Cause:
Windows 7 and later use NTLM version 2 (NTLMv2) authentication. By default, NTLMv2 authentication is not enabled in Windows 2000 or Windows 98. Consequently, this problem occurs.
Resolution
To resolve this issue, enable NTLMv2 authentication on the Windows 2000 (or NT4) or Windows 98 machine. To do this, follow these steps:
Start the Registry Editor. To do this, click Start, click Run, type Regedit, and press ENTER.
Locate and click on the following registry subkeys:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA
Find the registry value LmCompatibilityLevel.
If the registry value is not present, follow these steps to create it:
Select the registry subkey listed in step 2.
In the Edit menu, point to New, and then click DWORD Value.
Type LmCompatibilityLevel and press ENTER.
Set the DWORD value to 1. To do this, click Modify in the Edit menu, type 1 in the Value data box, and then click OK.
Exit the Registry Editor and restart the computer.
"Alea jacta est: they are talkative at the Gare de l'Est." (P.Desproges)
Ok thanks davedrink
I consulted the first link, a page I had already skimmed through, but it seemed very complicated. However, as you presented it to me, I looked into it more closely and resolved my issues; it was indeed the authentication level that was not defined.
And on top of that, gpedit.msc was not installed on some PCs, so I had to install it.
However, for what reason the settings were changed on all three PCs is a great mystery.
Thanks again for the help; I would have never figured it out on my own.
I consulted the first link, a page I had already skimmed through, but it seemed very complicated. However, as you presented it to me, I looked into it more closely and resolved my issues; it was indeed the authentication level that was not defined.
And on top of that, gpedit.msc was not installed on some PCs, so I had to install it.
However, for what reason the settings were changed on all three PCs is a great mystery.
Thanks again for the help; I would have never figured it out on my own.
Yes, it's clear I'm breathing because not having access to that network drive was blocking all IT production for us.
And yes, on all client workstations in "Network Security: LAN Manager authentication level," instead of "not defined" in the properties, I replaced it with "Send LM & NTLM – use NTLMv2 session security if negotiated."
And everything returned to normal, like magic.
But for me, how this setting could have been changed when everything had been working perfectly for years will remain a mystery.
And I repeat, thank you once again to you, to this forum, and to all the forums that help people like me.
And yes, on all client workstations in "Network Security: LAN Manager authentication level," instead of "not defined" in the properties, I replaced it with "Send LM & NTLM – use NTLMv2 session security if negotiated."
And everything returned to normal, like magic.
But for me, how this setting could have been changed when everything had been working perfectly for years will remain a mystery.
And I repeat, thank you once again to you, to this forum, and to all the forums that help people like me.
Hello,
Are you on a domain or in a workgroup?
With the domain admin account you shouldn't have any issues accessing your shared resources.
I assume you are in a workgroup.
Start by turning off all the machines on your network, then turn on your server and then start your client machines. Try to access your resources!
Keep us updated
Best regards
Are you on a domain or in a workgroup?
With the domain admin account you shouldn't have any issues accessing your shared resources.
I assume you are in a workgroup.
Start by turning off all the machines on your network, then turn on your server and then start your client machines. Try to access your resources!
Keep us updated
Best regards
After 30 to 40 seconds of waiting still the login password window
on another partition of the server with:
\\192.168.1.11\E (share with everyone permission and full control)
on another partition of the server with:
\\192.168.1.11\E (share with everyone permission and full control)