<div>
On each machine, delete all mapped drives &nbsp;(NET USE &nbsp;X: /Delete for all drives X:)<br />
Restart, and remap again and that normally will fix this.
</div>


<div>
Does not work. &nbsp;As soon as I simulate another internet failure the same thing happens again. &nbsp;The error code is 0X80070079.
</div>


<div>
You mentioned you have a WatchGuard router. That is your failure point. It is your gateway. Once the gateway goes down, you can no longer route.
</div>


<div>
When you simulate the failure, can you reach the NAS via IP?
</div>


<div>
Try looking at this Article for Connection lost issues<br />
<br />
<a href="https://windowsreport.com/fix-semaphore-expired/" rel="ugc">https://windowsreport.com/fix-semaphore-expired/</a><br />
<br />
Also open cmd.exe and type NET USE X: \\device\folder What numerical error do you get?
</div>


<div>
No &nbsp;I have to disagree. &nbsp;It has nothing to do with that otherwise you could not see it in the Windows Network folder. &nbsp;This is local network access only, nothing involving the gateway.
</div>


<div>
Do not Browse (as that has become somewhat unreliable). &nbsp;Map network folders properly with NET USE
</div>


<div>
John, <br />
<br />
Not sure what you mean by &quot;Do not Browse (as that has become somewhat unreliable). &nbsp;Map network folders properly with NET USE&quot; &nbsp;I click the Map Network Drive icon in the toolbar and type in \\192.168.0.97\FNDocuments<wbr />.<br />
<br />
Also all of my computer use NTFS already not FAT32. &nbsp;This situation in the same on all 7 computers.
</div>


<div>
Security has changed so much that going to Network on the client and browsing for the NAS may not work. I never use that method any more
</div>


<div>
Check your network settings on any of the clients just to see if there exists a gateway or paste your IPCONFIG /ALL
</div>


<div>
I know you stated no gateway, but it's just to rule it out.
</div>


<div>
IPConfig All<br />
<a href="https://filedb.experts-exchange.com/incoming/2019/03_w13/1416195/IPConfig-ALL.JPG" target="_blank" class="file-inline" title="IPConfig-ALL.JPG (294 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>IPConfig-ALL.JPG</a>
</div>


IPConfig-ALL.JPG

<div>
John what method do you use to access an NAS drive or a mapped drive on another computer?
</div>


Photographer

Fred Fisher

<div>
You mentioned that you don't use a gateway.<br />
<br />
What is device 192.168.0.1? Would this happen to be your WG?<br />
<a href="https://filedb.experts-exchange.com/incoming/2019/03_w13/1416197/2019-03-27_153102.jpg" target="_blank" class="file-inline" title="2019-03-27_153102.jpg (104 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>2019-03-27_153102.jpg</a>
</div>


2019-03-27_153102.jpg

<div>
Can a shortcut be setup for this if not it is a deal breaker as the users on the network will not be sophisticated enough to do it.
</div>


<div>
Yes . Once you have the NET USE format, put it in a batch file on the desktop. I do this routinely
</div>


<div>
efrimpol,<br />
<br />
You mentioned that you don't use a gateway.<br />
<br />
What is device 192.168.0.1? Would this happen to be your WG? &nbsp;That is the watchguard router, my bad, but it is still in the loop all I am doing is disconnecting the cable to the cable modem. &nbsp;Local access has not been disturbed. &nbsp;I can still remote desktop to all of the computers on the network.
</div>


<div>
When I try Net Use a:\\192.168.0.97\FNDocumen<wbr />ts I get &quot;System error 67 has occurred&quot;.
</div>


<div>
No John stipulated devicename, not IP.
</div>


<div>
Try IP address for device. It must have that
</div>


<div>
also a space after &quot;A:&quot; is required. But in addition I think A: and B: are reserved. A: and B: were equated to the use of floppy drives.
</div>


<div>
I thought I did IP address for device.
</div>


<div>
correct format <br />
<br />
NET USE DRIVE LETTER FULL PATH <br />
<br />
net use G: \\192.168.0.97\FNDocuments<wbr />
</div>


