Windows 10: Initial connection to workroup share fails, but succeeds after repeat?

I've just clean installed the first computer on our little office network to Windows 10 and I'm seeing some strange and unreliable behaviour for connecting to workgroup shares. We are not using domains or Microsoft accounts. The Windows 10 computer is just using a local account. I have given it the same username and password as it had before and it is part of the same workgroup.

Here's where it gets buggy and unreliable. When I go to the Network I can see the other Win7 computers that have files and folders shared. When I double-click on the computer it hangs and then reports that it could not connect and offers to Diagnose the problem. If I cancel Diagnose and try again it might, or might not, fail. However, after the 2nd or 3rd attempt, it comes up and I can see all the correct shared folders. It never asks for credentials as it seems to be pulling the local account details like it did before in Win7. When I try to connect to a shared folder it sometimes fails as well, but after repeating the attempt it then succeeds and everything is fine.

So the issue can be resolved by making repeated connection attempts to workgroup computers, but it often fails before resolving itself? It is slow and frustrating though.

Anyone else experiencing this? Any suggestions on how to improve the reliability and performance of Win10 connecting to Win7 workgroup shares?

I wonder if this has something to do with the changes they made to SMB in Win10?

:)

 

Error 0x000003e3 when trying to install a shared printer (Server 2012 R2) from a Windows 10 (winver 1703) computer

Open a shared printer prompts for Install Driver, then failed with error message:

• Cannot connect to printer
• The operation failed
• Error message 0x000003e3

This issue seems to only occur on some of the Windows 10 hosts after recent Windows update. Other hosts succeed in same action. The host experiencing this issue seems to have difficulties connecting to all shared printers even from different Windows Servers
(2012, 2012R2, 2016).

Removing entries under HKLM/System/CurrentControlSet/Control/Print/Drivers/Version 3 does not resolve this issue.

However, adding same network printer using TCP/IP connection directly was successful.

 

restart/updates

Ciao, there are some precedences among updates, so this means that if you update altogether, the newest will fail until the oldest succeeds. Can you please try again and check if, after each restart, some more new updates succeded? Please share the outcome.
Ciao and thanks Ugo