W10 INCOMING connections - missing network protocols

Page 1 of 2 12 LastLast
  1. jimbo45's Avatar
    Posts : 10,455
    Windows / Linux : Arch Linux
       #1

    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
    Attached Thumbnails Attached Thumbnails W10 INCOMING connections - missing network protocols-capture.png  
      My Computer

  2. topgundcp's Avatar
    Posts : 2,760
    MintMate19x64 Win10Prox64
       #2

    @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
      My Computer

  3. jimbo45's Avatar
    Posts : 10,455
    Windows / Linux : Arch Linux
    Thread Starter
       #3

    Hi there

    No go I'm afraid --same error as before.

    cheers
    jimbo
      My Computer

  4. lehnerus2000's Avatar
    Posts : 1,809
    W7 Ultimate SP1 (64 bit), LM 19.2 MATE (64 bit), W10 Home 1703 (64 bit), W10 Pro 1703 (64 bit) VM
       #4

    Didn't work for me either


    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:

    W10 INCOMING connections - missing network protocols-networking-missing-protocols.png
      My Computer

  5. jimbo45's Avatar
    Posts : 10,455
    Windows / Linux : Arch Linux
    Thread Starter
       #5

    lehnerus2000 said:
    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:

    W10 INCOMING connections - missing network protocols-networking-missing-protocols.png

    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
      My Computer

  6. Kari's Avatar
    Posts : 17,434
    Windows 10 Pro
       #6

    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:

    W10 INCOMING connections - missing network protocols-2014-10-11_20h44_34.png
    Last edited by Kari; 11 Oct 2014 at 14:15.
      My Computer

  7. lehnerus2000's Avatar
    Posts : 1,809
    W7 Ultimate SP1 (64 bit), LM 19.2 MATE (64 bit), W10 Home 1703 (64 bit), W10 Pro 1703 (64 bit) VM
       #7

    Kari said:
    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:

    W10 INCOMING connections - missing network protocols-2014-10-11_20h44_34.png
    Is your W10 install "real" or virtual?
      My Computer

  8. Kari's Avatar
    Posts : 17,434
    Windows 10 Pro
       #8

    Real, clean install on a laptop.
      My Computer

  9. lehnerus2000's Avatar
    Posts : 1,809
    W7 Ultimate SP1 (64 bit), LM 19.2 MATE (64 bit), W10 Home 1703 (64 bit), W10 Pro 1703 (64 bit) VM
       #9

    Working Now


    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.

    W10 INCOMING connections - missing network protocols-networking-access-w10-lm17.png

    I like the new attachment manager on TenForums. :)
    Last edited by lehnerus2000; 11 Oct 2014 at 21:28.
      My Computer

  10. Kari's Avatar
    Posts : 17,434
    Windows 10 Pro
       #10

    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.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:48.
Find Us




Windows 10 Forums