Windows 10: Help - Network Gurus there Can't access W10 machine from another W10

Hi there

Going BONKERS over this (Build 10166)

Two computers on a LAN REDSQUIRREL running W10 PRO X-64 on a physical laptop logged on with a LOCAL account, BLACKDOG running W10 Enterprise X-64 with an Ms account.

1) REDSQUIRREL does not even SEE BLACKDOG. (Redsquirrel with Local account, Blackdog with Ms account)

2) Blackdog throws up enter User name and password -- but won't work even though password is correct.





If I logon with an Ms account on both machines they work fine.

Build 10166 used on Both machines.

( I will have to use Local accounts eventually in any case -- also I can't access my media server (Linux) unless I use a Local account - but I'd still like the system to work properly with Ms accounts too - in order to get the Insider builds).

Cheers
jimbo

:)

 

Connecting to Network Attached Storage

Hi!

Let me clarify The problem child and blind child would be W10. So running join a work group on W10. Most Win OS default to WORKGROUP. But with the home group enabled on 1 computer. I would try to create a new home group on the W10 machine and have all machines
join it. Except NAS. Removing the current home group first.

What is the name of the W10 machine? localhost@9010? if so change the name before you create home group. I know the issue is W10 can not access NAS, But remember the error:

Windows cannot access \\DISKSTATION

Error code: 0x80070035

The network path was not found

The W10 is not really part of the network. So if the W10 creates the Microsoft network, it should then be able to find the network path. The other 2 machine join that network then you should have a local network with access to NAS on all machines.

 

Home Networks or Workgroups connecting W7 W10 systems

More test results:

W7: After creating a Home net group on W10 machine, the W7 machine stated, that there were no Home net group in the system and prompts me to create one. I expected in contrary an order to join one.

W10: After creating from new a Home net group on W7, W10 prompts me to join this one, but ending finally also in a "not found on system"

I removed both Home networks.

W7 explorer shows me the W10 machine, but could´nt access it.

W10 explore showed me the W7 machine, accessable and adding a legitimation for "everybody" on W7 allowed me to open a dataset in the W10 explorer.

Summary:

It was not possible by no means to connect a W10/W7 and a W7/W10 by a Home net group.

By the basic workgroup the W7 explorer showed me the W10 machine, but did´nt allow to acess it, the W10 explorer worked without problems with the W7 machines objects.

 

This type of situation has caused me some problems for quite a while. But you haven't indicated if the computers were set up using a local or Microsoft account, which effects the actual folder designations

So, possibly some observations.

If you use a PIN to sign in, certain systems may not even be seen to allow for a Credentials dialog to be offered.

The user name on a Microsoft system is the entire e-mail address.

And even though you may get an "Unable to Access" error, letting it finish indexing may allow access the second time. Why the system is not set up to give it time to index prior to showing the error message, I don't know.

I have suggested during an install, an option to use a Local Name instead an e-mail address when logging on with a Microsoft account be offered. But so far so such option. And I don't mean an option to install as a Local or Microsoft account, since that is already a possibility. I have been installing mine using a Local Account then switching to a Microsoft Account after the install is completed.