Help! Windows 10 Peer to Peer

[red12049]

So... Windows Server 2012 Standard, two Windows 10 Home machines. "Server" is being used only in a P2P role, hosting data.

Had some WIN 7 Home Premium machine on the network originally, no problem accessing and sharing files.

Hooked new WIN 10 machines, set to no password, file and printer sharing on, lower security (48?). Can see shared folders, but not allowed to access them. I've done this a lot, and have no idea what I'm doing wrong this time.

All machines are Dells, not that that should matter in this case.

Any and all assistance greatly appreciated. Thanks in advance.

Rick

 

[dopangle]

So... Windows Server 2012 Standard, two Windows 10 Home machines. "Server" is being used only in a P2P role, hosting data.

Had some WIN 7 Home Premium machine on the network originally, no problem accessing and sharing files.

Hooked new WIN 10 machines, set to no password, file and printer sharing on, lower security (48?). Can see shared folders, but not allowed to access them. I've done this a lot, and have no idea what I'm doing wrong this time.

All machines are Dells, not that that should matter in this case.

Any and all assistance greatly appreciated. Thanks in advance.

Rick

Upgrade to Windows 10 Pro
http://answers.microsoft.com/en-us/...home-and/55338b22-d042-45cb-b9c9-a1be21b534e1

 

[Diggs]

I've seen this also. User-Public should be accessible for shares on C: drive but I am sharing D: drive. I not only had to set the drive to sharing for everyone, but each top level folder in D: drive also had to be shared. After that, all the sub folders were accessible also on the network.
You can hack the registry(?) and turn back on administrative shares like the days of old, but not a very secure way to go about sharing.

 

[red12049]

Upgrade to Windows 10 Pro
http://answers.microsoft.com/en-us/...home-and/55338b22-d042-45cb-b9c9-a1be21b534e1

If you're referring to joining a Domain, that's not the issue here. Network is P2P. Is there something else there I'm missing?

Rick

 

[ell]

So... Windows Server 2012 Standard, two Windows 10 Home machines. "Server" is being used only in a P2P role, hosting data.

Had some WIN 7 Home Premium machine on the network originally, no problem accessing and sharing files.

Hooked new WIN 10 machines, set to no password, file and printer sharing on, lower security (48?). Can see shared folders, but not allowed to access them. I've done this a lot, and have no idea what I'm doing wrong this time.

All machines are Dells, not that that should matter in this case.

Any and all assistance greatly appreciated. Thanks in advance.

Rick

did you see my post? https://www.technibble.com/forums/t...to-share-a-single-file-on-home-network.68046/

 

[Metanis]

I'm asking these questions based on the assumption you haven't created a Domain even though you are using Server 2012.

1. On the Server machine, have you set your Share permissions to Everyone Read/Write?
2. Also on the Server, have you ensured your valid Server user has Full Control in NTFS permissions?
3. Are you using a valid Server user and associated password to connect to the share from the Win10 machines? (machinename\username format)

 

[red12049]

I'm asking these questions based on the assumption you haven't created a Domain even though you are using Server 2012.

1. On the Server machine, have you set your Share permissions to Everyone Read/Write?
2. Also on the Server, have you ensured your valid Server user has Full Control in NTFS permissions?
3. Are you using a valid Server user and associated password to connect to the share from the Win10 machines? (machinename\username format)

No domain.
No login set up, prefer not to have to. Has WIN 10 changed something that would require that? The WIN 7 boxes that are being replaced didn't need that.

Thanks for the assist.

Rick

 

[red12049]

did you see my post? https://www.technibble.com/forums/t...to-share-a-single-file-on-home-network.68046/

I did. Thanks, but not quite the same situation. I''ll keep monitoring your thread as well.

Rick

 

[Markverhyden]

Are you sure that you can do this without passwords on the workstations. I thought that passwords were enforced, including complexity, out of the box.

 

[Diggs]

Are you sure that you can do this without passwords on the workstations. I thought that passwords were enforced, including complexity, out of the box.

Our network runs with no passwords required for sharing anything in C:\User\Public\ using Win10 machines but so far I can only get sporadic sharing from D:\ and can't explain why it's a hit or miss thing.....

 

