Should I be setting up this network as a domain?

Good Morning

Once again I wish to seek the knowledge of this esteemed group.

I am having fits trying to keep 3 computers, all running windows 10 (one is an Insider Preview), connected in a stable network. I have tried different fixes suggested in other areas of ten forums but nothing seems to keep ALL my computers seeing ALL my other computers. What is the best way to connect three computers ion a small home network?

I have changed the workgroup name. I have cleared and recleared my network settings. I have restarted my router multiple times and many things seem to work for a while then I look again and some computers have dropped out of some networks.

My network is as follows: in a three floor house I have a recently built (but older) windows 10 machine in basement, It is plugged into an Asus router which is fed by my cable modem. Also plugged into the router is a WD My Cloud as well as feeds to the main floor and the upper floor. The Basement W10 machine has a WD My Book and a Seagate 8 TB Drive plugged into it. The main floor feed is connected to a Roku box. The upper floor feed connects to a hub which feeds two windows 10 computers connected with a small "hub".

That's my story.

Should I be setting up this network as a domain? Where should I look in ten forums for help?

Where to next?

As always, your patience and any assistance is deeply appreciated.

cereberus said:

Put them all in a Homegroup?

I started using them homegroup set up years back but found it troublesome and buggy so I have avoided it this time around.

CountMike said:

We need some good networking tutorials. Any network specialists here ?

Thanks, Count. I have tried perusing the forums and I haven't been able to find what I need except for a general agreement that MS networking is somewhat "suspect". I am not looking for someone to blame, just looking for a good "definitive" answer on the best (strongest, least buggy, proper) way to set up a small home network that stays connected in which I can see all the members of the network at any given time.

Again, thank you for your assistance.

CountMike said:

I have some networking problems too. Right now it works better with an old laptop with XP than on another machine with same version of W10. Need an old fashioned peer to peer network. This router/3G/4g modem doesn't have very rich options either.

There seem to be many who have networking "issues". I have a very good router (I think). I have fairly good gear and a half assed mind and I just don't understand why some computers see everyone all of the time others some some of the time and one doesn't see one all the time. Surely there must be a better way than the trial and error approach I have been forced to take. I am sure I am not alone.

CopperCliff said:

I started using them homegroup set up years back but found it troublesome and buggy so I have avoided it this time around.

Homegroup is still tiresome.

CopperCliff said:

Should I be setting up this network as a domain?

No, probably not. You can't put them in a domain unless you set up a Domain controller which for 3 PCs would be overkill. You could try it for free but then you'd have to eventually buy a Windows Server license somehow. Buying a Server license would be difficult to do for a home user and expensive if you could.

There is a tutorial for setting up a domain controller @Kari wrote though if you want to give it a try:
Windows Server 2016 - Setup Local Domain Controller Windows 10 Installation Upgrade Tutorials .

You have to live with networking I think. There are lots of posts on this site saying Windows networking is terrible and much worse than Linux. I've no idea if that is true. I set static IP for everything on my home network and that works just fine just using standard WORKGROUP for me.

There is always a little faffing around deciding whether to put name@outlook.com or \\PC1\name or MicrosoftAccount\name@outlook.com for the user ID but one or other works in the end.

lx07 said:

Homegroup is still tiresome.

No, probably not. You can't put them in a domain unless you set up a Domain controller which for 3 PCs would be overkill. You could try it for free but then you'd have to eventually buy a Windows Server license somehow. Buying a Server license would be difficult to do for a home user and expensive if you could.

There is a tutorial for setting up a domain controller @Kari wrote though if you want to give it a try:
Windows Server 2016 - Setup Local Domain Controller Windows 10 Installation Upgrade Tutorials .

You have to live with networking I think. There are lots of posts on this site saying Windows networking is terrible and much worse than Linux. I've no idea if that is true. I set static IP for everything on my home network and that works just fine just using standard WORKGROUP for me.

There is always a little faffing around deciding whether to put name@outlook.com or \\PC1\name or MicrosoftAccount\name@outlook.com for the user ID but one or other works in the end.

lx07, thank you for the response.

My operating system for the basement computer (essentially a server) was originally Windows Server 2008. I am using that computer/server both wired and wireless. The wireless feeds a Roku box on the top floor which needs to have its IP masked and is a wireless unit only. My VPN would not set up to be shared in this manner so I changed the OS to Windows 10. I may be stuck with this as an OS. My main floor Roku box is wired.

Again, that's my story!

Thank you for taking an interest and responding.

Its weird, when I reset the router sometimes all can see all for a little while and then I check a while later and it has reverted to an earlier state.

Yes, I have set the adapters to not shut off.

There's got to be a way. But it may turn out "the way" is buying a second router just for the upstairs Roku.

Dunno.

Again, thank you.

I have not set up static IPs for my machines. Is there a benefit to this?