Windows 10 To Windows 10 Workgroup Over Ethernet Setup

I'm asking this a different way than my struggle with getting Win10 to recognize my old Win7 workgroup a while back. The workgroup is called HOMENET and I've struggled with adding a Win10 machine.

The Network pipe never shows for anything made in Windows 10 to Win 7.
What I did now was just set up two PCs with Windows 10 Pro . The same problem of getting no workgroup installed on the same OS occurs. I've been through everything. There are two many variables to juggle to do this simple task.

I just want to know who has successfully added a workgroup to two Windows 10 PCs.

 

Your answer is in post #5 in your other thread. Just share a folder on one of the Win 10 systems and it will be accessible on the other. Please forget about adding Workgroups to a system, that concept disappeared 20 years ago and is not at all relevant to your problem. The IP settings you gave us earlier are all good and file sharing should be working.

 

I appreciate your patience with me fumbling around with this. So for filesharing what is the equivalent of the Public folder on all Windows PCs which is all I've ever used-- no special naming conventions or anything. And what is the command sequence to make a folder on both PCs?

 

Follow this tutorial and all will be revealed -

https://www.tenforums.com/tutorials/111783-share-files-folders-over-network-windows-10-a.html

 

You may find option 4 the best

 

I'll try anything. Thanks for the lead.

 

As you have been using public folder sharing in the past you might want to follow this method instead

https://pureinfotech.com/public-folder-share-files-windows-10/

 

First off I have seen that advanced file sharing screen repeatedly and did all the settings repeatedly.

Sharing a folder or accessing public on a Win10 machine has appeared inscrutable to more users than just me. I've seen other threads where they are scratching their heads. One of the examples shown shows Homegroup open. Some versions of Win10 don't even have that
anymore. What I'm looking for is someone who has actually done it beyond google searches. It's just wheel- spinning.

What I remember from WinXP or one of those was during _setup_ it asks if this machine will be on a Network and so opens whatever it has to open to allow workgroups over Ethernet etc. Here I've mentioned that I can see a workgroup or public folder but it is empty. And you can't drag anything to it either. In Win10 setting up a workgroup exists as an option. Let's start from that premise for any tips. Is it broken? What's up with it if not.

I've looked at about all the 'permissions screens' to use my own PCs I can stand. And this is a complaint I've seen elsewhere. I'm not the Lone Ranger on it.