[Markverhyden]

Our network runs with no passwords required for sharing anything in C:\User\Public\ using Win10 machines but so far I can only get sporadic sharing from D:\ and can't explain why it's a hit or miss thing.....

I know it sounds like I'm being nit picky but do you have your own thread for this? I've seen you make a few comments about this and having it's own thread will help a lot. Nothing personal.

 

[Diggs]

I'm sharing information very close to the same thing he is going through and can share locally files on Win10 machines as I've expressed. I don't see that you have sharing experience peer-to-peer locally on Win10 machines or you wouldn't be asking about passwords.....

Sorry if I offended....

 

[Markverhyden]

Sorry if I offended....

You did not offend me. I'm just pointing out the obvious, want answers to your questions post them separately.

 

[Metanis]

This may have some bearing on the issue?

http://www.howtogeek.com/126214/how-to-create-network-file-shares-with-no-passwords-in-windows-8/

 

[red12049]

This may have some bearing on the issue?

http://www.howtogeek.com/126214/how-to-create-network-file-shares-with-no-passwords-in-windows-8/

Already done, but thanks.

Rick

 

[Markverhyden]

No domain.
No login set up, prefer not to have to. Has WIN 10 changed something that would require that? The WIN 7 boxes that are being replaced didn't need that.

Thanks for the assist.

Rick

Personally I do not believe in doing anything without credentials, but that is another discussion. As we all know, we have to make our customers happy. I remember reading articles recently, can't call them up, where M$ has been tightening up security, including credentials. Why not just create everything with a single set of credentials. As I'm sure you know you can save credentials on workstations. So just create a account on the server and use those credentials to map the share on the server.

 

[red12049]

Personally I do not believe in doing anything without credentials, but that is another discussion. As we all know, we have to make our customers happy. I remember reading articles recently, can't call them up, where M$ has been tightening up security, including credentials. Why not just create everything with a single set of credentials. As I'm sure you know you can save credentials on workstations. So just create a account on the server and use those credentials to map the share on the server.

Looking like I'm going to have to do something like that, but I'd still like to know why. Thanks.

Rick

 

[Metanis]

Personally I do not believe in doing anything without credentials, but that is another discussion. As we all know, we have to make our customers happy. I remember reading articles recently, can't call them up, where M$ has been tightening up security, including credentials. Why not just create everything with a single set of credentials. As I'm sure you know you can save credentials on workstations. So just create a account on the server and use those credentials to map the share on the server.

Good call.

Sounds like the customer doesn't need a server, just a NAS device with no security enabled at all. Server 2012 seems like an expensive amount of overkill here.

I just setup a small p2p at an accounting office using all Win10 home machines. The most powerful machine is the server. Called Server. It has a traditional shared folder c:\shared called Shared. That machine has an administrative user defined as XYZ with a password of 123. All the other machines map a drive to the \\Server\Shared folder and they use the alternate credentials of "server\xyz" as the username with the password of 123 to connect and map to that drive. My customer has simple instructions on using File Explorer to re-map the drive if it ever becomes disconnected. Works like a champ using all the traditional Microsoft file-sharing methods and tools.

 

[Pacific Blue IT]

Did you change the security permissions to everyone?

 

[red12049]

Good call.

Sounds like the customer doesn't need a server, just a NAS device with no security enabled at all. Server 2012 seems like an expensive amount of overkill here.

I just setup a small p2p at an accounting office using all Win10 home machines. The most powerful machine is the server. Called Server. It has a traditional shared folder c:\shared called Shared. That machine has an administrative user defined as XYZ with a password of 123. All the other machines map a drive to the \\Server\Shared folder and they use the alternate credentials of "server\xyz" as the username with the password of 123 to connect and map to that drive. My customer has simple instructions on using File Explorer to re-map the drive if it ever becomes disconnected. Works like a champ using all the traditional Microsoft file-sharing methods and tools.

You're correct, they don't need a server, but a NAS won't work (QuickBooks, Drake). Server was already in place and working flawlessly with WIN7 workstations. They replaced the old workstations with WIN10 stations. It is an accounting firm.

Rick