Windows 10: W10 - File Share server access very slow

Hello all,

Since a week ago my File Share server has been slow to open the "root" folder. Opening a folder via the path in the explorer is immediate.
Anyone with this problem?
This only happens with Windows 10, when I try to access File Share through a Windows Server, it's immediate/normal.

Notes:

My "corporate" antivirus is Kaspersky, I have already uninstalled it from the server and stopped on my computer. It didn't.

PC: Kaspersky Endpoint Security 11.5.0.590
Server: Kaspersky 11 for Windows Server v11.0.0.480
OS: Windows 10 20H2 Build 19042.867 with CU 2021-03


Thank you

:)

 

accessing and renaming of network files on w10 with w10 computer is slow

Occasionally the accessing of network files on w10 computer acting as server is very slow. It takes long to read or rename the file on server from osme w11 computers in the network. We have try to disable Indexing on server but it is the same. Renaming
the files on the server directly is always good and fast.

 

W10 cant access WS2008 file shares

I have the following setup:

Server: Proliant series, with my required folders shared with 'Administrators', WS2008

Clients:
2 Laptops, W10 Home installation |
1 Desktop, W10 Pro installation

All are connected to the same router, there is only 1 router which is also our internet gateway

Previously

Whenever I wanted to retrieve or store files on the server, I would navigate to it through explorer \MY-SERVER\ and be prompted for login credentials. I provided the Administrator credentials and I could then see and interact with the file shares, as expected. This was true of all clients on the network.

Changes

Yesterday an order for a new mobo/cpu arrived for the Desktop. After installing these I flattened the boot drive and reinstalled W10 (for good house keeping)

Now

If I try to access the server (nav to \MY-SERVER) I am presented with the following message:
"Windows cannot access \MY-SERVER\

You do not have permission to access \MY-SERVER. Contact your network administrator to request access"

It is not even prompting me for login credentials. Whats curious is that if I navigate to a specific shared folder, eg \MY-SERVER\stuff, then I AM prompted to login (after a long pause), but the login dialog is captioned "Access denied", and providing the correct login credentials presents a similar Network Error message.

The server also does not appear in the list of network places on the Desktop. The other clients (2 W10 laptops) can still see and access the Server as normal.

Notes

• The desktop can reach the server through ping and Remote Desktop (I
  would just live with it and copy files through the tsclient share
  which appears during an RDP session, but I cannot stream files this
  way).
  
• The server has not stale credentials in Credential Manager
  
• All systems are in the same workgroup (WORKGROUP)
  
• Reg keys for 'restrictanonymous' are set to 0, although this surely would not affect an authenticated login anyway?
  

What am I doing wrong? Why is the W10 Desktop not able to access the shares in the same way the other W10 clients can?

 

W7 access of W10 share

On my home network W10 systems can access shares on other W10 systems, and W10 can access W7 shares. However, when W7 tries to access a W10 share, it wants a network password. I give it the user/pswd I use to log in on the W10 but that doesn't help.

I found one place:
Cannot access Shared folder in Windows 10 via Windows 7 PC
that suggested setting HKLM...Lsa\restrictanonymous to 1
but that didn't seem to help.

TIA!