Charlie Hoffpauir wrote:
On Tue, 25 Sep 2018 23:32:33 -0400, Paul
wrote:
Charlie Hoffpauir wrote:
I'm having an awful time trying to get my simple home network working
between all my computers, since the elimination of Workgroups in Win
10. Basically, I have three desktops, mine, my wife's, and one that's
acts as a file server for backups. In additiona there are three
portables of various ages, but all running either Win 10 home or pro.
My desktop can see the files on any of the computers. My Thinkpad can
see my desktops files, but not those on my wife's computer, or the
file server that I want to use for backups. Is there any writeup
somewhere that explains how to set these computers up so that each one
can see the files on the other computers?
Are multiple cascaded routers involved ?
Some networking setups you can easily build at
home, cause all the computers to be able to see
the Internet, but some of the computers cannot
communicate with the other computers. You are fooled
by all your working web browsers, into thinking
there is nothing wrong with your networking setup.
*******
On each computer, you can use
ipconfig
and get the network address of each computer
right now.
Then, you can use "ping tests".
192.168.1.2 192.168.1.3
| |
---+--------+-------------+--
|
|
192.168.1.4
In that example, node "2" could try
ping 192.168.1.3
ping 192.168.1.4
and verify that the other computers are "reachable".
Node "4" could try
ping 192.168.1.2
ping 192.168.1.3
And so on.
That's to verify they can actually see one another.
There is also the topic of subnets and netmasks.
But you have to start somewhere.
Even being able to draw us a picture with some IP
addresses doodled on it, is a start.
Paul
Thanks for the comments. I didn't give enough information, I realize,
cause I was looking for a link to some write-up to read over. However,
I do have some details that I didn't mention.
1. In some cases, I can "see" the other computer(s) from a computer
(say from my Thinkpad) but when trying to access drives on the remote,
I get a message I don't have permission to see the files. File sharing
for everyone is set up on the remote, and indeed I can see all the
drives and files and access them from my desktop computer.
2. The network is "new" in the sense that it's now using AT&T Fixed
Wireless to access the internet, and using their router. The router is
a multipurpose device that looks like they use for fixed wireless and
for other services like DSL. All the devices in my home are connected
either to the router directly via cat 5A or to a 8 port switch, or
wirelessly via WiFi. I uploaded a printout (PDF file)of all the
connections to my OneDrive. Link to it is:
https://1drv.ms/b/s!AtjEABxG0hlciiFCJVMuDI9vuVgX
If you look at the list, there are a couple of items that I can't
really identify. The one labeled Unknown might be my Ubiquity access
point, which is wired from the 8-port switch.
Also I noted that some of the devices which actually connect via a
WiFi adapter, like my wife's computer which is temporarily relocated
and can't be connected via ethernet cable, is listed as connected via
ethernet. I think this is because it connects via the Ubiquity AP,
which is connected to the router via cable.
Thanks for your comments.
I converted your PDF into some hen-scrawl of my own.
GB_Desktop 192.168.1.65 * sees all
SuperJoey-MoCA 192.168.1.67
Hopper2-br 192.168.1.68
? 192.168.1.66
Fox (serve) 192.168.1.79 * (running IPV6)
fe80::7d7b:d30b:2df4:c95e
? 192.168.1.69
Android 192.168.1.70
Wife 192.168.1.72 *
fe80::5da5:b0c6:513c:ccfe
X SAMSUNG-SM-G930A 192.168.1.64
X Matebook 192.168.1.73 Portable
SAMSUNG-SM-G930A 192.168.1.75
fe80::ae5f:3eff:fe69:a993
SAMSUNG-SM-G930A 192.168.1.74
fe80::ae5f:3eff:fe9f:a752
X LAPTOP Thinkpad 192.168.1.76 Wifi Portable Can't see IPV6 Wife or IPV6 Fox
Galaxy-Tab-S2 192.168.1.77
fe80::b674:43ff:fe30:809d
X ROKU 192.168.1.78 Wifi
viziocastdisplay192.168.1.80
fe80::a68d:3bff:fe34:14f6
1 Portable missing from list ???
*******
IPV6 used to be a requirement of HomeGroups.
HomeGroups are deprecated in 17134.
Yet, a number of services used by HomeGroups
are still present. Something with a name like
"Function Discovery" or the like, might be one of
them.
Apparently, while IPV4 has NetBIOS (the workhorse),
one of those seven services for HomeGroup is the
IPV6 equivalent of a resource enumerator.
But that doesn't really explain your symptoms, because
your description suggests you're not having a problem
"seeing" the device, merely a problem getting in.
The standard advice for these situations is to do
\\192.168.1.79\FamilyTree
to get to a particular volume on Fox, instead of
doing symbolic access as in
\\Fox\FamilyTree
So you can attempt to contact the server (i.e. one
of your cases that does not work) and get the job
done that way.
As for fixing it properly, you'd research what the
seven services are that HomeGroups used to use,
and two of them (with perhaps Function in the name),
might play some part in Discovery of the things via
their IPV6 address.
I would hope that the OS is not set up to prioritize
one addressing scheme over the other, but such a thing
happening is probably inevitable. It could be that the
IPV6 machines lean on IPV6 first, and if their
Function Discovery thingy is missing, then the
\\Fox\FamilyTree
remains broken.
Maybe someone who has a handy list of the services to
check, could post them for you.
Plugging in some breadcrumbs from the above gets me...
https://technet.microsoft.com/pt-pt/...(v=ws.10).aspx
"NetBIOS over IPv6 is not supported. Therefore, NetBIOS name
resolution techniques cannot be used to resolve names to IPv6 addresses."
Neighbor discovery is necessary in IPV6, because you have 4 billion
link local addresses available on your own LAN. And unlike a
subnet with only 255 nodes, it's a little difficult to use a
primitive brute force search to find the other machines. A
more intelligent method is needed when a node wakes up.
Now, this article is getting a bit closer, except it is doing
the *negative* of what you want. It's disabling discovery.
But at least it has some names you can check in services.msc.
https://blogs.technet.microsoft.com/...ork-resources/
# Function Discovery Resource Publication
# Function Discovery Provider host
# SSDP
Now, SSDP was a useful one back in Win7 days. It's sole
purpose back then, was to draw that network map in the
Network control center panel. It didn't seem to do anything
else at the time. But still, it's something you can check
to see if its running on the ThinkPad (which I believe is
your flaky node).
Paul