Windows 10: Server 2003 + Win 10 Pro Mapped Drive Issue

Hello all, I have 8 windows 10 PCs, all identical, a Windows 7 Pro machine with 1 shared folder and a Windows Server 2003 which shares 3 folders. All PC's have access to server shares with their own username/password. Windows 7 PC doesn't require a login.Only 2 machines have an issue where the mapped drives sometimes don't open after a restart or shutdown/turn on of the workstation. The issue is intermittent, sometimes I can restart the PC 10 times and everything works fine, I can access the mapped drives on server and Win 7 PC. But the other times I cannot access the shared folders on the ser

:)

 

Mapped Drives Issues

To clarify .... the issue is the Windows 10 OS. It is with Windows File Explorer. The Mapped drives used to appear in File Explorer's left panel list of drives and folders. Two days ago File explorer stopped show the mapped drives. so not they don;t appear in the list of Drives and folders.

- - - Updated - - -

I did, it has no effect. I also check the NAS devices they support SMB 2.0. Also I have several other computers on my home network they work fine with the mapped drives and They do not have SMB 1 turned on. So it is something that happened to the computer in question.

 

GPO Mapped network Drives mapping in Win 10 but not Win 7


I have a medium sized network running. We are currently migrating and updating our shared folder systems. The old system is running Win 2k8 R2 and still has the old mapped drives running what we haven't migrated. The new shared folders are on a new server Win 2012 R2 with a different folder structure and everything. Half the computers in the building run Win 7 Pro and the other half Win 10 Pro. Here is my issue. On every single Win 10 computer every drive maps and can be accessed normally, however the new shared drive DOES NOT map to any Win 7 machine. I created a Hyper V win 7 machine and on my Win 10 machine I have all my folders however when I log into that Win 7 machine only the home drives(located on the new share server) and the old shared drives seem to map. I have switched the Drive Maps to Update Create Replace, I have checked all permissions even though it seems not permission related as I can get to it on any win 10 machine. Any advice?*Mad*Mad*Mad*Mad*Mad*Mad*Mad

 

Windows 10 2004 Enterprise - will not run logon script when mapping drives to 2003 server using SMB1

First off, I am pushing to get the old 2003 server replaced, that is being held up due to economic reasons. Up to the 2004 update the logon scripts ran fine and mapped drives to various servers - 2003, 2008,2012,2016. When 2004 is installed the logon
scripts stall at the mapping command. But only on our corporate sites that are mapping drives to old Windows 2003 servers that uses SMB1. The map portion of the script will take 15 minutes to complete. Each map progresses slowly like molasses.

Testing this I found if I do a manual UNmap before the next reboot ( net use * /d /y ) it takes about 10 minutes to complete. On the next reboot the logon script runs fine and all connections are available - but subsequent reboots stall on the script.
Drives to the 2003 server are not available during the the time the logon script is running and stalled, nor after it completes the run, the drives show disconnected.

If I remove mapping commands to the 2003 server the script runs fine, add them back and it stalls again.

SMB 1 IS installed on the PCs and the script currently works on 1909 machines and maps to the old 2003 server.