Windows 10: W10 INCOMING connections - missing network protocols

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

:)

 

PC and Laptop not seen to each other on home network after update KB3116900 W10

After W10 update KB3116900 I can connect to internet with my PC and Laptop but not each other. Error on both is "One or more network protocols are missing on this computer" and " Windows sockets registry for network connectivity are missing"

Desktop and printer connected to router via TPLink powerline. Laptop is WiFi. Desktop gets the printer but not the laptop. Uninstalled KB3116900 and reset Winsock but no change. Help please.

 

when I turn on my computer I have got something like no internet access

Hello

I have very strange issue about my connection to internet each time when I turn on my computer I have got something like no internet access

Windows Network Diagnostics

L: Publisher details

Issues found

L: One or more network protocols are missing on this computer

One or more network protocols are missing on this computer
Windows Sockets registry entries required for network connectivity are missing.

Not fixed

Restore network protocols to default settings

Completed

Issues found

L: Detection details

6

One or more network protocols are missing on this computer

Not fixed

Windows Sockets registry entries required for network connectivity are missing.

Windows Network Diagnostics

L: Publisher details

Issues found

L: One or more network protocols are missing on this computer

One or more network protocols are missing on this computer
Windows Sockets registry entries required for network connectivity are missing.

Not fixed

Restore network protocols to default settings

Completed

Issues found

L: Detection details

6

One or more network protocols are missing on this computer

Not fixed

Windows Sockets registry entries required for network connectivity are missing.

any one cat help me with this one??

many thanks

 

@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_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters]
"NullSessionPipes"=hex(7):6c,00,61,00,6c,00,61,00,6c,00,61,00,00,00,00,00
"restrictnullsessaccess"=dword:00000000
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"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_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters] 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?

 

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. *Redface



I like the new attachment manager on TenForums. *Smile

 

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.

 

I meant that I must have typed the address incorrectly:
//192.168.118.128
instead of:
smb://192.168.118.128 *Redface

 

My bad *Redface.

You get it working without IP, with computer names?

 

It was "My bad", not yours. *Smile

I have also been able to connect an XP VM to the W10TP VM (on LM17 Host) and share files each way (using Windows Explorer and File Explorer).

I haven't tried connecting by typing in the PC names yet.
I'm assuming that Windows Explorer and File Explorer use the PC names by default (based on previous usage).