#QFINDER CANNOT MAP DRIVE CODE#

I disconnected the drive, rebooted and reconnected the folder (within Explorer still) using the static IP address and shared folder drive name. Log on to the remote client workstation as a valid user with shared directory access to the code server. Even a Windows reinstall cannot be considered since the second computer was built last week, and already has the same behavior. I have a more complicated setup at home running mapped drives (through my server and a QNAP TS-212, with various W10 versions) without having the same behavior. Did try to dig through the Registry and find equivalent changes to the Drive Mapping in GPO, but to no avail.Īny network gurus around? I know a few of us use Windows and QNAPs. also CMD prompts to disable Autodisconnect made no difference. Usual resolutions fall within GPO changes to Drive Mappings ('Update' instead of 'Delete') - but since both computers run on W10 Family, no GPO access. I've done some research on the subject Microsoft decided since W8 to disconnect idling drives to save network bandwidth. Only way to reconnect is to reboot the NAS - which is a pain. After some time (difficult to evaluate, since it varies - usually within a couple of hours), the drive disconnects. Credentials are recognized, mapped drive folders are accessible. The mapped drive connection is made either through the Map Drive function in Explorer, or using QFinder (QNAP's software). Same domain, private network, sharing on. I have a customer with a simple network - a DIR-655 router, 2 computers running latest W10 Family build (custom builds by yours truly), and a QNAP TS-112 NAS.

Qfinder cannot map drive