memo09, OldNavyGuy:
Thanks for the quick replies! Restarting this service on one or both laptops didn't do anything. It seems that the batch file would be a nice automated way of doing this, but it didn't seem to have any effect whatsoever.
Again, I am stumped!!
You were given an automated way to fix the issue.
Try it.
Also check that these settings are correct on all systems -
In Network and Sharing Center -
Private profile -
Turn on Network Discovery
Turn on File and Printer Sharing
Guest or Public -
Everything turned off
All networks -
Turn off Public Folder Sharing
Turn on 128-bit Encryption
Hey OldNavyGuy,
Thanks again for the ideas.
I created the batch file, created a task to run it at startup, and made sure both laptops on my network had the same batch file/schedule. Zippo.
Then I modified my Network Sharing settings to your suggestions. Still zippo.
Bummer!
Maybe I should go back to the drawing board and set everything up from scratch again.
Did you check that the task ran successfully?
No, not yet.
More importantly, I thought the other laptop was updated to the latest Win10 update - it's not, but it's on it's way now. I need to get both at the same version and try again. How did I miss this?
Here's hoping!
I'll definitely make sure the tasks are running properly on both machines.
They don't need to be on the same version.
I personally would not recommend going to Windows 10 2004 at this time. There are several issues with it currently.
I would suggest reading the list of Known Issues.
https://docs.microsoft.com/en-us/win...indows-10-2004
There is also a currently running thread here on Windows 10 2004 issues -
Known and Resolved issues for Windows 10 May 2020 Update version 2004
However, you have 10 days from the time you install it to roll back to your previous version.
Good to know. The update is underway - hoping for the best.
I'll be getting back to this network problem tomorrow.
I really appreciate your help so far! Thanks!
Hi folks
@billyjk
Not a scientific answer so any network gurus out there can if they want tell me OK this is JUNK but I've found that it generally works --why or how I don't know -- as far as Windows Networking is concerned - I'd rather believe in Gandalf the Wizard's stuff in The Lord of the Rings than any explanation from Ms itself. !!
sometimes the only way to get this stuff working again is to totally switch off EVERYTHING that's connected to your network -- including any wifi extenders, smart phones, tablets, TV's, SKY Q and other satellite boxes etc etc and to switch off the router. Then leave everything for 10 mins -- switch on the router again and after it's connected to the Internet (on most cable / fibre systems there will be a green connect led on the cable box - might be blue depending on the cable box).
Now switch on computers and other equipment test each one first before switching on other things -- do the phones last !!!
sometimes - especially with DHCP your phone might get allocated an IP address that a computer WAS using before it was switched off and on re-start it can't get an IP address. Also ensure the "lease time" in the router is set to a long interval -- the default on a lot of routers is 24 hours so after 24 hours that IP address can be re-allocated.
To get into the router maintenance screens use address of the form 192.168.x.x or 10.10.x.x depending on your network -- even if using IPV6 the router should still be "logabble into" with the standard IPV4 addresses for home / private networks.
Windows has had networking problems for as far back as I can remember -- Windows 3.11 for workgroups was the first version of Windows I used.
I am STILL having connection problems with the new "insider" or DEV builds -- the most recent for me with networking functioning correctly are builds 329 and 331 (330 failed as do all the newer "pre-release" things).
Funny though W7 doesn't have this problem !!!
@OldNavyGuy
remember if the OP images his system (with say free macrium) then he can restore at any time -- and the 10 day limit isn't then applicable. People should always backup their systems before doing any updates or making signicant changes.
Cheers
jimbo
Quote