I will wee what I can make of finding the Public folder on Win10 (I don't have the HD on all the time).

 

Well I have something going between Win7 and Win10. On the Win10 I made the Documents folder a Share. That seemed to set the path up I normally see. So the Win10 PC shows up on Win7 which it did, but 'empty' as described. I'm not clear on the method yet. What I do know is I'm getting no permissions to drag and drop a video file from desktop Win7-- to the Win10 network.

This is just two PCs on an ethernet cable through the router. No WiFi etc. The connection is
not to go out anywhere just between two setups.

 

I should give this a rest for a while. I just tried to follow one of those wretched You Tube tutorials removing permissions with a tiny mouse pointer jumping all over the screens. I stopped watching it after about 6 different screens were needed jumping back and forth. I cannot stand them.

And I don't know if even what was going on with that would work anyway. There should be one straightforward way to do this. Not 6 or more screens just for personal use.

 

I can't begin to tell you how offensive that comment is! The reason I'm advising specific tutorials is because they are the sites I most trust to provide a full and accurate description of the correct methods. Whatever it is that is not working for you is not because the methods themselves aren't right, it is because your preset ideas are causing you not to follow them accurately.

If we had an ignore feature here you would most certainly be on it. Goodbye!

 

I accept your criticism and spoke in haste.
In fact at one time I spent a lot of time with Sevenforums for Win7.

Things are still unanswered for anyone else joining in: Why is Workgroup available in Win10 if it is unusable?

 

OK, I'll try again. You said "...accessing public on a Win10 machine has appeared inscrutable to more users than just me. I've seen other threads where they are scratching their heads". The answer is C:\Users\Public and it has subfolders already set up for Documents, Pictures etc. This was fully explained in the link I gave you in #7 which you clearly chose not to read, along with much else it seems.

 

Yes, OK thanks for the clarification. I've now read the how to for set up of the users/public.
I'll study that before posing any difficulties.

 

I am going to follow up with the links above. I have a new install of Win10-- different version-- and it seems to be getting data at least from one of my PCs to the other in the next room. But I still need a repeatable procedure. Some of this is still guesswork. So thanks for all the previous info.

[edit] Looking at the pureinfo again that is specifically for Win10 to Win10. My major
problem is Win10 to Win7. I don't want to get going on this again-- just saying that Win7 complicates any of the how to info.

 

Reading through here and you have these 2 computers directly connected over an ethernet cable? No router, switch, nothing?
So you have assigned IP addresses to both? What did you use?
Ok, then you got as far as finding the other PC's shared folder?

 

No, not a direct connect. The PCs go through a plain Uvers router/DSL modem.
No extra switch box or anything..

Yes you are correct in saying I have been able to communicate to the Win10 shared folder with a new Win10 install from a different source. Things are working, just not a good repeatable procedure after all the trying different things suggested.

 

On the computer with the shared folder, open CMD (hit Win+R and type cmd) in that window type whoami, that will give you the computer name\user name. Hopefully you know the password for that user
Goto the other computer and do Win +R and type \\computername\ & enter or OK, you should get a prompt for user name and password. If the dialogue box doesn't have a place for the username and password, look for "More Choices.." and click that. Pput in the username & password of the user of the computer you're connecting to.
If it is successful you'll see an Explorer window with the shares open. If that works and you want amore "permenant solution" open CMD again and type net use X: \\computername\share /PERSISTENT:YES - that will put the share in explorer as a drive with the letter X, so you can use any available drive letter there.

 

https://www.majorgeeks.com/files/details/takeownershippro.html

How does PERSISTENT YES differ from the Takeownership command available in the majorgeeks
TakeOwnershipPro free software (above)? Can there be two 'magic wands' to grant permissions?

I continue to see different commands that sound like they do the same thing.

They talk about take ownership in detail here:

https://theitbros.com/using-takeown-exe-command-to-take-ownership-of-file-or-folder/

 

net use with the persistent switch will 're-map' the 'drive' next time the computer boots up - ie you don't need to run any commands to connect to that share again - it has NOTHING to do with permissions. It will show up in explorer as a drive again & every time you reboot. I just wanted to show how to find and connect to another computer and find shares without using the network browser.

I did not cover anything to do with permissions, I was working from the point of

 

It shows how little I understand, how to say, the language of it.

What I want to do is turn off ever seeing a permissions denied again. The takedown routine seems to offer that. But across two operating systems Win 7 and Win 10? Don't know.

I didn't and still don't understand the 'pre-installed' workgroup called WORKGROUP. I've made a workgroup called HOMENET always. If I had two Win10 setups and used the join workgroup just as-is, would that get me a workgroup with two nodes, PC1 PC2? That's what I'm not getting in these tries with Win10 going to Win 7.

 

"But I still need a repeatable procedure"

I was involved in this thread from the outset but gave up due to the OP's persistent refusal to follow the the standard Windows networking settings and insistence on only using the Public folder. I do not want to get involved again except to say that Map Network Drive entirely answers the OP's issues in both Win 7 and Win 10. To use that feature it is necessary to follow the built-in networking procedure.

 

HERE is an excellent and straightforward tutorial on setting up mapped network drives.

OK it is written for Win 11 but it's essentially the same in Win 7 and later.

 

Why I made a video, easier to see it than read it.

Small part I left out, when mapping the share as a drive you need to supply and user and password
net use x: \\pcname\share /user:Username Password /PERSISTENT:YES
That reconnects without a prompt - no more denied access.

Did I say anything about workgroups? Nope, they just don't matter...see the video.
I connect to a PC's share that is not in my 'workgroup'. Also I show where Win 7 has the local PCs name in the authentication box and how to use the PC you're connecting to credentials.

 

Apologies for going silent on this. I'll re-read it carefully.