|
I'm a Sys Admin for a small manufacturer, and we migrated our file server onto a Dell NX 3200 NAS running Windows Server 2012 R1. About once or twice a month, the SMB file shares and associated network drives will stop communicating, despite the server itself and all other Network oriented services remaining active (iSCSI, RDP, Name Resolution, ICMP, TCP/IP, etc.) You cannot restart the service, it freezes at 'Stopping' and you cannot manually force it to close via PowerShell, and if you attempt to restart the machine, it will hang at Shutdown due to the LanManServer Services being unresponsive. Its apparently a bug with Windows Server 2012 R1 and R2, but I was hoping maybe one of the other Sys Admins or Server Gurus had a response. I'm well aware this is a shot in the dark. Otherwise, I'm rolling out a *nix SMB solution. Problem description: LanManServer service becomes unreponsive Attempted fixes: Applied Microsoft provided Hotfixes, did not resolve Recent changes: Made Registry changes to facilitate SMB 1.0 and SMB 2.0 support in attempt to resolve issue. Operating system: Windows Server 2012 R1 System specs: Dell PowerVault NX3200 / Xeon E5-2609 v2 2.5Ghz / 8 GB ECC DDR3 / 300GB RAID 1 for OS, 8TB RAID-6 for File Server Location: United States I have Googled and read the FAQ: Yes, and opened Microsoft trouble ticket, only result was 'Problem under review' See related TechNet article: https://social.technet.microsoft.co...smb-connections CommieGIR fucked around with this message at 19:53 on Jan 15, 2015 |
#
?
Jan 15, 2015 19:39
|
|
|
|
| # ? Apr 27, 2024 19:58 |
|