New Windows 10 Insider Preview Fast Build 17751 - August 31 Insider

slicendice · 02 Sep 2018

24c said:

The only thing consistent with this situation is the inconsistency of it all.

Yep! I've had this on/off situation ever since Windows95 and NT3.51. On Linux all this simply just works, and it works in split seconds. I don't understand why Windows is so inconsistent in this matter.

24c · 02 Sep 2018

slicendice said:

Yep! I've had this on/off situation ever since Windows95 and NT3.51. On Linux all this simply just works, and it works in split seconds. I don't understand why Windows is so inconsistent in this matter.

Glad to see I am not alone and I should not expect any remedy in my lifetime.

jimbo45 · 02 Sep 2018

AndreTen said:

Few builds ago MS started to push IPv6. Something about increased security. But there were different symptoms, so have no idea.

Hi there
IPV6 also needs ISP's etc to handle -- where I am that's OK but Ms can't do it on its own. Also if IPV6 used on home networks remember a lot of networked devices such as older TV's computers etc (some of which can't even handle 5Ghz on Wi-fi networks) won't have a clue about IPV6 - so your router will have to handle both protocols.

Cheers
jimbo

swarfega · 02 Sep 2018

IPv6 was introduced with Vista I beleive. But as Jimbo says it requires ISP support

badrobot · 02 Sep 2018

First time I noticed the ninja cat here...

New Windows 10 Insider Preview Fast Build 17751 - August 31-image.png

Looey · 02 Sep 2018

24c said:

Like you, I have 4 machines - Surface and Laptop on latest Win 10 update - ASUS on Skippy - Gigabyte on Fast ring. As seen in the pic, right now are all visible on Network. This is not always the case. I have found by "refreshing the Network" I can, sometimes, get all 4 machines to show up.

I have done this "I have checked services to make sure Function Discovery Resource Publication is set to automatic.", but set to automatic, delayed start, as was suggested here in another thread.

The only thing consistent with this situation is the inconsistency of it all.

Attachment 201943

Thanks for the tip. I tried the automatic, delayed start but I still have the same problem. I formatted a couple of times and installed build 17751.1. The strange thing is after the installation is complete and before the first boot the PC shows up on the network. After the boot it disappears again. Something changes after the first boot. I reported it to Microsoft so I hope they can figure it out but if I'm the only one with the problem something is weird here even though previous build networking was OK. Thanks for the help.

24c · 02 Sep 2018

Looey said:

Thanks for the tip. I tried the automatic, delayed start but I still have the same problem. I formatted a couple of times and installed build 17751.1. The strange thing is after the installation is complete and before the first boot the PC shows up on the network. After the boot it disappears again. Something changes after the first boot. I reported it to Microsoft so I hope they can figure it out but if I'm the only one with the problem something is weird here even though previous build networking was OK. Thanks for the help.

All my machines are "wireless", I wonder if connecting them to router with ethernet cable would make a difference. I couldn't do it with all 4, just curious???

slicendice · 02 Sep 2018

24c said:

All my machines are "wireless", I wonder if connecting them to router with ethernet cable would make a difference. I couldn't do it with all 4, just curious???

The reliability over LAN with static IPs is certainly much better but it still is no guarantee that it will work as it should 100% of the time. The issue is somewhere in the services and Explorer. The signal sometimes just won't get through so all computers will see each other. Connections using IPs or host names works however quite reliably.

jimbo45 · 02 Sep 2018

24c said:

All my machines are "wireless", I wonder if connecting them to router with ethernet cable would make a difference. I couldn't do it with all 4, just curious???

@24c

Hi there

Great way if you have 4 or any number of machine > 1 irrespective of actual Internet speed

1) Get a cheap network 1 Gb/s 4 or 5 port switch only costs a few USD / EUR.

From UK 12 GBP -- got mine less VAT so 10 EUR

NETGEAR GS205-100UKS 5 Port Gigabit Ethernet Desktop Switch: Amazon.co.uk: Computers Accessories

2) connect each computer to switch via ethernet / USB ethernet adapters if your PC's don't have direct ethernet.

3)Connect switch via LAN to router. Only 1 cable needed.

You will be amazed at difference in performance.

I'm not a network guru but I know this works

Also if your switch can't reach the router via LAN then use something like a Netgear Nighthawk extender -- plug the LAN from switch into the Nighthawk extender and the extender can communicate with the Router using both 2.4GHZ and 5 GHZ doubling the throughput -- even if your actual devices can't handle 5GHZ wifi. The switch will handle that side of the stuff.

I'm amazed that there's not more literature on these sorts of switches for simple home users -- we aren't talking server farms here -- typical decent 5 port switch around 12 EUR. Difference in throughput is nothing short of amazing - especially if the original computers can't deal with 5GHZ wifi.

The Nighthawk extender isn't the cheapest but well worth every penny / eurocent etc

Buy NETGEAR Nighthawk EX7000-100UKS WiFi Range Extender - AC 1900, Dual-band | Free Delivery | Currys

got one from UK (fortunately I get VAT back - Iceland is non EU although EEA)

Cheers
jimbo

Ztruker · 02 Sep 2018

From what I can see, it's a Computer Browser problem (as in Computer Browser component of networking, not IE, Edge, Chrome, etc).

The network at the shop has anywhere from 3 to 7 computers, comprised (always) of 2 Windows 10 (1 Pro, 1 Home) computers and 1 to 5 other computers running Vista, Windows 7, 8, 8.1 or 10. The various computers come and go on the network like fireflies. The Vista, 7, 8 and 8.1 computers see each other always and can see the Windows 10 computers sometimes.

There is no identifiable reason why they can see each other one moment and not the next. It's incredibly frustrating that I have to revert to copying files to a flash drive to move them from either of the Windows 10 permanent system to the other systems I'm working with, and ditto moving diagnostic data back to the Windows 10 systems to look for solutions to problems.

I don't understand why Microsoft can't fix this. It's 100% reproducible and should be easy to fix with source code and a debugger.
Are they too busy working on bells and whistles and apps no one wants instead of fixing something like this which is at the absolute heart of networking?