- May 19, 2011
- 17,577
- 9,268
- 136
I just sorted a problem for a customer that had me scratching my head for quite a while: Small business, network-connected photocopier and a bunch of Windows PCs. The photocopier is set up to send scanned documents via Windows filesharing services to whichever PC the user wants. The copier worked with all the other PCs except one. That one PC is running Win10 1809, newer than any of the others (some 1803, some Win7). That PC had no problem allowing other clients to connect but not the copier ("The network path cannot be found", said copier).
Long story short, I ran a packet sniffer and found the copier was in fact connecting to the PC in question, sent a negotiation packet which didn't include SMB support (in response to the problem I had configured the copier to use NTLM and port 445), and the PC responded by closing the connection. I then read up on enabling SMB 1.0 support, which did the trick.
What I'm puzzled about those is why this has only just become a problem. From what I've read, 1709 removed SMB 1.0 support yet here are 1803 PCs without any prior problems with the copier. I thought it might have been an 1809 change, but the copier definitely worked with that PC after the 1809 update. I even removed a cumulative update that occurred after 1809 that coincided nicely with the problem starting, still nothing.
Any ideas what might have triggered the problem?
Long story short, I ran a packet sniffer and found the copier was in fact connecting to the PC in question, sent a negotiation packet which didn't include SMB support (in response to the problem I had configured the copier to use NTLM and port 445), and the PC responded by closing the connection. I then read up on enabling SMB 1.0 support, which did the trick.
What I'm puzzled about those is why this has only just become a problem. From what I've read, 1709 removed SMB 1.0 support yet here are 1803 PCs without any prior problems with the copier. I thought it might have been an 1809 change, but the copier definitely worked with that PC after the 1809 update. I even removed a cumulative update that occurred after 1809 that coincided nicely with the problem starting, still nothing.
Any ideas what might have triggered the problem?