Transfer files?

I have two Win 10 computers on my home network. One (call it "1") is
connected the router with an ethernet cable, the other (vall it "2") by
WiFi.

On 1,Â* I open File Explorer This PC Network. None of the computers
on this network are displayed.

On the other, it lists two computers -- itself (2) and the other (1).Â*
But when I click on the 1 icon, I get "This folder is empty"

WhatÂ* do I have to do to access the files of one from the other?

Thanks.

Alek wrote:
I have two Win 10 computers on my home network. One (call it "1") is
connected the router with an ethernet cable, the other (vall it "2") by
WiFi.

On 1, I open File Explorer This PC Network. None of the computers
on this network are displayed.

On the other, it lists two computers -- itself (2) and the other (1).
But when I click on the 1 icon, I get "This folder is empty"

What do I have to do to access the files of one from the other?

Thanks.

If you find a Tutorial, some of those are quite thorough, and
try to head off trouble before you get there. If you've accidentally
misconfigured something, the Tutorial can give hints on what items to
look for.

https://www.tenforums.com/tutorials/...dows-10-a.html

Control Panels can be found by running

control.exe or just control

in the Run box

The System control panel (once control panels are running), allows
specifying membership in a Workgroup. If the machines share the
same Workgroup value, then they can share. The workgroup declaration,
takes the place of "Domains" at work, where a domain server and some
client machines form a kind of "computer club". Well, at home, you
need to fake some of that stuff, and declaring a Workgroup manually
on each machine, is a replacement for some of the infrastructure
you might have at work.

To scan a network for "foreign" computers, you can try

http://www.unixwiz.net/tools/nbtscan.html

L:\nbtscan.exe 192.168.2.0/24 # scan 256 addresses on subnet 2

192.168.2.104 WORKGROUP\BOB SHARING
192.168.2.109 WORKGROUP\ZBOX SHARING
192.168.2.125 HOMEGROUP\WENDY SHARING

By walking over to the third machine and changing the
group name (then, reboot), all three machines can belong
to the same club.

*******

Unrelated to your question, you can use this in Linux

smb://192.168.7.23/mydisk

or from a mindless file explorer like Nemo, you could do this
because nemo lacks a GUI for entering file share details

nemo smb://192.168.7.23/mydisk # immediate prompt for uname/pw

The usage of IP addresses like that, takes the place of computer
names like \\bob\mydisk . In cases where the nameserving portion
of networking is broken (or insecure and turned off), you resort
to other means to hack a working solution.

While it would be nice to use \\bob to find the server,
beggars can be choosers, and IP addresses work when the symbolic
names are broken.

Paul

On 1/29/20 5:47 PM, this is what Paul wrote:
WhileÂ*itÂ*wouldÂ*beÂ*niceÂ*toÂ*useÂ*\\bobÂ*toÂ*fi ndÂ*theÂ*server,
beggarsÂ*canÂ*beÂ*choosers,Â*andÂ*IPÂ*addressesÂ*w orkÂ*whenÂ*theÂ*symbolic
namesÂ*areÂ*broken.
And you have static IP.s
If not you're up a creek.

Big Al wrote:
On 1/29/20 5:47 PM, this is what Paul wrote:
While it would be nice to use \\bob to find the server,
beggars can be choosers, and IP addresses work when the symbolic
names are broken.
And you have static IP.s
If not you're up a creek.


DHCP in the house isn't that bad.

\\bob is usually where I left him.

If I fire up one of the old machines, that
usually gets one of the less used, higher addresses.

Static addresses smacks of "organization" :-)

Paul

On Wed, 29 Jan 2020 17:58:14 -0500, Big Al wrote:

On 1/29/20 5:47 PM, this is what Paul wrote:
While*it*would*be*nice*to*use*\\bob*to*find*the*se rver,
beggars*can*be*choosers,*and*IP*addresses*work*whe n*the*symbolic
names*are*broken.
And you have static IP.s
If not you're up a creek.

Not really. I think this is about file sharing at someone's home, so
presumably the owner has physical access to each of the PCs, and/or access
to the router's DHCP table. Static IPs make things easier, but not having
them shouldn't be a show stopper.

If you find a Tutorial, some of those are quite thorough, and
try to head off trouble before you get there. If you've accidentally
misconfigured something, the Tutorial can give hints on what items to
look for.

https://www.tenforums.com/tutorials/...dows-10-a.html

On this past weekend I set up a new home network with 1 W7 machine and 2 W10
machines. Was having the same issue as well and searched to exhaustion with no
resolve so thought I'd post a Q here asking what to do. Saw this thread and
read your post, followed your link, and now all is working as it should.

Thank you! Thank you! Thank you!

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

On 30/01/2020 00:35, Char Jackson wrote:
On Wed, 29 Jan 2020 17:58:14 -0500, Big Al wrote:

On 1/29/20 5:47 PM, this is what Paul wrote:
WhileÂ*itÂ*wouldÂ*beÂ*niceÂ*toÂ*useÂ*\\bobÂ*toÂ*fi ndÂ*theÂ*server,
beggarsÂ*canÂ*beÂ*choosers,Â*andÂ*IPÂ*addressesÂ*w orkÂ*whenÂ*theÂ*symbolic
namesÂ*areÂ*broken.
And you have static IP.s
If not you're up a creek.

Not really. I think this is about file sharing at someone's home, so
presumably the owner has physical access to each of the PCs, and/or access
to the router's DHCP table. Static IPs make things easier, but not having
them shouldn't be a show stopper.

Al means static IPs within your own home network. It may not be strictly
necessary as most routers' DHCP allocation is semi-static anyway as
there's little demand for IPs. Static IPs do avoid head scratching
moments, when you most don't need them.

On Thu, 30 Jan 2020 12:08:08 +0000, Chris wrote:

On 30/01/2020 00:35, Char Jackson wrote:
On Wed, 29 Jan 2020 17:58:14 -0500, Big Al wrote:

On 1/29/20 5:47 PM, this is what Paul wrote:
While*it*would*be*nice*to*use*\\bob*to*find*the*se rver,
beggars*can*be*choosers,*and*IP*addresses*work*whe n*the*symbolic
names*are*broken.
And you have static IP.s
If not you're up a creek.

Not really. I think this is about file sharing at someone's home, so
presumably the owner has physical access to each of the PCs, and/or access
to the router's DHCP table. Static IPs make things easier, but not having
them shouldn't be a show stopper.

Al means static IPs within your own home network. It may not be strictly
necessary as most routers' DHCP allocation is semi-static anyway as
there's little demand for IPs. Static IPs do avoid head scratching
moments, when you most don't need them.

Yes, I understood what he was saying. Thanks.