Windows 10: cannot see non_windows machines

I cannot see my NAS running FreeBSD. I have a SAMBA share configured. I read the article from Tech support saying I have to use a password account, not a PIN account.

Yes they are on the same net and subnet.

I can ping all devices with no problems but the NAS does not show up in Network Neighborhood.

Yes my other Windows system does show up, and my DirecTV mediaserver, Network Printer, TV display etc.

From a browser I can log into to the web admin page on the NAS and configure it.


Where do I go from here?

:)

 

Can't write to shares on a Windows 10 machine from a Windows 7 machine

I still get "You need permission to perform this action" from the Windows 7 machines if I try to write to a Windows 10 share after I made the above changes on the Windows 10 machine.

 

how do I get machine id for activation purposes?

Hi Fred,

Machine ID also known as Product ID is being used to identify the device. We suggest following the steps below to get the product ID of your device:

• Type about your PC on the search box.
• Look for the Product ID.

Get back to us if you need further assistance.

 

Clean install of W10 not possible in Virtual Machine.


Please get a cup of coffee, lean back and think an answer for these two questions. Take your time, then check the answers below the questions:

Questions:

1. If you do a clean install of let's say Windows 10 Insider Build 10525 on a totally new computer which has never had an activated Windows 10 on it, does it activate?
2. If you do a clean install of Windows 10 Insider Build on a computer where the underlying Windows 10, upgraded from a qualifying old operating system has already been activated, does it activate?

Answers:

1. No, of course not.
2. Yes, of course.

Why do you think that a virtual machine would make any difference? You have tried to install Windows 10 on a totally new machine which has never had an activated Windows 10 installed, therefore the Microsoft activation servers block the activation due invalid machine ID. In the highlighted part in below quote you admit your mistake yourself, plain and simple, yet you when doing this wrong draw conclusion that even if done correctly it would not work:

What you have tried is essentially the same as if you took a brand new real physical PC without any operating system, which has never had any operating system, and then installed Windows 10 Insider Preview wondering why it does not activate! Virtual Machines behave exactly the same way; if you want to clean install Windows 10 Insider Preview and get it activated you must do it on an existing virtual machine, one which has already had an upgraded Windows 10 activated. This "computer", the virtual machine, its machine ID is marked on activation servers as valid and activated and it will of course activate.

Be it a virtual machine or a physical computer, you cannot activate a clean installed Windows 10 Insider Preview on a totally new machine. How difficult can this be to understand?

When clean installing Windows 10 Insider Preview on a computer which has already had a previous Windows 10 Insider activated, you do not use the product key! It will be asked twice, once before the installation starts and once after the last reboot to OOBE phase. In both cases you skip the product key and your Windows will be automatically activated.