Hi there
It seems that for earlier computers such as XP / W7 or even Linux machines connecting TO a W10 machine causes problems unless you connect via an IP address.
Even if you apply the "Fix automatically" it still doesn't work and if you re-try the INCOMING connection you've STILL got the same diagnostic. (Note this is for computers connecting TO w10 not W10 connecting TO OTHER computers that way round works in all cases).
I've tried also netsh winsock reset but that din't fix it either.
Cheers
jimbo
@jimbo45
I did have problem accessing Windows 10 from my Windows 8.1 PC/Media Player. So here's what I did to fix. If you wish, you can try. Copy/Paste and save as reg file then merge into registry.
From Admin Command: run ipconfig /flushdns
Reboot your PC.
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesLanmanServerParameters]
"NullSessionPipes"=hex(7):6c,00,61,00,6c,00,61,00,6c,00,61,00,00,00,00,00
"restrictnullsessaccess"=dword:00000000
[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlLsa]
"everyoneincludesanonymous"=dword:00000001
"NoLmHash"=dword:00000000
Hi there
No go I'm afraid --same error as before.
cheers
jimbo
I tried the "LanmanServer" and "everyoneincludesanonymous" hacks that allow my media box to talk to W7.
They didn't work.
I noticed that the [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesLanmanServerParameters]key in W10 is different to the W7 one.
When I ran the W10 "Troubleshooter" I got this message:
I tried the "LanmanServer" and "everyoneincludesanonymous" hacks that allow my media box to talk to W7.
They didn't work.
I noticed that the [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesLanmanServerParameters]key in W10 is different to the W7 one.
When I ran the W10 "Troubleshooter" I got this message:
Hi there
Even if you "Correct" via this - it still doesn't work - even after reboot of ALL computers on the LAN.
There's definitely something in Networking on W10 that's changed.
I tested it again with a W7 X-64 computer to double check --it can SEE the W10 computer but can't access it's shares unless as before you access it via IP address rather than Hostname. The W10 machine has no problems accessing W7 computer's shares also via HOSTNAME.
Now Ms might not worry about access from Linux or XP but it will HAVE to do something about the W7 access. Many businesses are still on W7 and they have to sell W10 to these customers.
So to recap - It's access TO W10 FROM W7 not the other way around which works perfectly.
Cheers
jimbo
As long as the Linux machines belong to same workgroup than Windows 10, I have no issues in connecting using computername instead of IP. Here CentOS vm connected to a shared backup drive on Windows 10 using computername:
Is your W10 install "real" or virtual?As long as the Linux machines belong to same workgroup than Windows 10, I have no issues in connecting using computername instead of IP. Here CentOS vm connected to a shared backup drive on Windows 10 using computername:
Real, clean install on a laptop.
It's working now.
My "real" LM17 can access files on W10TP VM.
I didn't make any changes to the VM (I reversed the Registry hacks I tried).
I must have forgot to use "smb:" when I was playing around yesterday.
I like the new attachment manager on windowssh blog.
Yeah SMB is important.
I got file sharing from / to Linux (CentOS, Mint, Suse) to work simply by installing Samba and setting Linux machines to same workgroup than my Windows workgroup.
