After KB4058043, cannot access workgroup

Page 1 of 2 12 LastLast

  1. Posts : 51
    Windows 10
       #1

    After KB4058043, cannot access workgroup


    Everything was working until I installed KB4058043. I do not know if that was a coincidence or not, but after the reboot, I cannot access any of the computers on my workgroup. I do use Kaspersky anti-virus (reinstalled it just in case).

    I do see this:

    After KB4058043, cannot access workgroup-update_problem_2.png

    Internet is working on all of the computers.

    Suggestions?

    Todd
      My Computer


  2. Posts : 6,979
    windows 10
       #2

    Can you see ther pc can you ping them by name or by IP?
      My Computer


  3. Posts : 51
    Windows 10
    Thread Starter
       #3

    They are on my LAN, so I do not know how to ping them since they are part of 216,228.174.9. When I use FileExplorer, they no longer show.

    \rtc
      My Computer


  4. Posts : 6,979
    windows 10
       #4

    Use this tool does this see them try on a couple of pcs NetBScanner - NetBIOS scanner
      My Computer


  5. Posts : 1,471
    Win10 Home x64 - 1809
       #5

    Hey rtcary,
    In File Explorer (address bar) see if you can access them by \\PC_NAME or \\PC_INTERNAL_IP

    To get the internal IP ... Open Command Prompt as Admin and type ipconfig /all and look at the IPV4 Address

    Example ....
    IPv4 Address. . . . . . . . . . . : 192.168.1.2(Preferred)
      My Computers


  6. Posts : 51
    Windows 10
    Thread Starter
       #6

    Last night, Windows did another update, but with the same name (KB4058043) and now Mac can see the Windows 10 machine *and* the Linux server and connect.

    The Windows 10 can see neither. NetBScanner on the Windows machine can see the Mac; not the Linux.

    ipconfig gives the following:

    After KB4058043, cannot access workgroup-update_problem_4.png
      My Computer


  7. Posts : 1,471
    Win10 Home x64 - 1809
       #7

    Hey rtcary,
    Can you access you shares using my post #5 ?
      My Computers


  8. Posts : 51
    Windows 10
    Thread Starter
       #8

    Yes, I can access my Linux server (192.168.1.22), however it does not show up with ipconfig /all . The preferred IPV4 is 192.168.1.16, however I do not know what my network password is -- never been asked for that. However, I have the router set to 192.168.1.22 for the server.

    Here is the output:

    Windows IP Configuration Host Name . . . . . . . . . . . . : NUC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : NoEthernet adapter Ethernet: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) Ethernet Connection (3) I218-V Physical Address. . . . . . . . . : B8-AE-ED-76-43-96 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::a0f5:7cba:e030:7dde%12(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.16(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Wednesday, December 20, 2017 7:00:04 AM Lease Expires . . . . . . . . . . : Thursday, December 21, 2017 7:00:04 AM Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DHCPv6 IAID . . . . . . . . . . . : 129543917 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-79-E8-2C-B8-AE-ED-76-43-96 DNS Servers . . . . . . . . . . . : 192.168.1.1 NetBIOS over Tcpip. . . . . . . . : EnabledWireless LAN adapter Wi-Fi: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC 7265 Physical Address. . . . . . . . . : 34-13-E8-30-5C-BE DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : YesWireless LAN adapter Local Area Connection* 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter Physical Address. . . . . . . . . : 34-13-E8-30-5C-BF DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : YesEthernet adapter Ethernet 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Kaspersky Security Data Escort Adapter Physical Address. . . . . . . . . : 00-FF-1B-10-8A-24 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : YesTunnel adapter Local Area Connection* 4: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:9d38:953c:c68:187a:271b:51f6(Preferred) Link-local IPv6 Address . . . . . : fe80::c68:187a:271b:51f6%19(Preferred) Default Gateway . . . . . . . . . : :: DHCPv6 IAID . . . . . . . . . . . : 318767104 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-79-E8-2C-B8-AE-ED-76-43-96 NetBIOS over Tcpip. . . . . . . . : Disabled
      My Computer


  9. Posts : 51
    Windows 10
    Thread Starter
       #9

    This has been a learning experience for me, however I have been able to use the file explorer and connect to the two computers on my LAN:

    192.168.1.22 my server on it's fixed IP
    192.168.1.11 Mac computer on it's DHCP IP
    192.168.1.16 The IP for my Windows computer

    Took me awhile to figure out the passwords.

    The problem appears to be the fact that the Kaspersky Ethernet (#2) cannot be made. This is outside my expertise.

    Todd
      My Computer


  10. Posts : 1,471
    Win10 Home x64 - 1809
       #10

    Hey rtcary,
    As you probably figured out ... ipconfig only works on Windows (Linux & Mac it's ifconfig) and the command is for finding the Internal IP Address (IPV4 Address) for each PC.

    From your Win10 PC .. if you can access shares on the other PCs using the \\INTERNAL_IP_ADDRESS .. then you could use map network share so that they show in File Explorer again.

    Map Network Share Tutorial - Map Network Drive in Windows 10 Network Sharing Tutorials

    FYI ... I don't think KB4058043 (Windows Store Reliability) was the cause of the issue, but that your Win10 PC was updated to 1709. If it did, then probably the original issue that the other PC's disappeared from File Explorer / Network might have been caused by SMBv1 getting uninstalled.

    Win10 1709 and SMBv1 - https://support.microsoft.com/en-us/...r-version-1709

    The problem appears to be the fact that the Kaspersky Ethernet (#2) cannot be made. This is outside my expertise.
    Sorry ... don't know anything about Kaspersky, so can't help you there.
      My Computers


 

  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 10:01.
Find Us




Windows 10 Forums