| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 145607 | 2017-12-16 19:52:00 | Folder sharing problem - any tips? | BBCmicro (15761) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1443441 | 2017-12-16 19:52:00 | I have two computers called White and Black. White sees Black's shares fine but Black doesn't see White's shares reliably (using LAN) Once or twice it has worked OK but I don't know what I had to do to get it that way - and it disappears on reboot. When I power up Black I occasionally see a flash of White's name (not sure what screen I see this in - File Manager? Control Panel?) but it disappears and I don't see the actual shares Troubleshooter doesn't work reliably, although it occasionally says "Can't find a problem" and I close it and everything works! As if the mere running of the troubleshooter kicked something Microsoft's virtual assistant is spectacularly useless. Even when I put in NOT Homegroup, NOT Hotspot, NOT internet it still brings up those - and NOTHING to help with folder sharing |
BBCmicro (15761) | ||
| 1443442 | 2017-12-16 21:38:00 | Assuming its W10. In Search type Sharing -- Select "manage advanced sharing Settings". Make sure Network Discovery is ON --- Scroll down to All Networks -- Turn off Password Protection Sharing. On the shared folders you want to share -- Right click Properties, Sharing , Share -- Make sure the person you want to allow is there, OR select Everyone, change the permission in the drop down box to Read/Write. In The Advanced Sharing, Tick, Share this Folder, and make sure Everyone ( or person you want) has permissions. 8533 Sometimes If the Computers drop, they will come back. The other way( I use) is create a network link to the share, that always works, or you can open the folders by the run command ( with network Address) or create a tile on the start menu, that works all the time. |
wainuitech (129) | ||
| 1443443 | 2017-12-17 08:21:00 | Unfortunately the W10 sharing didn't work Wainui, even though I followed your instructions exactly. I also tried turning off all the shares except a single folder on Cdrive (in case the problem was due to slow wake-up of Ddrive). That had the effect of removing all of white's own shares along with my cellphone and the internet! Rebooting the router brought back the internet. Adding a Ddrive share brought back the Cdrive one as well. At some point the cellphone came back and a bit later I could see Black's shares. I don't know what I did (if anything) to bring these back but I did a lot of rebooting and relaunching File Manager. Obviously it's quite flaky. When I get some time I might compare Black's Services start-up settings (anything to do with Network) with White's. I had a problem with the installation of the OS on White when I downloaded the wrong version of Windows 10 to go with my key. (Something to do with single language? I recall you warning someone about it on PressF1). It might have affected services or it might be something in the Registry (in which case I'm stuck) Microsoft got my OS installation to work but I wouldn't be surprised if there's now a permissions kludge causing problems You suggested a couple of alternatives involving network addresses. I don't know how you would go about doing those. I suppose a network address is something like "\\DESKTOP-05B9TI2\Shared folder on Cdrive - white"? But I don't know how to use it |
BBCmicro (15761) | ||
| 1443444 | 2017-12-17 20:50:00 | Obviously it's quite flaky. and has been for 10++ years . Sharing via a server, almost no issues. Sharing PC to PC : god help you if it doesnt work Start from the beginning. As above , turn on network discovery & turn off pass protection on sharing Change the PC's names: one PC white , the other Black (if you havnt allready) Make sure the workgroup name is the same on both ** Turn off the homegroup services ** Start by trying to share a new folder C:\test . add a txt file in it. Right click the FOLDER , sharing , add 'everyone' right click properties, advanced sharing right click properties , security .... More than one 'setting' in sharing & security to check in that folders properties In 'properties' securitry, you can check access permissions then on the other PC run \\black\test . see if you can access it. Perhaps map the share , making it easier to access directly (google it) Make sure no 3rd party AV or Firewall software is installed. Dont just disable, uninstall them . Make sure network card's power saving is OFF (device manager) use network cable , not wifi (untill its sorted) give both PC's a static IP. try another network card (perhaps flaky network drivers) If it really becomes an issue, then the last resort is a 'Net Use' bat file that runs on startup via task scheduler : last resort sort of thing. |
1101 (13337) | ||
| 1443445 | 2017-12-17 22:08:00 | Networking is one of my weaker areas so you've probably already had better advice than I can offer. However here are a few tips that have helped me in the past when windows file sharing was being a *****. Using the same username and password on both PCs Map a network drive - basically the same as the network link Wainui suggested but with a drive letter, easy way is to right click a network share when it is working and select map network drive Use Homegroup instead of windows networking - or enable both. Mainly if you only use windows 8 and up Make sure both are set for a private network not a public one What's truly annoying is how well linux devices work with windows networking.... They tend to just work. My Nuclear solution was to buy a NAS and use that for shared storage - devices that had trouble seeing each other have no problem seeing the NAS. |
dugimodo (138) | ||
| 1443446 | 2017-12-18 02:29:00 | also, make sure both network connections are set to private , NOT public this may help otherwise social.technet.microsoft.com |
1101 (13337) | ||
| 1443447 | 2017-12-18 08:51:00 | Thanks guys - lots of things for me to try I checked the network adapter power saving and all of them were set to ON - now unclicked. A useful tip 1101 especially since the problematic computer has been sleeping For a short while I had network access both ways, the only thing wrong was White didn't show its own shares So I took your advice Dugi and mapped both ways while I had the chance. On restart File Explorer shows red crosses (both ways) on the mappings. R-click says Disconnected. However a single L-click on each of them removes the crosses and it all works. But File Explorer's Network location doesn't show the shares A good link 1101. I might try an adapter reset particularly since the router is needing a lot of resets these days. I used to have Bluetooth problems and resetting the BT adapter was a regular fix |
BBCmicro (15761) | ||
| 1443448 | 2017-12-18 10:11:00 | I think there's an issue where windows checks for network shares before the network has finished initialising and decides they are not there. I get the same red crosses on my NAS but works anyway so it's not an issue. | dugimodo (138) | ||
| 1443449 | 2017-12-18 19:14:00 | Windows 10 sharing works 100%, all the time, on my network so there is no inherent flaw now. Not to say there wasn't a flaw couple of years ago! W10 is back to using NetBios for WORKGROUP share discovery and this means every adaptor must be running Microsoft client, and there must be an active Master Browser. I find my Master Browser migrates to my WD NAS as it is the most consistently online. It is useful to check for your MB and this site discusses this topic and also has a nifty download that finds your MB:- scottiestech.info It may also be informative to add a heading to your File Explorer/Network display. Rt click the heading row and click Discovery Method. You will then see how W10 found your shares. Hope this is useful. |
linw (53) | ||
| 1443450 | 2017-12-18 20:08:00 | Running a Ruby script might be beyond me linw. We'll see. It's tempting to persevere if the end result is as good as you say I wonder if my Discovery methods give any useful information? |
BBCmicro (15761) | ||
| 1 2 | |||||