Windows 10: Windows 10 file shares server no longer show on devices

James A. Zoufaly · Mar 14, 2025

I've been able to watch shared videos from my Windows 10 PC on my TCL Roku TV & Sony 4K BR player for years and suddenly neither device sees the Windows server. I've reset the router, reset network adapter, checked ALL network settings and nothing works. To be clear, I am NOT talking about screen mirroring.Any advice?

:)

Ahhzz · Mar 14, 2025

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

Open a new Explorer window.

Click View in the ribbon.

Click Options.

Under General, next to “Open File Explorer to:” choose “This PC.”

Click OK

credit to Lifehacker.

Wing P · Mar 14, 2025

Cannot file shared to windows server 2003 using windows 10 build 1703

Hi Rose,

Did you get any error messages when you try share file? Yes,i got error windows cannot access \\192.168.1.15\public (error code : 0x80004005)

Does this happen to all files you want to share or to just specific file only? this happen when i use windows 10 and some windows 7. (but the older computer can access file in windows server 2003).

What troubleshooting steps have you done so far? I have check connection with LAN cable working, ping with ip and name server to server it working to.

any solution for this error?

Thank You.

Regards,

Brink · Mar 14, 2025

New File Share Witness Feature in Windows Server 2019

This blog discusses a new feature in the upcoming release of Windows Server 2019. Currently, Windows Insiders receive current builds of Server 2019. We urge you to become an Insider and play a part in making Windows Server 2019 the best that it can be. To do so, go to this link and sign up.

One of the quorum models for Failover Clustering is the ability to use a file share as a witness resource. As a recap, the File Share Witness is designated a vote in the Cluster when needed and can act as a tie breaker in case there is ever a split between nodes (mainly seen in multi-site scenarios).

I don’t want to go through the list of all the requirements but do want to focus on one in particular.

The Windows Server holding the file share must be domain joined and a part of the same forest.

The reason for this is that Failover Cluster utilizes Kerberos for the Cluster Name Object (CNO) to connect and authenticate the share. Therefore, the share must reside on a domain member that is in the same active directory forest.

There are scenarios where this is not possible. These scenarios are:

No or extremely poor Internet access because of a remote location, so cannot use a Cloud Witness

No shared drives for a disk witness. This could be a Storage Spaces Direct hyper-converged configuration, SQL Server Always On Availability Groups (AG), Exchange Database Availability Group (DAG), etc. All of which do not utilize shared disks.

A domain controller connection is not available as the cluster has been dropped behind a DMZ

A workgroup or cross-domain cluster where there in no active directory CNO object

We have had a lot of requests over the years for how to get around these scenarios and there wasn’t a good story for it. Well, I am here to tell you we listened, and we produced something better than a workaround.
In comes Windows Server 2019 and the new File Share Witness feature to the rescue.

We can now create a File Share Witness that does not utilize the CNO, but in fact, simply uses a local user account on the server the FSW is connected to.

This means NO kerberos, NO domain controller, NO certificates, and NO Cluster Name Object needed. While we are at it, NO account needed on the nodes. Oh my!!

The way it works is that on the Windows Server you wish to place the FSW, create a local (not administrative) user account, give that local account full rights to the share, connect the cluster to the share.

Let’s take for example, I have a server called SERVER and a share called SHARE I want to utilize as the File Share Witness. For creating this type of File Share Witness can only be done through PowerShell. The steps for setting this up are:

Log on to SERVER and create a local user account (i.e. FSW-ACCT)

Create a folder on SERVER and share it out

Give the local user account (FSW-ACCT) full rights to the share

Log in to one of your cluster nodes and run the PowerShell command:

Set-ClusterQuorum -FileShareWitness \\SERVER\SHARE -Credential $(Get-Credential)

You will be prompted for the account and password for which you should enter SERVER\FSW-ACCT and the password.

Viola!! You are done as we just took care of all the above scenarios. The cluster will keep the name and password encrypted and not accessible by anyone.

Just as an FYI, the original demo of this feature was using a USB thumb drive holding the share plugged into a router. Not that we would recommend doing it, but does show how far you could take this.

Please try out this new feature and provide feedback through the Feedback Hub app.

Thanks,
John Marlin
Senior Program Manager
High Availability and Storage
Click to expand...

Source: New File Share Witness Feature in Windows Server 2019 | Clustering and High-Availability

Windows 10: Windows 10 file shares server no longer show on devices

Windows 10 file shares server no longer show on devices

Windows 10 file shares server no longer show on devices

Windows 10 file shares server no longer show on devices

Windows 10 file shares server no longer show on devices - Similar Threads - file shares server

Windows 10 Enterprise - tmp files on shared server

Windows 10 Enterprise - tmp files on shared server

Windows 10 Enterprise - tmp files on shared server

FILE AND DEVICE SHARING NOT WORKING ON WINDOWS 10

FILE AND DEVICE SHARING NOT WORKING ON WINDOWS 10

Windows Server 2019 Shares no longer accessible from windows 10 clients

Windows Server 2019 Shares no longer accessible from windows 10 clients

Windows Server 2019 Shares no longer accessible from windows 10 clients

File share no longer works