Windows 10: 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.

:)

 

Surface Pro 4 can not see other home network computers

My surface pro 4 is part of a home network and can be seen by other computers on the network, but the surface can't see the other computers. Homegroup is setup and works good on all computers on the network. Desktop and surface are windows 10 pro and
my older laptop is 8.1 pro. If the desktop is restarted while the surface is on, the surface will see the desktop, but the desktop will only see the surface not itself under network computers. Once the surface is restarted it no longer see the desktop.
Network discovery is turned on for all computers and all hard drives are shared. What am I missing!!!

 

Upgraded to Build 10586 on Eight Home Networked Computers. Two of the computers are no longer visible on the network

Just one more note on the networking problems in build 10586...

On my one Windows 10 Pro computer in the GARAGE that is on a WiFi connection

to the router in the house....The ONLY PC on my network that can reliably see

the Computer in the GARAGE is my one remaining WINDOWS 7 HOME PC.

It can see the GARAGE Windows 10 PRO computer no problem with 100 percent

reliability. ALL the other computers which are WINDOWS 10 (HOME and PRO) cannot see the

GARAGE computer. And YES they are ALL on the same subnet 192.168.1.xxx

Windows 10 networking DEFINITELY has a problem and yes the

case structure for the name was all changed to upper case and they still can't access it.

 

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

 

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.

 

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.

 

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

 

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.

 

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

 

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

 

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.

 

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

 

Hi there

As Windows is used by almost every conceivable piece of hardware out there and also loads of hardware yet to be even thought about much less actually designed !!! this isn't really an option -- like buying a Car and having a restriction that you can't put any fuel in it.

The Hardware manufacturers usually design their own drivers anyway sometimes with but often without any help from Ms.

Yes I suppose it theoretically could be done but the reality would have a probability of ZERO of this being done.

As far as disabling Linux stuff -- how many people out there are happily using NAS boxes on Windows LAN's -- loads I suspect. Windows doesn't have anything like that yet -- lowish power CPU so low power consumption for "always on box", decent nr of bays for several TB of storage with FAST I/O and data transfer and an optimised file system for serving media and data. Some of these NAS boxes use Intel CPU's but they don't have to so even giants like intel need to tread carefully by restricting OS'es that can run on their chips --and in any case it's always possible for an alternate chip manufacturer to "emulate" a particular CPU and trap the instructions that restrict a specific OS from being used . Can be done in the chip's microcode set.

People might cast their days back to when IBM mainframes ruled the roost -- Amdahl and Hitachi also made mainframes which actually could run the IBM OS'es such as MVS/XA etc simply by code written in the microcode set of the CPU hardware.

Cheers
jimbo

 

Well, I suppose anything is possible in the land of Unicorns and rainbows. The driver error is thrown by M$.
Intel and Lenovo are likely acting per their licensing agreement. You don't have to hold the gun to be responsible for pulling the trigger.

Lenovo Flex 3 Clean Win7 Install - Spiceworks