| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 149383 | 2020-11-25 22:11:00 | Win10 20H2 networking | bk T (215) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1473201 | 2020-11-30 01:51:00 | 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. |
bk T (215) | ||
| 1473202 | 2020-11-30 03:43:00 | 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. 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 windowsreport.com 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 ;) |
wainuitech (129) | ||
| 1473203 | 2020-11-30 04:12:00 | My PC#2 XYZ is a freshly installed Win10 20H2. Both PCs are Professional. |
bk T (215) | ||
| 1473204 | 2020-11-30 04:16:00 | 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 |
bk T (215) | ||
| 1473205 | 2020-11-30 04:40:00 | My PC#2 XYZ is a freshly installed Win10 20H2. Both PCs are Professional. Great :D that saves a truck load of problems / Options. 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. |
wainuitech (129) | ||
| 1473206 | 2020-11-30 04:58:00 | Great :D that saves a truck load of problems / Options. Lets see where the problem is. From the computer that wont bring up the credential box ---- . Don't quite understand: In my case, PC#1 cannot access PC#2 requires Network Credentials to access. PC#2 can access PC#1 no problem. So. run the sandbox from PC#2 right? |
bk T (215) | ||
| 1473207 | 2020-11-30 05:35:00 | Don't quite understand: In my case, PC#1 cannot access PC#2 requires Network Credentials to access. 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. 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. |
wainuitech (129) | ||
| 1473208 | 2020-11-30 08:15:00 | Problem running Sandbox: 10622 10623 |
bk T (215) | ||
| 1473209 | 2020-11-30 08:24:00 | Problem running Sandbox: 10622 10623Expand hyper-V, the Black Square means not everything is Enabled. Should look like this 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 ---- 10625 |
wainuitech (129) | ||
| 1473210 | 2020-11-30 09:09:00 | 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 |
bk T (215) | ||
| 1 2 3 4 5 6 | |||||