win 10 machine can’t access network shares on pdc, intermittent
I manage a small windows domain for my home/home office. It consists of a PDC running Windows Server 2003 SP1 (I know! it’s old! etc.) and a hand full of computers with fixed private IP addresses (10.x.x.x):
2 Win 7 Pro (one 64-bit, one 32-bit)
My intermittent problem for the past year or so is that one of the Win 10 machines occasionally (maybe 3 times/month) suddenly cannot access any network shares on the PDC. This causes a number of automated backup processes to fail. When this happens:
(machine names and IP addresses changed to protect the guilty! 🙂
— it can ping the PDC by name, so DNS is not the issue
C:\Users\XXX>ping MyServer Pinging MyServer [10.x.x.x] with 32 bytes of data: Reply from 10.x.x.x: bytes=32 time=1ms TTL=128 Reply from 10.x.x.x: bytes=32 time - this fails, with a fairly long delay before the error message appears (perhaps 2 minutes):
C:\Users\XXX>dir \\MyServer\backupfiles The semaphore timeout period has expired. - and yet this works:
C:\Users\XXX>dir \\10.x.x.x\backupfiles Volume in drive \\10.x.x.x\backupfiles is zzzz Volume Serial Number is 10C0-79BC Directory of \\10.x.x.x\backupfiles 05/09/2021 08:28 AM . 05/09/2021 08:28 AM .. 05/13/2019 09:53 AM 23 BackupCacheRoot.txt 03/21/2019 12:14 PM 23 BackupRoot-ZZZZ.txt 03/21/2019 12:14 PM 23 BackupRoot.txt 05/25/2019 11:53 AM 23 BackupStagingRoot.txt 07/27/2020 10:43 AM 22 BatchFolder.txt 03/24/2019 09:36 AM 24 BatchJobFolder.txt 05/14/2019 08:13 PM 1,510 GetBackupLoc.bat 7 File(s) 1,648 bytes 2 Dir(s) 4,306,067,456 bytes free - it can connect to network shares on other machines
The only way I can clear this is by rebooting the win 10 machine, after which all is well . for perhaps a week.
I'd be grateful for any insights anyone may have.
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
9,137 questions
Sign in to follow
Windows 10 Network
Windows 10: A Microsoft operating system that runs on personal computers and tablets. Network: A group of devices that communicate either wirelessly or via a physical connection.
2,019 questions
Sign in to follow
0 comments No comments Report a concern
I have the same question 0
Accepted answer
Gary Nebbett 4,596 Reputation points
2021-06-12T08:47:18.447+00:00
Hello @Blaise , I think that your problem may be related to other reported problems in this forum and we may be getting closer to an understanding of the root cause. The problem seems to affect older Network Attached Storage devices and Windows 2003 and earlier. I have included part of another post of mine here, adapted to your scenario. The authoritative source of information about SMB is the Microsoft specification "[MS-SMB2]: Server Message Block (SMB) Protocol Versions 2 and 3". Section "3.2.4.2.2 Negotiating the Protocol" of this document says: When a new connection is established, the client MUST negotiate capabilities with the server. The
client MAY use either of two possible methods for negotiation. The first is a multi-protocol negotiation that involves sending an SMB message to negotiate the use of
SMB2. If the server does not implement the SMB 2 Protocol, this method allows the negotiation to fall
back to older SMB dialects, as specified in [MS-SMB]. The second method is to send an SMB2-Only negotiate message. This method will result in successful
negotiation only for servers that implement the SMB 2 Protocol. The footnote says: The Windows-based client will initiate a multi-protocol negotiation unless it
has previously negotiated with this server and the negotiated server's DialectRevision is equal to
0x0202, 0x0210, 0x0300, 0x0302, or 0x0311. In the latter case, it will initiate an SMB2-Only
negotiate. What might be happening is that your clients are attempting to reconnect to the Windows 2003 PDC (after an interruption in the TCP/IP connection) using an SMB2-Only negotiate message. Windows 2003 seems to just silently ignore this negotiate message, perhaps expecting the first SMB message on a new connection to always be a multi-protocol negotiation. If you issue a "net use" command on a client that can't connect, you might see something like:
New connections will not be remembered. Status Local Remote Network ------------------------------------------------------------------------------- Disconnected \\ay\c$ Microsoft Windows Network The command completed successfully. If you do see that, try issuing the command "net use \ay\c$ /d" for all of the connections to that server (e.g. "ray"). The reason for doing this is that the client remembers that it negotiated an SMB2/SMB3 connection with the server and skips the multi-protocol negotiation; removing all connections to the server also causes this "remembered" information about protocol capabilities of the server to be deleted. After this, it should be possible to re-establish connections to the Windows 2003 system. Please let us know what experiences you have with this approach - it would help to build a body of evidence for the problem. Gary
[d-parser.text.asis count="4-9"]
Другие запросы похожие на ищут: