Forum Discussion

Tutor

Oct 20, 2017

RN314 OS 6.8.1 - Win10 Pro 64-bit Fall Creator 1709 - Can't access Shares

A few days ago I have created a new instance of Win 10, and this has just upgraded to Win10 1709 Fall Creator.

Before upgrading to 1709 the instance was connected to the shares, and the shares were mapped as drives with drive letters.

After the update to 1709 it can't connect to the shares on my NAS.

My old Win10 instance (on different partion) can still connect fine to the shares.

My new Win10 in connected to an MS Work Account using Office 365, that means using Active Directory.

My old was not using AD.

My NAS uses the authentication access type Local users, and has done this all the time.

Hence when usually establishing connection to the NAS, I am using the NAS-defined username and password, and this has worked fine.

I have done some searching, and based on this tried using the SMB Plus app on the NAS, and there tried to adjust SMB-versions etc.

This changes the types of errors I get when trying to view/connect to shares, but it does not make accessing shares possible.

I have also looked in to the Win-setting for IPv4 (NetBios). It is set as standard, and the same way as on the functioning Win10 instance.

To me this appears to be clearly RELATED to the windows update.

Any hints on what to do/try, before I consider opening a support case?

File Sharing

43 Replies

Replies have been turned off for this discussion

Sandshark
Sensei - Experienced User
Oct 20, 2017
Is your user name the same on the PC and NAS but the password is not? If so, the PC is likely presenting the AD credentials to the NAS, which is refusing them. You should be able to correct that by deleting the mapped drives and re-mapping them using Connect using different credentials.
- WarCon
  Tutor
  Oct 20, 2017
  I (usually) connect the drives as you describe (using different credentials), as I have always had different usernames on the PC and the NAS.
  
  (This was what I meant with this: "Hence when usually establishing connection to the NAS, I am using the NAS-defined username and password, and this has worked fine.")
  - Sandshark
    Sensei - Experienced User
    Oct 20, 2017
    Can you access it by typing the NAS address or name and share name (//xxx.xxx.xxx.xxx/Share or //NasName/Share) into a Windows Explorer address bar? If not, what is the error message?
kohdee
NETGEAR Expert
Nov 08, 2017
You can get Windows to force credentials either via Mapped Network Drive or using Windows Credential Manager
- evan2
  NETGEAR Expert
  Dec 13, 2017
  the root cause is Win10 1709 doesn't allow access SAMBA using guest accout,
  
  it try to access NAS using windows login account and password,
  
  if you add a same account on NAS, you may access NAS, and you will find it login using the windows login account,
  
  6.9.2 T build has fixed the issue.
  
  if not all shares disable guest access, set "map to guest = bad user" in smb config,
  
  if all shares disale guest access, set "map to guest = never" in smb config.
  
  Note: if set "map to guest = never", Windows will pop-up login page to let user input user name and password,
  
  Win10 1709 want to access NAS via Samba,
  
  all shares need to disable guest access on NAS.
  - StephenB
    Guru - Experienced User
    Dec 13, 2017
    evan2 wrote:
    
    Win10 1709 want to access NAS via Samba,
    
    all shares need to disable guest access on NAS.
    
    Using credentials on all the windows systems works too, and would allow SMB guest access for other devices (older media players for instance).