Windows 10: file name too long for mapping a network drive error

When ever i am trying to map a network drive it is showing file name of the path is too long. reduce the characters and try again

:)

 

Trouble Mapping Network Drive

I have a WD NAS drive connected to my router and have mapped it on three of my computers. I just setup another laptop with Windows 10 and have updated it to 1809 and when I tired Mapping a network drive nothing is displayed in the browse window except the
computer I am currently using. The drive is shown under network locations in File Explorer but not when you select map network drive and browse. I right clicked on the drive and selected properties and noted the IP address and went back into Map network drive
but instead of selecting browse I entered the IP address but it still does not map the drive. The strange part is if I go to any of the computers that already has the network drive mapped and select Map network drive and select browse none of those computers
show the drive either but you can select the mapped drive in the drive list in file explorer and it works just fine.

I have read several articles both here and elsewhere and tried the suggestions but nothing works. Network discovery is turned on as is file sharing and also checked if all three boxes under SMB file sharing support in Windows features were also checked and
they are. I have mapped several computers to several different drives over the years and anytime the drive was not listed it was always easy to go into Network Sharing Centre and find the problem but everything seems to be as it should so would appreciate
if someone can suggest something I may have overlooked.

Thank you

 

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.

 

'Directory name is invalid' when trying to access files on mapped network drive

The file server on this local area network is running Windows Server 2012.

On any of the Windows 7 (Pro 64-bit) PCs on this network, when trying to double-click on a file on a mapped network drive, the error 'The Directory Name is invalid' is displayed and the files cannot be opened.

Opening the same files on the mapped drive by first running their respective applications and then selecting 'Open' opens any of the files fine, as does using 'Open with' and then choosing the relevant application, as does copying the files from the mapped
drive to a local drive and then using double-click.

I would be grateful if someone can solve this mystery for me.

Regards