Windows 10 Network problem between Win 7 and Win 10

[John Clark]

I've been having a problem getting my computers to fully connect to each other on the network. My wife has a HP laptop with WIN 10 Home edition. My machine is a desktop with WIN 7 Pro. The desktop can see the laptop but cannot log on or access the laptop, while the laptop can log onto DT and access all shared directories. The info in the Credential managers are correct for both machines.
At one time the machines could access each other but with updates from Microsoft the connections were broken.
Attached are 2 files containing system and network info for both machines. I would like to find out how to solve this problem.

 

[John Clark]

They're within 2 seconds of each other.

 

[John Clark]

They're within 2 seconds of each other.

 

[John Clark]

The machines are within 2 seconds of each other.
Policy does not exist.

 

[Neemobeer]

You can either update the admx templates or just set it manually in the registry

Key: HKLM\System\CurrentControlSet\Control\LSA
DWORD SuppressExtendedProtection to 1

 

[John Clark]

Sorry about the multiple post, did not realize that we moved to second page.
Made addition to registry and rebooted. Was previous policy to be added?
If so it didn't show up.

 

[Neemobeer]

No, enabling the registry setting is the equivalent of enabling the gpo setting.

 

[John Clark]

Where do we go from here or are we at a dead end?

 

[Neemobeer]

Did you enable the setting and reboot?

 

[John Clark]

I made the key addition and rebooted.

 

[Neemobeer]

Oops in reply 24 the value needs to be set to 1 not 0.

 

[John Clark]

Change made and rebooted. Still no access to LT.
Don't know if this will add to the confusion but printer sharing is turned on and the LT can print to laser printer connected to the desktop. Also I have a program on both machines that tallys up the bandwidth used and shows usage for each of us and total on each machine.

 

[John Clark]

I assume that we're at a dead end here? No solution to the problem?

 

[Neemobeer]

Well the basic process of accessing an SMB resource via NTLMSSP is the following

Client sends a negotiate request
Server sends a negotiate response (to agree on smb version, NTLM mechanism and authentication provider )
Client uses the agreed upon smb version NTLM etc
Server sends a challenge to validate the account is correct, password
The challenge has a server challenge value

The client using the credentials creates a hash from that 16 bit value and sends it in the response
The server also hashes the 16 bit challenge and compares it with what the client is sending

So basically these hashed values are not match
The logical conclusion is the credentials are not correct or the hashing mechanisms are not the same (although for this usually the connection would fail on the initial negotiate request/response

Since they are local creds the machine name, username and password all need to match that being used on the remote system and that you have access to the smb share you're trying to connect to.