Windows 10: Windows 10 Pro computers can't see themselves in network

Page 1 of 2 12 LastLast
  1.    23 Dec 2015 #1

    Windows 10 Pro computers can't see themselves in network


    I have a 4 computer network with 2 Windows 7 machines and 2 Windows 10 Pro machines. The Win7 computers can see and access all 4 computers through Network. The Win10Pro machines can see and access the Win7 machines. They can't see or access themselves. They can PING each other though through powershell. I've tried disabling firewall and anti-virus and nothing changes.
      My ComputerSystem Spec


  2. Posts : 4,489
    Mac OS High Sierra 10.13.5
       24 Dec 2015 #2

    Is SMB service running, along with the other associated services? How is advanced Sharing setup?
      My ComputerSystem Spec

  3.    24 Dec 2015 #3

    SMB1 and SMB2 running on both machines. Advanced sharing set up as similar threads suggest: private network, network discovery and automatic setup are checked. File and printer sharing are turned on, 128-bit encryption is on, password protected sharing is currently off but it was on before and didn't change anything. I don't currently have any of the machines connected to a home group.
      My ComputerSystem Spec

  4.    24 Dec 2015 #4

    I have same issue.

    If I manually navigate to the shared folder \\computer\folder it works but it is never shown in the network section of file explorer.

    Win7 works fine but Win10 never shows.
      My ComputerSystem Spec


  5. Posts : 138
    Microsoft Windows 10 Pro 64-bit BETA
       24 Dec 2015 #5

    Try switching off SMB2/3;

    sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
    sc.exe config mrxsmb20 start= disabled

    in elevated command

    https://support.microsoft.com/en-us/kb/2696547
      My ComputerSystem Spec

  6.    15 Jan 2016 #6

    Same problem here since I upgraded to Windows 10. I'm finding that I can see all of the other computers on my network (six in total) from one machine, none from another, others can see some machines on the network but not others, and one seems to have a particular problem with a NAS Drive where it can see the drive sometimes but not others! If I manually open a shared drive in Windows Explorer (e.g.\\STORAGE\BACKUP) I can then see the machine on the network through Explorer, but in the case of the NAS, even though it sometimes appears under the Network Places on the left-hand side of Explorer, when I click on it I get a message "Network path not found". I can always access machines on the network from any other machine by using the IP address rather than the other machine's network name. This seems to be a real mess in Windows 10.
      My ComputerSystem Spec

  7.    18 Jan 2016 #7

    mbagshaw said: View Post
    can see the drive sometimes but not others! If I manually open a shared drive in Windows Explorer (e.g.\\STORAGE\BACKUP) I can then see the machine on the network through Explorer.....This seems to be a real mess in Windows 10.
    I can verify this to be the same here. Mixed Win7 - Win10 workgroup with garden variety sharing. Everything normal from the Win7 side - but the Win10 explorer does not see the connection unless manually entered. The problem is evidently not the physical connection, but the Win10 GUI presenting invalid information. This plus the missing protocol bug show Win10 machines not ready for prime time. Just when M$ stops use of Windows 7 & 8.1 on new PCs. There will be blowback.
    With no warning, Microsoft stops use of Windows 7 8.1 on new PCs How dumb is that? | Computerworld
      My ComputerSystem Spec

  •    18 Jan 2016 #8

    DoItJust said: View Post
    Try switching off SMB2/3;

    sc.exe config lanmanworkstation depend= bowser/mrxsmb10/nsi
    sc.exe config mrxsmb20 start= disabled

    in elevated command

    https://support.microsoft.com/en-us/kb/2696547
    Hi there

    This worked on ONE of my W10 computers -- the other one still sits there "In splendid isolation " !!!! It can't even see itself in Windows Networking.

    I think a lot of us agree W10- seems royally hosed up as far as Networking is concerned -- solutions sometimes work and the whole area is very hit and miss.

    I still can't get my W10 computers to see any Linux shares either although the Linux machines can access all the W10 computers without any problem. The only thing the W10 computers see are the media servers running on my Linux boxes (Logitech Media server (aka Squeezebox server), Plex and the mpd (music player daemon) and can work as clients for these servers - i.e they can access and play the mult1-media files provided by the server.

    W7 and XP machines don't have any problem either.

    Update - testing Logitech media server and PLEX on a W7 box -W10 machines can see servers (although not the machines themselves. Testing also with the servers on a W10 box - all W10 boxes can see the servers - but again not the computers or shares.

    I wouldn't believe all the rubbish about latest CPU's not being able to support W7 / W8.1 / W8. I'm not sure how they would even do that -- if these OS'es only use a subset of the new chips instruction set then they will still work. In any case what about "Virtualisation" - I don't really see how they could stop that from working either - to say nothing of the zillions of Linux systems out there - both home users and professional systems such as RED HAT servers.

    They could easily design the OS so W10 wouldn't run in earlier chipsets - that in any case is too late now and would be suicide forcing everybody to upgrade perfectly good hardware.

    Sometimes even in those so called technical mags there's a load of B/S written -- maybe these are a few unemployed FINANCIAL journalists who are having a go at something else.

    (I'm running a perfectly good XP VM system in daily use performing serious work on an i7 machine with the latest Intel CPU -- absolutely ZERO problems !!!!!).

    Cheers
    jimbo
      My ComputerSystem Spec


  • Posts : 4,489
    Mac OS High Sierra 10.13.5
       18 Jan 2016 #9

    Jim you and a lot of us could design a better OS that could run circles around anything out there.

    There are still OS's that are written strictly in Assembly, that are slowly gathering a following from the Raspberry Pi groups. Also those of of that are hanging on 20+ year old laptops that will run a Asm based OS.

    Windows 10 still has a lot of legacy code in it, left over from XP.

    I do like that the reason why Microsoft chose to restrict the use of SMB 1-3, from those who use and Enterprises that rely on Linux Servers and Workstations, was by their statement that it was to disallow "Guest" access, because they felt that was a stop-gap measure to stop hack attempts. It was more like they want to keep people from integrating Linux into their networks, even though everything we use on our networks that is not Windows based, runs on some form of Linux.
      My ComputerSystem Spec

  •    18 Jan 2016 #10

    jimbo45 said: View Post
    I wouldn't believe all the rubbish about latest CPU's not being able to support W7 / W8.1 / W8. I'm not sure how they would even do that -- if these OS'es only use a subset of the new chips instruction set then they will still work.
    Rubbish?? Hardly. It's quite simple, actually - don't supply drivers - and make sure your agreements with vendors prevents users from obtaining them. The Lenovo Flex 3 1580 uses Sklylake. Here is a case in point -

    Laptops and netbooks :: Flex Series :: flex 3 1580 - Lenovo Support (US)
    Lenovo Flex 3 1580 Clean Win7 Install | Windows 7 Forums
    Pre-install drivers for Lenovo Flex 3 1580 clea... | Intel Communities

    The Intel response ir rather telling. (unless, of course, you think Lenovo writes their own code for the Intel chipset). Lenovo support basically offers the unidigit salute. Drivers extracted from the current Lenovo storage driver updates do not function either. Incidentally, Win10 Pro loads perfectly on the same machine.

    Never underestimate the suicidal tendencies of M$ when it comes to control. In the old days, they would call that restraint of trade, but I doubt Eric T. Schneiderman lurks in Win10 Forums.

    ymmv
    Last edited by Tranas; 18 Jan 2016 at 09:58.
      My ComputerSystem Spec


  •  
    Page 1 of 2 12 LastLast

    Related Threads
    Hi, I have a desktop and a laptop setup at home, I have recently upgraded both to Windows 10. Both were previously running Windows 7 Home Premium and could identify each other on the network and I could access files on either PC from one or the...
    Hello I recently upgraded the 3 machines on my home network to windows 10 home. I am having frustrating issues with the network at the moment and would appreciate any help available. Currently when I open up "this PC" and click on network,...
    As the title says. I can reach them by the quick access shortcuts I added before the upgrade but they don't show up in WE Network. Rebooting my WD MyCloud solves the problem until next time I reboot my Win10 c.
    I work for a small company, with a network of 25 users. We have recently replaced 4 of the users with new Intel machines. All of the other machines on the network have retained their ability to print to the network printer after the Windows 10...
    Hi everyone! Just got an ASUS ZenBook UX305 and am having trouble mapping network drives as I can't connect to the devices via explorer (either in the list in Network under "computers" or my manually browsing to the device name or the IP...
    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 19:46.
    Find Us