Can't share a folder on a local network in Microsoft Windows Server 2025 STD
We have two Microsoft Windows Server 2025 Standard (Version 24H2, Build Number 26100.32995) servers in our Active Directory. We can't share folders; it constantly asks for a username and password. We've tried every solution, but nothing worked. I found a similar thread, but the solutions there didn't work either. topic : https://learn.microsoft.com/en-us/answers/questions/5559013/opening-fire-share-on-2025-server-from-another-202 How can i solve this sharing problem ?QUIC Config not available in Datacenter Build 26052.1000
Hopefully all relevant screenshots are below, please let me know if there is anything else needed. Getting a message that SMB over QUIC is only support on the Azure version. From what I am seeing all versions should have this feature enabled correct? Are there any other pre-reqs that I am not seeing? Thanks * The same message was present on the WAC public release 2311Intermittent issues with SMB over QUIC (Server 2022 Datacenter Azure Edition)
Hi, we're trying to implement SMB over QUIC using a Windows 2022 server syncing with an Azure File Share. This seems to work fine in the first place - when we bring up the server and map the drive on a client, we can connect and everything is good. However: After a while, clients lose connection ("the network share is no longer available") When mapping the drive as persistent, in many cases it does not work after reboot (but after disconnecting it and mapping it again) Sometimes it works again after restarting the client's "workstation" service Sometimes it works again after restarting the server's "lanmanserver" service Sometimes it requires server reboot to work again Sometimes it requires client reboot to work again It behaves similarly from both the internal network (using the server's internal IP) as well as the Internet (using the server's public IP). Per WAC everything seems configured correctly: KDC proxy is enabled and configured and known to clients: Regularly (apparently on every connection attempt, but also if nothing is connected), server logs a QUIC error with its own IP: "This event commonly occurs because the server certificate mapping is not created", but the certificate mapping seems fine: Screenshot from the client (services.msc was used to restart the workstation service): Does anybody have an idea what could be wrong, or which logs to check, or which events to collect?
Veeam B&R backup jobs failed to login to Qnap Nas after KB5011503 installed
Good Morning, Veeam backup & Replication CE 11 (last release) installed on Windows Server 2019 Hyper-V VM from about 1 month Veeam Backup jobs use as destination a shared folder on Qnap Nas. Windows 2019 VM Italian language standalone, Qnap Nas under domain. R&W user used for Qnap autentication it's local user for Qnap and Administrator for Win2019 VM. All go fine before KB5011503 update After this installation Veeam Backup job works only with guest user. No other user can autenticate to Qnap with SMB 1, 2, 3 Error message on Qnap is "Processing MACHINENAME Error: Nome utente o password non corretta --tr:Error code: 0x0000052e Failed to process [isFileExists]. --tr:Client failed to process the command. Command: [isFileExists]. --tr:event:3:" Trying to uninstal KB5011503 update, after reboot all veeam Backup Job returns to work. Updating KB5011503 again all Job stop to work. Could be this a bug? Where I can report this to microsoft? Thanks PaoloBSOD with SMB Compression
I got page "fault in nonpaged area" BSOD in "srvnet.sys" with server 2022 when I enable smb compression and open a rar file with winrar from remote mapped drive with windows 11 client. so when will the final version be available. It seems so buggy that can not be used now. btw there is also no gui effort probably because of not matured yet. I want know the roadmap for smb compression. thanks in advance. and It took some time 2 day to figure out the bsod caused from compression. I isolate it.Cant use SMB by host
Hello there My customer provided Windows Server 2016 Standard Edition system. After testing, it is found that the SMB share cannot be accessed through the domain name, but can only be accessed through the loopback address 127.0.0.1 and the network card IP (192.168.111.4) Visit after adding "127.0.0.1 me" in the Host file, Error 0x80004005 After Wireshark captures the packet, it is found that the SMB protocol returns a STATUS_NOT_SUPPORTED error How can i fix this. Thanks lot.
Windows Server 2016 Intermittently Slow
Hi So I have two Windows Server 2016 (1607) they are RDS servers they do run SQL but the CPU is not massively high on them. The both run on ESXi 6.5. Latest hardware and tools applied. Both servers run the same AV the same FW rules, etc. They connect to a file server which is running Windows Server 2019 (1809). For some reason only one of the RDS servers will be a pain. The other one will run fine. So for example: 01 - Fine 02 - Painfully slow Logging on to 01 takes around 5 seconds. Logging on to 02 takes around 3 minutes - stuck on either applying the printer GPO or the drive mapping GPO. When logged in people will get a blue wheel when accessing file shares or such like. The file shares will just hang when browsing but then return fine. On the other server it's fine. I've checked and they're both running SMBv3 to all connections that I can see. I have completely ran out of ideas on what could be causing this. Anyone have any ideas? Thanks!SMBv3 - Windows Server 2016 - Roaming Profile
Hallo, wir haben ein Problem mit der Freigabe von Dateien auf einem Windows Server 2016 in Verbindung mit Roaming Profiles und Offline Cache. Auf dem Server existiert ein Home-Share welcher für das Offline-Caching von Notebooks verwendet wird. Zusätzlich gibt es hier einen unternehmensweiten Profile-Share in dem auch der Appdata-Roaming Zweig abgelegt wird. Wenn sich ein Benutzer an einem System anmeldet wird ja das gesamte Profil vom Server geladen und beim Abmelden wieder zurückgeschrieben. Wir haben festgestellt, dass diese Dateien beim anmelden (Read) und beim Abmelden (Write) noch lange am Server in Verwendung sind (Open Files) obwohl hier bereits die Vorgänge am Client abgeschlossen wurden. Sollte sich der Benutzer nach erfolgter Anmeldung gleich wieder anmelden, kann es vorkommen, dass der Benutzer noch länger beim Anmelden warten muss - hier wird anscheinend die lesende Dateifreigabe am Server abgewartet. In einigen Fällen wurden auch temporäre Profile erstellt (Zeitüberschreitung!?). Hat jemand einen Vorschlag wie wir hier bei Profilen die Dateifreigabe am Server gleich nach Abschluss auslösen können? Die Tipps mit Oplocks und Leasing am Server ist etwas kritisch, da wir hier ja noch das Offline-Caching auf einen anderen Share am selben Server benötigen. Vielen Dank für eure Unterstützung. LG Joachim