<div>
Usually you want to use letters above E or F.<br />
<br />
A: Floppy<br />
B: Floppy<br />
C: O/S<br />
D: CD/DVD drive<br />
<br />
E: could be a USB flash drive or external USB drive<br />
F: could be another USB drive or a mapped drive
</div>


<div>
A and B are not reserved. &nbsp;As I have the same issue with P as a mapped drive. &nbsp;I use A and B so that it came be the same across all of the network computers. &nbsp;Net Use a: \\192.168.0.97\FNDocuments<wbr /> &nbsp;- results in error 85.
</div>


<div>
All the CD/DVD drives on all the computers on the network are drive V:. &nbsp;C, D, E, F are used or not used on the network computers for the disk drives that may or may not be on a particular computer. &nbsp;The I drive for example is the iTunes drive. &nbsp;Drives X and Y are for media cards.
</div>


<div>
Also R, S, and Q are used for thunderbolt 3 drives.
</div>


<div>
You have a domain so WHY are your DNS servers using a public internet address and not using a private IP address? Ergo using NAME will fail when the internet isn't available. IP address should still work.
</div>


<div>
Somehow your DNS settings are involved because the issue only occurs when you replicate it by unplugging the WG from the internet.<br />
<a href="https://filedb.experts-exchange.com/incoming/2019/03_w13/1416199/2019-03-27_153628.jpg" target="_blank" class="file-inline" title="2019-03-27_153628.jpg (27 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>2019-03-27_153628.jpg</a>
</div>


2019-03-27_153628.jpg

<div>
Sorry, Dave. You beat me to punch yet again. ARGH!!<br />
<br />
LOL
</div>


<div>
net use A: \\192.168.0.97\FNDocuments<wbr /> still get error 85.
</div>


