Question Windows 10 machines on network can't see each other

[Muse]

My laptop has D drive shared. My desktop knows it's there but says I have to contact the server administrator to get permission. What's up with that? What more can I do than set up access and full control to Everyone on the laptop?

 

[JackMDS]

It will very "nice" of you to give some Tech info about the Network involved?

If it regular Home LAN it usually means to get the Control Panel, Network and Sharing Center.

On top left click on Change advanced Sharing and configure the sharing on each computer.

 

[Muse]

It will very "nice" of you to give some Tech info about the Network involved?

If it regular Home LAN it usually means to get the Control Panel, Network and Sharing Center.

On top left click on Change advanced Sharing and configure the sharing on each computer.

Thought I did that. Yes, it's a home LAN. Other computers see each other. This new desktop Win10 doesn't see the others. I just added a network place based on the IP of another machine and it picked up a shared drive/folder and I see it in Explorer but when I access it it says I need my network administrator to allow access to it. Can't fathom what is meant by that. Maybe the problem stems from fact that I use my name as user on other computers but on the new desktop I just have the default Admin account.

 

[Muse]

I also had a devil of a time. I was asked for "network credentials." In the past this meant my user name and Windows logon. But it's not working. Not for the user based on my name or the Admin account, both of which have the same password. Plus, I restarted the desktop in hopes it would sort out the problem and it would NOT accept my usual logon, WTF! After some messing around (not capslock!) it finally let me in... sheesh!

Still, the network credentials were never accepted. I went in and turned off asking for password for sharing between computers, no help! Now, I don't know if I want that on and on which computers!

Also, of course, I don't want my computers accessible by just anyone, just me, just people who sign into my computers, and that just me.

 

[ch33zw1z]

If you use the same username/password across PC's, then the credentials are automatically used

If you're using a different name, then map a network drive and choose login using different credentials.

Also, if you've migrated to a Microsoft cloud type account, the login may be a bit different

 

[VirtualLarry]

I guess, in theory, for "Network Credentials", if you have the same "Username" (Windows Account Name), and "Password", on both machines, it should Just Work.

But the real world is often thornier.

I found that when I log into my NAS, I have to specify the username, as "SERVERNAME\username", which is MS Domain specification for usernames. MACHINENAME\username

Then provide the password, for the account, on the REMOTE machine / NAS.

That works for me.

 

[JackMDS]

But the real world is often thornier.

I found that when I log into my NAS,

My guess would be that the NAS does not use Windows10.

 

[Muse]

I'll sort it out... eventually. One machine sees the others fine, one doesn't. I figure it would have been smarter to create a new account with my usual login credentials instead of sticking with the default Admin account. Now, to do that, guess I'll have to reinstall all my apps. Will see if I can forgo all that and stick with the Admin account first.

 

[Ajay]

Just create a new user with your usual login creds, you don’t need to reinstall your apps. The new user's desktop just won’t have all the shortcuts on it. Let us know how that works.

 

[Rifter]

I had to install SMB 1 as it was not installed by default in win10 to get anonymous file sharing working properly on my network.

 

[Ajay]

I had to install SMB 1 as it was not installed by default in win10 to get anonymous file sharing working properly on my network.

Good catch, I had to do the same thing.

 

[hoorah]

MSFT is continually increasing security in windows 10 as it relates to remote credentials, often 'breaking' file sharing using legacy methods in the process. Sorry I don't have much of a suggestion other than googling the error codes and hope someone has written an article on how to fix it. Several times I've had to modify registry settings to fix file sharing that breaks after a windows update.

 

[Muse]

Just create a new user with your usual login creds, you don’t need to reinstall your apps. The new user's desktop just won’t have all the shortcuts on it. Let us know how that works.

Thanks, I'll give that a try!!!

 

[Muse]

I had to install SMB 1 as it was not installed by default in win10 to get anonymous file sharing working properly on my network.

Never heard of that before. Get it at microsoft.com?

 

[JackMDS]

Never heard of that before. Get it at microsoft.com?

It is to be switched on in Control Panel Programs and Features Turn Windows features On and Off.

 

[Rifter]

It is to be switched on in Control Panel Programs and Features Turn Windows features On and Off.

Exactly, this is how i enabled it.

 

[mxnerd]

Microsoft discourage users turning on 30 years old SMB 1.0 feature, since it's not secure and it's been deprecated. Unless you have old PC running XP/2003.

They instead ask user to start the “Function Discovery Provider Host” and “Function Discovery Resource Publication” services and set them to Automatic (Delayed Start).

https://blogs.technet.microsoft.com/filecab/2016/09/16/stop-using-smb1/

 

[bbhaag]

Thanks for the tip mxnerd. I was having trouble with one of my Win10 machines showing up on my network. I tried the solution you provided and now it shows up. Thank you!