Setting up the home network has changed in ver 20H2.
How do I get to the Network settings to change the work group name, etc?
I just want to set up a simple home network for my 3 PCs.
It's all different in this version of Windows.
Printable View
Setting up the home network has changed in ver 20H2.
How do I get to the Network settings to change the work group name, etc?
I just want to set up a simple home network for my 3 PCs.
It's all different in this version of Windows.
Go into the old control panel . Its still the best way for many things .
Control panel its still there but MS try & hide it from you . Do a Win10 search for control & you'll see it .
ctrl panel , system, advanced , computor name , change , (workgroup name)
More to it than that , you need to change share setting on the PC you want to access , and older PC's may not be accessible (smb1 issues , its broken since v2004)
Network browsing is a bit broken now , ie browing via the workgroup name . Access the other PC's shares via IP adress .
I go to Control Panel -> System -> No Advance option.
get this:Attachment 10598
Thats not the old control Panel -- As 1101 Posted Got to Search - Type in Control PanelQuote:
Originally Posted by bk T
Attachment 10599
OR From (That Window) Search Type In System Open it, on the right click rename this PC (Advanced) -- On The window that Opens, Click Change and rename the Workgroup to suit.
Attachment 10600
Just adding to 1101's comment. SMB1 is turned off by default and can be turned back on easily enough -- Again from the old control Panel -- programs and features - On the Left Turn Windows features On or Off -- Scroll down and tick SMB1. Sometimes it works other times it doesn't as 1101 points out accessing Via IP is better, could mean you need to set static IP's on all computers instead of DHCP From the router.
Got it. But how do I share a folder?
Before, I just right-click a folder -> Share with ->
Now, I can't find the Share with option to share a folder.
you can turn it on but it wont work properly , 2004 broke it & MS wont be fixing it.Quote:
Originally Posted by wainuitech
Ive had issues with clients with win10 PC's and old servers where mapped drives wont connect & temp lockup if you click them. They had to roll back to previous 10 build till I found a workaround
Same with old NAS's .
Could write it all out but easier to show, This is Via Windows Sandbox Create folder ( or use existing), Right click -->>>>Quote:
Originally Posted by bk T
https://streamable.com/i61w1c
Also shows Opening via the Run Command --- Usually by another PC,(Shown,-- the Sandbox to one of my Servers) but only an example ( or you can map a drive / Create Shortcut) Normally you would have a Computer Name, but this is Via as mentioned Windows Sandbox.
The Video Shows Selecting Everyone has permissions, if you were wanting Only certain Users you can select them as long as they have accounts on the computers- sort of like when accessing Servers. Windows is now using ( for some time) the server style sharings and settings. Obviously on a real server you have a LOT more control/ options with shares.
Windows Sandbox is a TEMP Virtual Machine on Windows 10 pro and above. Not available on Home.
Still got problem:
Both PCs are Win10 ver 20H2 :
PC #1 Computer Name: ABC with a login user name and a password.
PC #2 Computer Name: XYZ with a login user without password.
Both PCs can 'see' each other. but, PC ABC cannot access PC XYZ --- asks for Credential user name and password
XYZ can access ABC without issues.
Windows Security requires Credentials to connect to XYZ. -- Have set up Windows Credential ABC with username and password. saved and restarted.
When I type in the username with blank in the password box (as PC#2 XYE doesn't need a password to log in)
Error: You might not have permission to use this network resource. Contact Administrator .... blank passwords aren't allowed.....
Am I right to say that I will have to assign a password for PC#XYZ in order for the network to work?
If you want to have sharing password required you then need to sign in with a User name and password thats on the computer you are trying to access.
You can still have a different user name and password to sign into the computer without effecting shared folders.
To by pass it completely, two things:
1. Disable password protected sharing in the OLD control Panel.
Open the Control Panel app.
Go to Control Panel\Network and Internet\Network and Sharing Center.
On the left, click on the link Change advanced sharing settings.
On the next page, expand the All Networks section.
Under Password protected sharing, enable the option Turn off password protected sharing.
With Pictures - https://winaero.com/password-protect...ng-windows-10/
2. Make sure your Network Type connection is set to PRIVATE not Public.
Open Start > Settings > Network & Internet, under Network Status, click the Properties Button - Make sure or Select PRIVATE.
BTW -- None of these settings are new, they have been like this for several years.
Good morning, wainuitech.
Followed your instructions closely. still doesn't work. Password protected sharing is turned OFF, set to private .
The moment I put in a password to login to PC#2 XYZ it works straight away. When the password is removed, it cannot be access.
Have tried several times. exactly same results.
Something isn't quite right, somehow.
Have you checked that Password protected Sharing is turned off on BOTH Computers ?
Had that the other day a Business couldn't access one computer, and it wasn't till every PC had it disabled, then they all worked fine.
If both computers have it disabled and its still asking, then have a read through this -- One of them should work https://windowsreport.com/windows-10...ected-sharing/
Some of the settings above may not be available on the Home Edition -I'd have to check. But Found a file the other day that they can be installed - If I can just remember which USB drive its on ;)
Both PCs' Password protected sharing all turned OFF.
Will read through your link and see whether can get it sorted.
Thanks.
some things to try
make a new shared folder & see if that works . You may have NTFS level permission issues
add 'everyone' to share permissions , in both the sharing & security tas
make both PC's : private network connections (not public) , in Win settings,networking
give the PC without a password a login pass (shouldnt need it though)
Dont try & find the shares by browsing the network. That doesnt work properly anymore
instead , start , run , //PCNAME (use the pc name there) . That will show all working shares on that PC . Run that on BOTH PC's & see what pops up
Correction there :) ( gotta be monday ) :pQuote:
Originally Posted by 1101
It should be \\PCNAME
Good morning, guys.
Monday is weird!
Tried 1101's suggestion: start, run \\PCNAME no joy still ask for credential password.
Tried on both PCs with same results.
The weird thins is: my XYZ PC was able to access PC ABC without issues, but now, both PCs cannot access each other, all required Credential password.
Restarted the PCs corrected the above. It's back to the original situation, i.e. \\ABC requires password to access \\XYZ.. but \\XYZ can access \\ABC without issues.
I remember vaguely that one of the Windows 10 Updates broke the networking and the fix was to change 'Function Discovery Resource Publication services' settings to Automatic and restart.
I tried just tried that, but no. doesn't work.
try removing saved network credentials : control panel , credential manager
disabling homegroup service (I think thats no longer a thing in new build of Win10 ?)
try removing the share , then re-add that same share
try making a new shared folder , just as a test.
try this , in a cmd box(run as admin)
net use s: \\pcname\sharefoldername
or
net use s: \\pcname\sharefoldername /user:pcname\username password (or /user:username password)
forum is changing above txt to smilies , so /user : pcname \ username , without spaces in that bit
On both PCs?Quote:
Originally Posted by 1101
Could it be a Win10 ver 20H2 issue?
Any of you guys having similar networking issues?
No Issues here apart from what 1101 Mentioned about the Populating / network browsing. Sometimes it works as it should other times doesn't. But each and every time it does work if you enter the name Via the Run command as shown below:Quote:
Originally Posted by bk T
The computer name as shown in the command: and all shares show.
Attachment 10620
Just a thought --- Are you using a email account on the computers or Local only. If its a email linked signing that will sometimes have a hissy fit regarding passwords regardless of if you use "Everyone" in the share, and give all permissions or not.
The other way around it is to give the Computers login passwords, then when it prompts for details fill them in and tick "Remember My Credentials" and you wont be prompted again.
In The Video I uploaded Post #7 did you do everything exactly and completely as I demoed ? There are two stages to sharing.
wainuitech, I am using local accounts to sign in to both PCs.
I just went through your uploaded video in Post #7 again, followed exactly, one more time. Same results.
Tried many times already that when a password is given to PC#2 XYZ PC #1 ABC can access the it straight away, without asking for passwords. When Password is removed, no way I can access it.
I remember quite a long time ago, when I had this problem, I just add Windows Credential and away it goes. That's many, many years ago.
Thats what should happen.Quote:
Originally Posted by bk T
Bit of a long shot, but open CMD, run as admin, type sfc /scannow Press enter, run it, see if it finds any faults, may require a reboot after.
Cant remember do you have Windows Professional or Home ??
There are a few things you can do, have a look at this page https://windowsreport.com/enter-netw...ls-windows-10/ Some require Windows 10 Professional ( home doesn't have all the settings) and there's one other not mentioned but does require an add-in or Professional.
NOTE: DO NOT download any repair tool -- Its an advert ;)
My PC#2 XYZ is a freshly installed Win10 20H2.
Both PCs are Professional.
Both PCs are using obtain IP addresses automatically. You reckon set it to static IP addresses will help?
Windows 10 is so good nowadays, just don't bother to change the IP address settings. LOL
Great :D that saves a truck load of problems / Options.Quote:
Originally Posted by bk T
Lets see where the problem is.
From the computer that wont bring up the credential box ---- For starters, if you dont have sandbox active - turn it on. ( its the inbuilt Temp Virtual Machine) Open old control Panel - programs and features - Top Left - Turn Windows features on /Off -- When it populates, scroll down to Windows Sandbox, Also locate Hyper-V, while there make sure SMB 1.0 is enabled. Put ticks in the Boxes, you'll need to reboot.
Once it restarts, in Search Type Sandbox Run it. That will be a Temp Version of Windows ( as I did the last video creation) In the SandBox Search type Run type in your Computer address you want to access \\PCName you should get this but with your PCName:
If you dont get the login then its the computer you are trying to access thats the problem.
You dont need a Static IP. Oh, you "may" need to activate Virtualization in the BIOS if they error and wont load.
Don't quite understand: In my case, PC#1 cannot access PC#2 requires Network Credentials to access.Quote:
Originally Posted by wainuitech
PC#2 can access PC#1 no problem.
So. run the sandbox from PC#2 right?
I'd go the other way around, If I got it correct then PC#1 has to enter the Credentials to access BUT if the shares are set to Everyone on PC #2 then you shouldn't need to enter anything. If on the other hand the Credentials window is not popping up then running Via Sandbox should allow straight in.Quote:
Originally Posted by bk T
The key there is what's stopping the log in.
If the Credentials box IS popping up, AND PC #2 has a password to log in simply use the User name and Password it has (this acts like its logging into itself)
The Sandbox is a fresh W10 each time it starts, its only for testing so ANY installs, changes etc are lost when it closes down. Its a Temp install to test programs ( for example) so if everything turns turtle in Sandbox then you don't do it on the main OS. The "ONLY" problem with Sandbox is if you need to reboot it to install a program - Wont work as it deletes everything on restart/shutdown.
Problem running Sandbox:
Attachment 10622
Attachment 10623
Expand hyper-V, the Black Square means not everything is Enabled.Quote:
Originally Posted by bk T
Should look like this
Attachment 10624
As mentioned, depending on the Motherboard "May" also need to be turned on in the BIOS ( most newer Boards last few years are enabled by default - its generally older boards that aren't).
Easy way to check -- Open Task Manager ( Ctrl + Alt + Del) Performance tab ----
Attachment 10625
It shows 'disabled' in Task Manager.
I enabled it in BIOS --- Advance \System Agent Configuration \ VT-d -- changed to enabled
Restarted PC. but Task Manager still showing Disabled.
How do I enable it in BIOS???
My Motherboard is Asus Z97-A
OK. Finally, got it enabled. It's in Advanced, CPU Configuration, Intel Virtualisation Tech
Task Manager shows it's enabled.
Run Sanbox and could access PC #2 XYZ without having to enter Credential password, but still cannot access the shared folder!
What's next should I do?
Can you take a screen shot of the folder you are trying to access and the Error message. Where is the shared folder actually located Eg: in Pictures, C Drive ??Quote:
could access PC #2 XYZ without having to enter Credential password, but still cannot access the shared folder!
You can try the trouble shooter that may actually give the problem.
From Settings - Update & Security - Troubleshoot - Additional Trouble Shooters (Unless Shared folders is displayed) Shared Folders -- Follow Prompts.
Shared folders is Under the Find and fix other Problems.
One weird thought which has been known to cause problems before, make sure the date / time is correct on both Computers.
How do I take a screenshot from Sandbox? After I exited Sandbox, everything is gone! The Shared folder is in D:\Temp Share
I placed both PCs side by side to compare and match the network sharing settings, and they seem to be all OK Can't see anything is not right.??
It all works FINE if a password in put in for logging in to PC#2 XYZ.
Password protected sharing certainly TURNED OFF in Advance sharing settings.
Date and time settings are correct.
Troubleshoot which PC? The one cannot be accessed, i.e. PC#2 XYZ.
Sandbox Error Message:
Network Error
Windows cannot access \\XYZ\Temp Share. Contact your network administrator to request access.
have you checked NTFS share permissions. They are additional to share permissions.Quote:
Originally Posted by bk T
Sometimes NTFS permissions get a bit screwy . Sometimes adding 'everyone' doesnt work .
Have you removed the share to the folder & re-added it ? Reset NTFS permissions ?
Honestly when the share is this bad , you need to start again & work forward from there.
make a new shared folder . Make sure you can read & write to that new shared folder from the other pc.
Then copy 1 (only 1 ) file from the old share to the new shared folder & see if you can open & edit/save that on the other PC (to check that files permissions).
yes. :)Quote:
Originally Posted by bk T
The error message basically means there is a permission Problem somewhere. Its a case of finding it.
If the share permissions are good as 1101 posted then it "should" open and work fine.
Just to show how things should work -- Opened sandbox, ( only because this PC has access already and wont prompt for the user name /password) entered the PCname in the run which opened a shared folder on the test mucking about install in the workshop. I made up a temp account name of General - along with a password - the shares are set to "Everyone", shown in pictures below.
Attachment 10632
Dont forget to put the tick in top left top left picture SHARE THIS FOLDER.
Attachment 10634
And The Video of how it should work. Everything has to be correct otherwise you end up with various troubles, then thats the hard part - Finding the fault.
https://streamable.com/vkzwc7
in WT's pic above ...
go into the security tab.
In security there are separate permissions that also need to be 100% OK
In that security tab is a minefield of headaches if things arnt right , the issue is often in there .
OK. in Sandbox, I could access the PC#2 XYZ but still could not access the shared file holder.
But, in my actual PC, I couldn't even access the PC#2 XYZ
What is wrong here? I can't run my PC in Sandbox all the times. It isn't right.
Well, well, well.
Since this PC has nothing important in there, I wiped everything off and did a fresh reinstall of the latest Win10 ver 20H2
After the installation has completed, I changed the workgroup name to my home network to join my home network setup the network & sharing , etc.. etc...
Restarted the PC in high hope that everything will be OK ... but....
this time, my PC#1 can't even 'see' the newly installed PC#2..... LOL....
Time to give up ????
I had a problem similar to this, worked for days in a fashion that closely resembles what you have tried, gave up and lo and behold weeks later it just started working correctly.
This was between Win 7, Win 10 and a shared folder on a Spark modem usb port.
... behold weeks later it just started working correctly ... Hahaha .... That's the spirit! ...
I am not alone .... :)
Anyway, wainuitech and 1011, thanks for your precious time and efforts in the above. Appreciated very much. :)
Couple of things come to mind -- When installing fresh I never have the Computer connected to the internet Via ethernet, that way once the OS is installed and the cable plugged in a second or so later there's a pop out on the right asking do you want to share / discover other PC's -- For here I click YES. This usually turns on network Discovery, if that's not on nothing will see anything. Being unplugged makes it easier to create a Local account instead of a MS account.Quote:
Originally Posted by bk T
Secondly - on a new install it pays to make a shared folder as again any requirements are turned on or prompted. By Default password protected sharing is ON, that's one of the things I turn off.
Previous comment about Sandbox, that was only to test to see if the computer was actually the problem. Sandbox creates a Virtual Testing Windows OS which all settings disappear when shut down. This is different to a Standard Virtual machine that keeps everything.
You connect the Ethernet cable half-way in between when it says: "Let's connect you to a network, To finish setup, you'll need to connect to the internet" or, wait till everything is finished then plug in the Ethernet cable?Quote:
Originally Posted by wainuitech
Only Connect after its installed fully ( still needs Drivers and to Activate)Quote:
Originally Posted by bk T
So Picture if you can -- Installs -- chug chug chug ;) When it gets to "Let's connect you to a network" Select I don't have internet -- it throws up a couple of warnings about missing out of things, as well as tries several times to get you to connect - it eventually gives up and reboots, tries again - again Select I don't have internet - Then you get the box Who is going to use this PC (enter what ever name you want to use) You can leave the password Blank if you don't want one, then it finishes setting up -- Plug in the Ethernet, the box pops out on the right, similar to this one:
Attachment 10635
Its only there a very short time , a few seconds, If local (one of mine) I click yes, if a customers I click No.
it then goes through the standard activation and downloads of any drivers, updates etc ( which I manually run).
You can replicate the pop out easily enough on an existing machine. Leave the Cable connected.
In Search type in Network Reset, open it - Click on "Reset Now Button", You'll get a prompt - Click YES, it will appear to do nothing for a few seconds, then get a pop up saying it will reboot in 5 minutes. This will totally wipe out your network connection instantly. Once the time warning is showing often I just click start /Restart. When the computer restarts, it will reconstruct the connection and you'll get the pop out again. But as before its not there for long.
It may take a few moments to settle as its rebuilt the connection and needs to reconstruct from the router, and a cmd window open/closes.
This is the easy way to reset a damaged connection.
Read an old article about Win10 & networking, that the 'Function Discovery Resource Publication' has something to do with home networking.
Went to Services to check the settings, found that it's set to Manual. I changed it to Automatic, restarted PC and now PC#2 XYZ shows up but still couldn't get the sharing part to work ...
Anyway. will leave it for now ... hopefully, it will fix by itself as mentioned by Zqwerty ... LOL
Haven't given up totally. Just remember that I have got a laptop (no password to log in to Win 10) to try on.
Set up all the necessary networking sharing bits and pieces, restarted ...
Exactly the same results as summarised, just to share:
1. PC with passwords to login to Windows CANNOT access PCs without passwords to login to Windows; even with Credentials entered in Credential Manager -- meaning that Windows Credential is not working correctly.
2. PCs without passwords to login to Windows CAN access PCs with password but need to enter Credential password. The credentials entered in the Credential Manager doesn't work.
3. PCs without passwords to login to Windows CAN share and access each other (without passwords to login) happily.
4. PCs with passwords to login to Windows CAN share and access each other (with passwords to login) happily.
I think it's a Windows 10 problem with the Credential Manager. I maybe wrong, though.
For the Passwords to work, generally there has to be the account on the PC.Quote:
The credentials entered in the Credential Manager doesn't work
Meaning.
PC 1 user Fred Password = 123456 PC 2 Account Fred should be on PC, Fred Password 123456 = Should work
PC 1 user Fred Password = 123456 PC 2 Account Fred NOT on PC2 --- Generally wont as doesn't have permission. As the Credential Manager doesn't have an account listed to assign permissions to.
Mixing types of permissions usually leads to :waughh:
These are server style setups, has been for several versions of Windows right back to W7 from memory.
Going by the listed descriptions, 3 & 4 are doing exactly what they are meant to be doing.
So really its up to you to decide, have passwords on all Computers or none on all computers ??
You'll find since pass worded PC's can access then its the security. Non pass worded are open slaver. (not generally a problem in a home network setup- unless someone's hiding something).- It happens.
Any demos I have given have Always been to Actual Servers and I know what's shared and what's not to whom, Actual servers have a LOT more control over what anyone can have access to.
Why do you think I used "Administrator" in the Demo Logins. :D
On Saying all that, NONE of the computers I have here are MS Account Signed in, any that do have passwords they are all to Local Servers.
Ive just seen that problem on a NEW Win10 laptop.
Despite setting networking for no passwords ,and permissions to 'everyone' , I had the popup requiring a login/password for the shared folder . Share access worked OK once the login name(only) was entered into that popup box (was no login pass) .
No wonder all the suggested fixes didnt help. Its a bug .
Reported