Windows 10: Why does windows explorer fail to show mapped local network storage when the internet...

I have several PC's on a Local network, and that network is also connected to the internet modem. When the internet is down for any reason, the local network is still functional. So why does windows explorer not show mapped drives to the network storage devices when the internet is down, yet they appear normally when the internet is 'up'?Is there a setting that will allow access to the local network NAS even when the internet is down?

:)

 

Microsoft Internet Explorer renamed to Windows Internet Explorer ?




Since version 7 of the world`s most popular web browser - Microsoft Internet Explorer was silently renamed to Windows Internet Explorer.Such a step from Microsoft is not a surprise since Internet Explorer is part of the Windows operation system for a long time.Obviously Microsoft corp. wants to state that Internet Explorer is already considered as a part of Windows and not as an external browser (remember the IE and WMP law issues last year!?).

 

Mapped drives not showing up on Explorer

Wanted to mention that I'm experiencing this same issue. Environment here is a Windows Server 2012 R2 domain with network shares and printers mapped by GPO. GPO drive mappings are not on a per-user basis and instead are global for all users.

Affected user can not access mapped drives via explorer, yet NET USE shows drives mapped as expected. Attempting to remap network drives via explorer results in a prompt stating that the connection is already mapped to that drive letter, do I want to disconnect and reconnect it?

Oddly, using applications that provide an 'open document' dialogue can see and access mapped network drives normally. For example, open Word, file -> open -> browse: Left pane shows network shares, clicking on network share shows share contents. Clicking on 'This PC' shows all mapped drives which are navigable and documents can be opened normally. Doing this does not correct the issue with Explorer. Similarly, a command prompt also operates as expected, so it's possible to change to a mapped network drive by the associated letter and to list / copy / delete files normally.

Issue appears to be limited to a single user profile on the workstation displaying the described symptoms. Logging in as another user results in the drives being mapped and accessible as usual. Symptoms persist through reboot. User account with symptoms does not have admin access locally or on the domain.

 

Tweaking Save Menu to show "Network" as a save location?

You may be able to "map" the network address, be sure to map to the Drive Root or top of the tree of any area you wish to access. A mapped network location shows in the File Explorer as a local Drive letter, that you select, so should work with your application.

Add a Network Location in Windows 10 | Tutorials will provide step by step