Win 10 file sharing problem

I meant google etc really, that will soon turn up others who have found how to do it (or that it can't be done) with a given router

Or you could disable DHCP on the router and do it on a Pi instead (maybe along with an adblocking DNS server such as pi-hole).

I've tried just about everything said here.

DCHP range on my router is 192.168.1.64 - 253

I've assigned static addresses to the things I want to talk to one another, including the range extender, below 64. And reserved those IP addresses in the router.

Googled lots of times. Everyone has a different answer.

None of which seems to have made any difference. Some can see another, but not the other way. Some show another on the network, but aren't allowed access.

I have a similar problem. However it is possible to use \\192.168.1.xx\ to see the files that are shared and accessible on the remote device even when discovery isn't working.

Once accessed by IP address the name may be apparent and so use cut and paste or if you're lucky you can use the pull down feature in the path in File Explorer to see historical network devices.

I've given up wasting too much time on this but if you see a solution, perhaps find an app or background service that does the discovery then I would love to know.

When you say "reserved" do you mean you've set an exclusion for addresses xx.yy.zz.1 to .64 in the router's DHCP scope, or do you mean you've associated every item's MAC address to the IP address you want it to have? The latter is what I meant, then you don't have to give the individual equipment static addresses, you can leave them on automatic and the router will look up their MAC and always give them the same IP addr.

You've not said what model BT router you have, then people can check if the router can do that.

"see" at what level? ping is the starting point, you might need to enable it through firewalls, once everything can ping everything else, move up to SMB/CIFS sharing. If you try to use file shares first it's running before the network can walk.

That's always a problem with windows, too many "experts" and you end up with the blind leading the blind.

another,

aren't

Also check that all devices are in the same "workgroup" or whatever they call it now...

This is just for fun.

nbtscan 192.168.1.0/24

That allows a survey, to see what has registered with a particular protocol. There's more than one nameserver in Windows, and it's outside my payscale to dissect this stuff.

But you can start with something like that for a look.

Both machines above have workgroup=WORKGROUP, so BOB should see BLUEWAVE and vice versa. The Windows 10 machines can benefit from at least having the two services.msc with "Function" as the first word in the name. One of the Function ones seems to be a nameserver of some sort.

And for Windows 10 to see Windows XP machines, needs SMBV1 turned on in Programs and Features : Windows Features.

Paul

My BT router only seems to give the option of reserving an IP address to an item it has seen. So has its MAC address. The devices page shows everything that has been in use. Highlighted if active at the moment. You click on the device and a page opens which allows you to rename it and always use (or not) the IP address given.

It has a pretty full A-Z index. Think it is a home hub 6 - originally supplied when FTC arrived here, so not the latest model.

But I'd say it's a red herring.

You can't actually ping things with Win 10.

Very true. Googling for file sharing problems Win10 should make it obvious you've had it working under a previous version. But much of that you'll find simply tells you how to set up file sharing. Which to me doesn't come under 'problems'.

My ancient Acorn doesn't use workgroups or whatever. But it accesses all files set to share on any of the PCs simply by their computer name and filename. Which makes me wonder about having read Win10 changed things for security...

Yeah, that what I have generally seen and not what I generally want.

If it's allocated the dynamic address via DHCP it's going to be somewhere in the DHCP scope and that's not where I want my static IP's?

I guess I could set it to static (on the device) manually, then go to the router and tell it to keep that IP with that MAC ... and then set the device back to dynamic? It just seems a bit longwinded, especially if you have to replace the router, have lot's of statically assigned devices (as I have) and can't copy the configuration file over? ;-(

Cheers, T i m

Only network geeks can use the diagnostics, understand the output and fix the problem. The rest are wannabes, born somewhere to the left of us, littering the internet with junk posts guaranteed to confuse. It's hopeless.

Try putting a -4 in the command

ping -4 192.168.1.33

if that works, then blame iPv6.

Various ways, erm ..., to get rid of it.

I allocated fixed IP addresses to the things I wanted to, below the DCHP range. Then in the router used the 'always use this address'

Setting the router is the easy bit. ;-)

iPv6 disabled long ago. ;-)

Nevertheless, add it the list of random things to try, just in case ;-)

And it let you *choose* the address?

Cheers, T i m

IPV6 necessary for HomeGroups.

There are a number of recipes on the web for disabling IPV6, some of which are wrong. There is a Microsoft webpage warning about this.

The machine you're trying to ping, does not have to answer if all of ICMP is disabled. The email machine of my ISP, has ICMP disabled. It's not always a firewall that stops it. The foreign host might simply not be listening due to internal settings. I can't ping the ISP Email server.

I disable IPV6 here, by using an IPV4-only router. If a machine wanted to, it could use Teredo Tunneling to push IPV6 through the IPV4 router. But at least the IPV4 router prevents the "chatty bits" of IPV6 through.

Paul

No. It shows you the existing IP address for that device. And gives you the option to 'always use this IP address'. But since it's already fixed, perhaps not needed. But at the same time you can change the name the router calls it (like Android Phone (with a code after that) to 'My mobile' or whatever. Handy for the things that don't tell you what they are. If you know their MAC address. The list shows everything that has ever been connected to the LAN. Highlighted if active.

Win10 doesn't do Homegroups. Workgroup only.

However I did load Win7 on the machine which has multi-boot, and presumably IPV6 still enabled, and on the old Homegroup system. It talked just fine to other Win10 machines, all of which had IPV6 disabled.

Since I've been following lots of 'advice' (from Google, etc) on my problem, I might well reverse those that haven't solved it. And enabling IPV6 again is one of the easier ones.

I don't use Homegroups, but picked this up while thread-browsing.

Somebody thinks there is a dependency. It doesn't make a lot of sense particularly.

Windows 10 did have Homegroups, but they've been deprecated. (A certain release removed Homegroup support.)

The services for Homegroups, at least a couple, are still there. I didn't check for all of them. I was just surprised they weren't removed.

Does it mean a grandfathered Homegroup could work ? Dunno. Not enough feature-kill evident to prevent it.

Paul