<div>
Also, Dave. <br />
<br />
He mentioned that there is no domain (no server). It is basically a workgroup setting (remember Windows 3.11??
</div>


<div>
try a different drive letter that you know is NOT in use
</div>


<div>
error 85<br />
When a user attempts to map a resource to a network drive using a drive letter that was previously used by another resource, the user may receive the following error message: System error 85 has occurred. The local device name is already in use.
</div>


<div>
&quot;You have a domain so WHY are your DNS servers using a public internet address and not using a private IP address? Ergo using NAME will fail when the internet isn't available. IP address should still work.&quot; &nbsp;<br />
<br />
There is No domain. &nbsp;No server. &nbsp;All computers (workgroup is &quot;FishNet&quot;) on the local network are free standing and independent. &nbsp;The router assigns all of the private IP addresses they are NOT public.
</div>


<div>
David, &quot;<br />
<br />
error 85<br />
When a user attempts to map a resource to a network drive using a drive letter that was previously used by another resource, the user may receive the following error message: System error 85 has occurred. The local device name is already in use.&quot;<br />
<br />
THANK YOU that helped. &nbsp;I disconnected the A: drive and then used the Net use command.
</div>


<div>
Should I be looking at the DNS settings on the router??
</div>


<div>
Ok, you successfully mapped the drive. Now pull the plug on the internet and see if you can still access the NAS.
</div>


<div>
To avoid the reliance on the Internet check which each Windows 10 does, disable the Microsoft network connection test via local security group on each system<br />
This will terminate the check.<br />
<br />
Double check once disabled that your other equipment does not rely on the presence of an Internet connection.
</div>


<div>
efrimpol &quot;Ok, you successfully mapped the drive. Now pull the plug on the internet and see if you can still access the NAS.&quot;<br />
<br />
Tried this just now. &nbsp;The results were curious at best. &nbsp;The A drive only worked after I issued the NET USE a: \\192.168.0.97\FNDocuments<wbr /> command. &nbsp;The B drive did not work at all even after issuing the NET USE b: \\192.168.0.98\FNDocuments<wbr />Bk command.<br />
<br />
I have checked the setup of both NAS drives to make sure that they were the same, the only difference of course was the device name. &nbsp;One has Bk appended on the end of the name and the other does not.<br />
<br />
I now this &quot;difference&quot; in the device name does not occur until the 12th and 13th characters. &nbsp;Should I rename the b: device the BkFNDocuments instead of FNDocumentsBk?
</div>


<div>
When you pull the internet feed, what happens on the router? Presumably it is issuing IPs. Does the route reset causing network connections to drop (see event log on each client workstation to see if there is an event attributed to the network) what is logged on the NAS when the internet connection is not present (i.e. does your NAS also functions as a CLOUD meaning it has a connection to the Vendor cloud (Segate/WDC)?<br />
Centrally managed via the cloud?<br />
<br />
<a href="https://answers.microsoft.com/en-us/windows/forum/all/enabling-ncsi-active-probing-prevents-auto-connect/c9f52738-7036-4391-b8d9-9c2ce3e73e92" rel="ugc nofollow">https://answers.microsoft.com/en-us/windows/forum/all/enabling-ncsi-active-probing-prevents-auto-connect/c9f52738-7036-4391-b8d9-9c2ce3e73e92</a><br />
<br />
Use local security policy to disable this option versus registry edit.
</div>


<div>
<i>I now this &quot;difference&quot; in the device name does not occur until the 12th and 13th characters. &nbsp;Should I rename the b: device the BkFNDocuments instead of FNDocumentsBk?</i><br />
<br />
I'm not sure about this since I don't have a NAS at our facility, but I just did a Windows mapping to one of shares, with a total of &quot;27&quot; characters after the IP address with no issues. But it doesn't hurt to at least try your rename.<br />
<br />
Microsoft Windows [Version 6.3.9600]<br />
(c) 2013 Microsoft Corporation. All rights reserved.<br />
<br />
U:\&gt;net use i: \\192.168.1.100\Shared\TP\<wbr />EasyLabelC<wbr />MDfiles<br />
The command completed successfully.
</div>


<div>
U:\&gt;net use i: \\192.168.1.100\Shared\TP\<wbr />EasyLabelC<wbr />MDfiles\te<wbr />st<br />
The command completed successfully.<br />
<br />
<br />
U:\&gt;net use k: \\192.168.1.100\Shared\TP\<wbr />EasyLabelC<wbr />MDfiles\te<wbr />stbk<br />
The command completed successfully.<br />
<br />
No difference - able to map successfully
</div>


<div>
Ok, that settles the device name question. &nbsp;I only mentioned it because I have run into situations where it did make a difference. &nbsp;I will not be able to test any further today since the network needs to be up to get some end of month work done. &nbsp;Hopefully I can tackle this again tomorrow.
</div>


<div>
admin's work is never done...
</div>


<div>
When you get an access error 85, 53 I think,<br />
It suggests a stale session on the server where the share is. The server already reflects an active session.
</div>


<div>
<div class="content wysiwyg-content">
I have a work network (no server, all on the same subnet) that has 7 computers all running Windows 10 Pro 64 bit, &nbsp;8 NAS drives, and each computer has various mapped drives. &nbsp;The network is connected to the internet via a WatchGuard router. <br />
<br />
Recently we lost our internet connection for several days during that time we were not able to access any of the mapped drives from any of the computers on the network. &nbsp;We could however access the admin setup for the NAS drives from the Windows Network folder.<br />
<br />
When our internet connection was restored, abracadabra the mapped drives all worked again. &nbsp;To simulate the internet going down I remove the cable into the router from the internet modem. &nbsp;Once again the mapped drives are lost. &nbsp;Plug it back in and they are restored.<br />
<br />
How do I fix this so that we can access the mapped drives regardless of the status of the internet connection.
</div>
</div>


I have a work network (no server, all on the same subnet) that has 7 computers all running Windows 10 Pro 64 bit,  8 NAS drives, and each computer has various mapped drives.  The network is connected to the internet via a WatchGuard router. 

Recently we lost our internet connection for several days during that time we were not able to access any of the mapped drives from any of the computers on the network.  We could however access the admin setup for the NAS drives from the Windows Network folder.

When our internet connection was restored, abracadabra the mapped drives all worked again.  To simulate the internet going down I remove the cable into the router from the internet modem.  Once again the mapped drives are lost.  Plug it back in and they are restored.

How do I fix this so that we can access the mapped drives regardless of the status of the internet connection.

Lost local network mapped drives when internet connection is lost

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.

Windows OS

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.