Unable to access via SMB...strange

[g7rpo1]

Hi

Not sure what is happening here

I have 2 104s, both running 6.10.1

predominently in a windows 10 environment

AD domain both AD servers running 2k12r2

Authentcation is set to AD

names are NAS-01 and NAS-02

NAS-02 is working absolutely fine but 01 will not let me get to any SMB shares

can connect to the web interface and via ssh, all seems happy but will not connect at all.

I have factory reset which acheived nothing and also did a fw install with the same outcome.

Any ideas would be greatly appreciated.

Can ping by name and IP

[StephenB]

• Does this happen with multiple PCs, or just one? 
• Are the NAS hosting different shares, or are they identical?
• Are you accessing the NAS by hostname or by IP address?

If you are using hostname, then perhaps try shifting to IP address.

Also, did you try connecting with net use?  It might give you more clues

net use * /delete
net use t: \\nas-ip-address\sharename /user=username userpassword

[g7rpo1]

Hi

It is accross 4 windows 10 machines  (2 vms and 2 physical)

Also the 2 windows 2k8r2 servers are unable to get to the shares.

Both boxes are being used to store different things

I have upgraded to 6.10.2 which has at least allowed me to connect via UNC using IP addresses, hostname still doesnt want to play tho.

I have successfully mapped them to drive letters using IP so not as urgent as initial post but thanks for getting back to me

[StephenB]

---

@g7rpo1 wrote:

I have upgraded to 6.10.2 which has at least allowed me to connect via UNC using IP addresses, hostname still doesnt want to play tho.

---

Hostname failing is a pretty common issue, but unfortunately not one that we've seen a solid fix for.  Many folks have either just used IP addresses or put the name in the HOSTS file on the client PCs.

You might want to check the "Legacy Windows Discovery" setting in system->settings->smb on both NAS, and see if it is set the same way on both systems.  Are both set up the same way in DNS?  

[g7rpo1]

Legacy windows discovery is already checked on both boxes.

Both are set up to get IP via a DCHP reservation on MS DHCP server, have tried changing the network settings to manual, mirroring the DCHP ones and no difference.

Luckily the box is used for storage only and nothing on there is needed day to day so the hosts file solution is probably my best option