![]() |
Forum Index : Microcontroller and PC projects : W10: Does not exist issue....(network shares)
![]() ![]() |
|||||
Author | Message | ||||
bigmik![]() Guru ![]() Joined: 20/06/2011 Location: AustraliaPosts: 2950 |
Hi Grogs, All, All was going well until 2 or 3 weeks ago when I did a Windows Update manually (Thanks Paul_L) I saw 21H1 was there and thought I installed it but it was some other in-between update. After that update these issues occurred (slow SOMETIMES to open any drive eg. when saving an attachment from email). I since found out I have to actually click on 21H1 to install it.. It didn't actually do anything different to my issues. @Grogs, Yes from a cold power on start I can ping the box, I can go to the box via my browser and I can access my share via the NETWORK icon of my box but the MAPPING to drive letters are not accessible. Strangely I can map to the IP and assign to another letter such as \\10.0.0.xx\bigmik and it works but on the next COLD power on start even that wont work. The only answer for me is a cold boot followed by a restart and that is fine.. Strangely since the real 21H1 update my slowness for saving attachments is much better if not fixed but the mapping is failing. I have 2 NAS boxes, a Buffalo link station that exhibits this issue and a ReadyNas that is perfect all of the time. The problem is the Buffalo is my main unit. I may have to back them up and swap them around. The 2nd NAS is mainly for backing up my backups. Ideas floating in my head are: 1. You mention you cant have a - in the name (my box is called Mickls-Nas note the - in the name. This has always been fine for the 6 or 7 years I have had this NAS and if something changed to enforce the naming convention why does a restart work and why doesn't using the IP instead of name for the server work? 2. It might be Norton as I recently installed the latest version when I resubscribed for another year. But neither of my other PCs do this. 3. At about the same time this started occurring I increased my RAM from 16GB to 32GB but no other instability is being exhibited so I can't see why that could be the cause I have been playing with networks for over 40 years going back to the old COAX 10mb networks and it has always been fun. I even did a Cisco networking course when I was at work but I have forgotten most of that (was about 5 years ago and I am retired now nearly 3 years) Anyway I am looking like it is a POWER UP then RESTART for me. Luckily the boot process is only 30sec or so. (excluding DELL screen) I will keep you posted. Regards, Mick Edited 2021-06-28 14:25 by bigmik Mick's uMite Stuff can be found >>> HERE (Kindly hosted by Dontronics) <<< |
||||
TassyJim![]() Guru ![]() Joined: 07/08/2011 Location: AustraliaPosts: 6283 |
Make sure you haven't got hibernate turned on. VK7JH MMedit |
||||
bigmik![]() Guru ![]() Joined: 20/06/2011 Location: AustraliaPosts: 2950 |
A big Kiss and Hug to you Jim. ![]() Wow, I dont use hibernate but it was enabled. Simply disabling it has fixed the problem. Now the question remains. WHY would hibernate do that weirdness. Thank you so much Jim, and everyone else who has offered suggestions except that bloke who told me to light 2 sticks of dynamite and throw 1 away ![]() Kindest of Regards, Mick Mick's uMite Stuff can be found >>> HERE (Kindly hosted by Dontronics) <<< |
||||
Grogster![]() Admin Group ![]() Joined: 31/12/2012 Location: New ZealandPosts: 9610 |
VERY weird. "WHY would hibernate do that weirdness." Well, W10 hibernate - is Windoze hibernate... "Let's shut down this drive, as it is sucking excess power - but let's NOT allow anyone to get access to it then after that point WITHOUT a full reboot...." Thanks Bill...... THIS sh*t is why I use Linux for all my servers/NAS stuff now. Under MOST linux's, they WON'T shut off the HDD's unless you specifically ask for that. Windoze just does it without asking, cos - you know - power saving and all that bollocks..... Smoke makes things work. When the smoke gets out, it stops! |
||||
lizby Guru ![]() Joined: 17/05/2016 Location: United StatesPosts: 3378 |
My question as well. I have hibernate turned on (but don't see exactly Mick's issue). ![]() Hearing voices inside your head, Mick? ![]() PicoMite, Armmite F4, SensorKits, MMBasic Hardware, Games, etc. on fruitoftheshed |
||||
TassyJim![]() Guru ![]() Joined: 07/08/2011 Location: AustraliaPosts: 6283 |
Hibernate was used to make systems start quicker. Now we have SSDs, it is completely worthless. Hibernate has the side effect of keeping bad settings saved for next time. With W10, if you simply shut the PC down, hibernate gets used so a shut down and restart does not clear out any problems. On the other hand, if you elect to restart rather than shut down. start up, Windows does a proper shutdown and the restart starts 'fresh' That is why Mick was having success with his restart. I still think it is a power - initializing issue with the network card, probably due to a driver update. Either way, no hibernate makes for a clean start. Jim VK7JH MMedit |
||||
lizby Guru ![]() Joined: 17/05/2016 Location: United StatesPosts: 3378 |
I don't understand this at all--other devices on my network are visible after opening a closed laptop--only the network drive gives me fits staying disconnected. If something visible when shut down is not visible upon opening up again, why can't Windows just keep trying for a moment or two? And of course, Network Diagnosis never finds it, although Windows Explorer does if I enter IP+folder name. After power-up/restart it takes me 10 minutes to set up the 20+ programs I'm typically running, so that won't work for me. PicoMite, Armmite F4, SensorKits, MMBasic Hardware, Games, etc. on fruitoftheshed |
||||
TassyJim![]() Guru ![]() Joined: 07/08/2011 Location: AustraliaPosts: 6283 |
After power-up/restart it takes me 10 minutes to set up the 20+ programs I'm typically running, so that won't work for me. If you aren't having problems, don't change anything. VK7JH MMedit |
||||
bigmik![]() Guru ![]() Joined: 20/06/2011 Location: AustraliaPosts: 2950 |
Lads, Out of interest, I re-enabled my BIOS setting (Allow USB to wake the PC) which was the other problem that the latest up-dates decided to play havoc with. I thought now I have disabled hibernate, which I never used, it might now work. Remember the issue was a 2x USB HUB cascade that caused my PC to not shut down and stay powered off). Nope no luck.. That issue is still there so I disabled it again. At least my problem is fixed for me. I still cant understand why having hibernate enabled (BUT NOT USED) would cause the network issue I had. Thanks again and another thing to jam into my brain for future recall. Regards, Mick Mick's uMite Stuff can be found >>> HERE (Kindly hosted by Dontronics) <<< |
||||
![]() ![]() |
![]() |
![]() |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |