Computers can't see each other after upgrade to 1803

Page 7 of 11 FirstFirst ... 56789 ... LastLast

  1. Posts : 46
    Windows 10
    Thread Starter
       #61

    When my problems, or challenge first started, I found a little program that sniff's IP address and is very simple. Once it finds the computers on the network, I can see, view and use programs just like I should via the normal network routines.
    Check it out.
    Advanced IP Scanner - Download Free Network Scanner.
      My Computer


  2. Posts : 14,046
    Windows 11 Pro X64 22H2 22621.1848
       #62

    It says "It is easy to use and runs as a portable edition." yet when I downloaded it and opened it, it wanted to install. Why? I want the portable version.

    Edit:
    NM< next window allows install or run.

    Nice tool, thanks for the info.
      My Computers


  3. Posts : 44
       #63

    Access Denied said:
    The reason the 2 computers are not seeing each other is Microsoft turned off SMBv1. Since your NAS and other devices are working fine right now, all you need to do is fix one service that is messed up in 1803. There is a service you need to set to Automatic start: Function Discovery Resource Publication Right click the Start button and click on Run near the bottom of the menu that shows. Type services.msc in the Run box and press enter to open the Services List. Scroll down until you find the Function Discovery Resource Publication. Set it to Automatic. Then right click and start it. That PC will now show up. You need to do this on all computers in the Network that are running April update 1803.
    Thanks, this solved it for me and I can access all file shares again. Is this intentional or is it just another example of Microsoft's poor recruitment skills? Every new winver introduces something like this. Rarely anything catastrophic (if you don't count the forced driver updates that makes hardware unusable) but always some minor headaches that you have to search forums to solve.
      My Computer


  4. Posts : 1
    Windows 10
       #64

    I've been struggling with this same issue all week, and most of the fixes have proved temporary.

    I've done the Function Discovery Pub / Host service fix, which did solve the problem for 15-20 minutes. In the middle of transferring files, the connection broke. Restarting the two computers and an ipconfig /flushdns caused them to work for another 30 minutes or so.

    I then disabled password protected sharing, made sure both computers were set to private network, and confirmed that the "Everyone" group had access. The two computers worked fine and could see each other for the rest of the evening (about 6 hours). However, after turning them off last night and back on this morning, I'm back to them not being able to connect to each other.

    Both computers have been rolled back to before the April 2018 update, but the issue still persists. I don't want to, but is the only solution at this point to assign each desktop a static IP in the router? Neither PC had their IP change this morning, so I'm not sure why the connection broke yet again. IPconfig /flushdns didn't solve the problem this time.

    I can SEE both PC's through the "Network" menu, but when I try to connect it'll say Network Path Cannot be Found.

    I appreciate any input. It's frustrating me that I'll get it fixed, and then it'll stop working shortly after even though no changes were made.
      My Computer


  5. Posts : 1,099
    Win 10 pro Upgraded from 8.1
       #65

    My 2 cents worth 3 of my computers P2P network work fine without SMB 1 turned on, the one computer 0n 1709 that I have been unable to get 1803 to install on I still have to have SMB 1 turned on. I assume once I get that computer to either install 1803 or Clean Install it will also work without SMB 1 So for me with my long time P2P workgroup network 1803 does solve the issue of SMB 1
    I actually had all 4 computers running SMB 1 on 1709 and 8.1 on one computer and was able to turn SMB 1 off on all both 2 1803 computers and the 8.1 computer that one computer is having some issue I can't seem to resolve to prevent it from installing 1803.
    Teamviewer works fully on all four computer no issues at all

    Update finally got 1803 installed and turned off SMB 1.0 all 4 network computer communicating with each other no issues
    Last edited by Clintlgm; 18 May 2018 at 06:34.
      My Computers


  6. Posts : 5
    Windows 10 1803
       #66

    Try this easy fix. In the Cortana search box type 'network status' and hit enter. When the status screen comes up, scroll to the bottom and left click "Network Reset". After a moment it will want you to restart your computer. Do so and your networking will be repaired! There's no no need to modify anything else on the computer.
      My Computer


  7. Posts : 46
    Windows 10
    Thread Starter
       #67

    topcat7736 said:
    Try this easy fix. In the Cortana search box type 'network status' and hit enter. When the status screen comes up, scroll to the bottom and left click "Network Reset". After a moment it will want you to restart your computer. Do so and your networking will be repaired! There's no no need to modify anything else on the computer.
    I never even knew Windows had that option. :)
    I'd like to know exactly what it does so I'll google it and see if there is more info on this. Thanks for the tip.
      My Computer


  8. Posts : 10,929
    Win10 x64
       #68

    It is easier to find just by opening Settings and typing Network Reset. I just did it and my shares are still working. I had to redo my static IP on my PC but that was easy. No ill effects from it. Hope it might help others. :)
      My Computer


  9. Posts : 68
    Inspiron 530: Windows 7 (64), XPS 8920: Windows 10 (64)
       #69

    I had the two-way mirror, no access syndrome (Home Network over Ethernet). After finally getting my Windows 7 computer (Dell Inspiron 530, purchased in 2009) and my Windows 10 computer (Dell XPS 8920, purchased in 2017) to even see each other, I did manage to get them to actually talk to each other. Thanks to those who helped here with your tips and suggestions.

    For the Windows 7 computer, I had to un-Share and then re-Share most, but not all of my shared directories ("Folders"). A few were still shared on both machines. For the Windows 10 computer, the process was simpler, but still annoying.

    I propose that we coin a new curse word for Microsoft Windows Update. Let us call it "MSWUP" (pronounced mis-wup) for any FUBAR created by an update that is supposed to "Make your Windows Experience easier and more productive".
      My Computer


  10. Posts : 10,929
    Win10 x64
       #70

    noquiexis said:
    I had the two-way mirror, no access syndrome (Home Network over Ethernet). After finally getting my Windows 7 computer (Dell Inspiron 530, purchased in 2009) and my Windows 10 computer (Dell XPS 8920, purchased in 2017) to even see each other, I did manage to get them to actually talk to each other. Thanks to those who helped here with your tips and suggestions.

    For the Windows 7 computer, I had to un-Share and then re-Share most, but not all of my shared directories ("Folders"). A few were still shared on both machines. For the Windows 10 computer, the process was simpler, but still annoying.

    I propose that we coin a new curse word for Microsoft Windows Update. Let us call it "MSWUP" (pronounced mis-wup) for any FUBAR created by an update that is supposed to "Make your Windows Experience easier and more productive".
    I thought removing the shares and re adding them might fix some stuff. Thanks for the information and good that your network is fixed :)
      My Computer


 

  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 18:17.
Find Us




Windows 10 Forums