If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Home Group
Fiddled with stuff and got a few homegroup PCs to show up BUT. But the names are NOT the PC names as in everything else but look like the User Names. Why ? What if I make all the user names the same as this would be legal. How do I make the PC names show up rather than user names. Anyway, aren't all users commmon in a homegroup or do I have to now worry who is logged on at a particular PC ? This is HOME Win 10 and it acts like ALIEN W10 from outer space. Another reason Win10 was NOT named Win 9 since it was to be; plan Win 9 from outer space was already taken. Come on MS make an OS for the home user EASIER ! NOT HARDER ! |
Ads |
#2
|
|||
|
|||
Home Group
I had to go through a different newsgroup provider but the just posted
previous post below this one went through no problem on the other newsgroup provider. Let's go back to teletype or better , morse code. More reliable ! |
#3
|
|||
|
|||
Home Group
|
#4
|
|||
|
|||
Home Group
FreeUser wrote:
Fiddled with stuff and got a few homegroup PCs to show up BUT. But the names are NOT the PC names as in everything else but look like the User Names. Why ? What if I make all the user names the same as this would be legal. How do I make the PC names show up rather than user names. Anyway, aren't all users commmon in a homegroup or do I have to now worry who is logged on at a particular PC ? This is HOME Win 10 and it acts like ALIEN W10 from outer space. Another reason Win10 was NOT named Win 9 since it was to be; plan Win 9 from outer space was already taken. Come on MS make an OS for the home user EASIER ! NOT HARDER ! I did a test here. I set up three virtual machines. Windows 7 Windows 7 Windows 10 I set up a Homegroup, between the two Windows 7 machines. Took no time at all. Then, I tried to get Win10 to join the HomeGroup. It resisted every effort. Gave the excuse about the time clocks might be too far apart. Claimed there was "No Internet". Kept losing the private network setting. You name it, Win10 did it. Windows 10 just seems to have too many dependencies, for HomeGroup to work for every person who tries to set it up. That's all I can figure. I used VirtualBox for the test. I isolated the VMs from my regular LAN by using the "Internal Network" setting, and had to turn on VBoxManage DHCP. Still didn't help. HomeGroup seemed to want a working DNS, and even with some hosts file entries, still wasn't happy. My guess, is it wanted to communicate with Microsoft for some reason. The File Sharing on the other hand (common Workgroup setting, three different user accounts on the machines), that worked fine and without a lot of kicking and screaming. I think the next time I need this, I'll just stick with File Sharing. I have no way to effectively emulate your NAS. It would not be easy to get any sort of technical information on what SMB features are actually implemented. The NAS should have some setting for WorkGroup, and it would be a good idea to match that on the three computers. If you do manage to connect the Win10 machine to the NAS, you can try the PowerShell commandlet Get-SMBConnection to get details about the connection, and what flavor of SMB it is using (1, 2, or 3). I don't know of a way to query a remote device and see what protocols it nominally supports. Paul |
Thread Tools | |
Display Modes | Rate This Thread |
|
|