{"id":51079,"date":"2020-12-04T03:01:01","date_gmt":"2020-12-03T17:01:01","guid":{"rendered":"http:\/\/www.rjmprogramming.com.au\/ITblog\/?p=51079"},"modified":"2020-12-03T16:17:57","modified_gmt":"2020-12-03T06:17:57","slug":"windows-file-server-and-file-sharing-inaccessible-troubleshooting-tutorial","status":"publish","type":"post","link":"https:\/\/www.rjmprogramming.com.au\/ITblog\/windows-file-server-and-file-sharing-inaccessible-troubleshooting-tutorial\/","title":{"rendered":"Windows File Server and File Sharing Inaccessible Troubleshooting Tutorial"},"content":{"rendered":"
\"Windows<\/a>

Windows File Server and File Sharing Inaccessible Troubleshooting Tutorial<\/p><\/div>\n

Businesses and schools around the world benefitted from the invention of the networking idea of a file server<\/a> as we discussed with the previous Windows File Server and File Sharing Primer Tutorial<\/a>, and we’ll let Wikipedia explain below …<\/p>\n

\nThe term server highlights the role of the machine in the traditional client\u2013server scheme, where the clients are the workstations using the storage. A file server does not normally perform computational tasks or run programs on behalf of its client workstations.
\n
\nFile servers are commonly found in schools and offices, where users use a local area network to connect their client computers.\n<\/p><\/blockquote>\n

Depending on the quality of the hardware and networking software making the file server be a server of files, they work well, and let people collaborate and procedurize tasks for the common good, in a lot of scenarios. But they can have issues. Today we talk about a Windows file server “network drive” issue. The word “inaccessible” will be seen, as well as the threat of “losing unsaved data” when disconnecting that network drive affected, manifesting itself with the user perhaps unable to access all or part of that network drive in the way they can when things are running smoothly.<\/p>\n

We’ve constructed an animated GIF<\/a> presentation with the (opening slide)<\/font> “blurb” …<\/p>\n

\nHave you ever had a Windows network drive (the ones that
\nuse a file server mapping to associate a [drive letter non-C]: with
\nfile server UNC (the \/\/ starting paths)) path cause you errors like above?
\n
\nTo the right is a webpage<\/a> talking of other symptoms too. For the user
\nsuffering the issue it can mean all or parts of the network drive
\nbecome inaccessible and\/or unseen to the user in Windows Explorer.
\n
\nWith problem, when disconnecting this network drive you may be
\nwarned about losing unsaved data because files are still open, and
\nyet it can be that you swear you have no applications you know of
\nopen that could cause this issue.
\n
\nOther than rebooting and reconnecting attempts, what else might
\nresolve this issue? Summary below and in rest of slides of the
\npresentation today, for a misfiring Z: network drive (disconnected) example:
\n
\nping<\/a> [domainNamePartOfMisfiringZNetworkDriveUNC]
\nrem \u2026
\nrem \u2026 this results in an IP address we call [IPAddress] below \u2026
\nrem \u2026
\nnet use<\/a> Z: \/\/[IPAddress][afterDomainNamePartOfMisfiringZNetworkDriveUNC]
\nrem \u2026
\nrem \u2026 this new Z: mapping (perhaps needing switch \/PERSISTENT:YES<\/a>) \u2026
\nrem \u2026 is quite likely to have resolved the issues (as alternative UNC definition)\n<\/p><\/blockquote>\n

… that resolved the issue around here that last time it happened, the alternative UNC<\/a> mapping presumably giving the file server a decent opportunity to reset things, we’re guessing.<\/p>\n

\n

\n

Previous relevant Windows File Server and File Sharing Primer Tutorial<\/a> is shown below.<\/p>\n

\"Windows<\/a>

Windows File Server and File Sharing Primer Tutorial<\/p><\/div>\n

Was discussing Windows and File Servers<\/a> the other day with a student and realized it is a subject often taken for granted now in workplaces, and perhaps in home networks. The way you can share files between networked computers has been around a long time now.<\/p>\n

It has been a boon to System Administrators tasked with allowing various parts of an office to share various parts of whichever file server host’s directories in a variety of access methods involving read, write and execute permissions. Imagine writing this out with pieces and paper and an honour system?!<\/p>\n

In Windows file server connections could be mapped to a spare (network) drive letter and perhaps for the purposes of usage the connection’s identity can just stay in terms of a UNC (Uniform Naming Convention<\/a>).<\/p>\n

Was once responsible for some of this type of work (in a VAX\/VMS server environment with Windows\/DOS desktop clients and Mac desktop clients, using Digital Pathworks<\/a> for DOS and Mac<\/i> file server software) and got quite anal about what people should do on their H: drives and who should be allowed access to the S: drive etcetera etcetera. The way it ended up best explaining it, for Windows systems, to the student was, in terms of local<\/font>, removable<\/font>, personal network<\/font>, network<\/font> drive types, loosely, …<\/p>\n