FreeNAS and Windows 10

[Axe]

I've spent many hours (and days ) on this to no avail. I've also read many websites and tried a number of methods to fix the problem I'm having with no success. My Win 7 PC's work perfectly. I cannot get my Windows 10 PC's (all/ 2 of them) to find my Freenas server. I can connect via web-browser to the NAS re: admin stuff.

I have enabled net bios, guest users, and other tried other things including changing settings in the registry (as per advice).

I am not that stronger a user of FREENAS but I just don't know what else I can do.

Please help and many thanks,

 

[Ericloewe]

You have two options:

1. Set up proper DNS to avoid dealing with NetBIOS
2. Give up and use the bare IP address.

 

[Axe]

You have two options:

1. Set up proper DNS to avoid dealing with NetBIOS
2. Give up and use the bare IP address.

Thanks for the reply. Set NetBIOS back to to defaults. It is beyond my understanding what you meant by 'proper DNS' and 'bare IP address' although I'll look those up. I essentially setup my server (quite a steep learning curve with trial and error on the way) and rest has been left on defaults (W10) Regards,

 

[Ericloewe]

'bare IP address'

Your server has an IP address. Type it in. \\IP_ADDRESS

 

[Axe]

Yes, I have tried that already a number of times but it doesn't work.
Tried:
\\IP
\\FREENAS
\\FREENAS\SHARE

 

[anodos]

Yes, I have tried that already a number of times but it doesn't work.
Tried:
\\IP
\\FREENAS
\\FREENAS\SHARE

So if your freenas server's IP address is 192.168.0.10, you can go to HTTP://192.168.0.10 to connect to the webgui, but you cannot go to \\192.168.0.10 to connect to your samba shares?

Turn off the windows firewall and try again.

BTW, you should never need to manually make registry changes.

 

[Axe]

So if your freenas server's IP address is 192.168.0.10, you can go to HTTP://192.168.0.10 to connect to the webgui, but you cannot go to \\192.168.0.10 to connect to your samba shares?

Turn off the windows firewall and try again.

BTW, you should never need to manually make registry changes.

Yes, that is correct. I have no such issues/problems with Windows 7. I use Kaspersky Internet Security and even after shutting that down down I still have the same problem. I've applied all updates for Windows 10 and FreeNAS is on the most recent stable release (with applied updates). The error I get is:

'The mapped network drive could not be created because the following error has occurred:
The file cannot be accessed by the system'

This issue is driving me nuts and I really don't wish to reinstall Windows 7 on my PC (although I do prfer W7 to W10) as it is setup how I like and I do not wish to spend ages reinstalling all the software and changing settings again.

 

[Axe]

I admit I still have a steep learning curvel for FreeNAS (and other relevant software like rsync, using SSH etc.) but the fact I've managed to setup shares... does demonstrate, I think, I am capable. Always was, and in many ways still am, a Windows user.

 

[Axe]

Managed to get it to work after spending many hours and days on this problem. I'd been letting Windows install updates but did not upgrade (didn't know/pay attention to) the fact Windows 10 Aniversary update hadn't been installed on my PC since there was no prompt or download on my PC and all updates as requested were applied. I installed it manually and now my NAS is detected on both PCs with W10. As a precaution, I reset 'Network' cards part of W10; it was after all a windows issue.

What I will take from this, and it has wet my appetite, is to learn more about the functions of FreeNAS and learn more advanced things related to this. I was highly tempted to go to Windows Server 2012 R2 as I am familiar with Windows and I do not, and did not, anticipate the jump to be as steep as going to FreeNAS.

Thanks all for your help.