NAS not accepting connection

[F]

Despite being able to log into it from a browser, one of my NAS boxes
running FreeNAS-9.10.2-U2 (e1497f2) is refusing connections from Windows
Explorer on Windows 10. Windows diagnostics comes up with:

'The remote device or resource won't accept the connection Detected
Detected

The device or resource (192.168.178.101) is not set up to accept
connections on port "The File and printer sharing (SMB)".
Contact your network administrator Completed

The computer or device you are trying to reach is available, but it
doesn’t support what you’re trying to do. This might be a configuration
issue or a limitation of the device'.

The only problem I can see from logging into it is it reports 'The
capacity for the volume 'NAS_2' is currently at 96%, while the
recommended value is below 80%'.
Could this be relevant? If it is, how do I delete files if I can't get
access through Windows Explorer?

Anyone got any thoughts?

--
F

[Rob Morley]

On Fri, 17 Mar 2017 15:12:41 +0000
F <news@nowhere> wrote:

> Despite being able to log into it from a browser, one of my NAS boxes
> running FreeNAS-9.10.2-U2 (e1497f2) is refusing connections from
> Windows Explorer on Windows 10. Windows diagnostics comes up with:
>
> 'The remote device or resource won't accept the connection Detected
> Detected
>
> The device or resource (192.168.178.101) is not set up to accept
> connections on port "The File and printer sharing (SMB)".
> Contact your network administrator Completed
>
> The computer or device you are trying to reach is available, but it
> doesn’t support what you’re trying to do. This might be a
> configuration issue or a limitation of the device'.
>
> The only problem I can see from logging into it is it reports 'The
> capacity for the volume 'NAS_2' is currently at 96%, while the
> recommended value is below 80%'.
> Could this be relevant?

The system should reserve enough space to allow root login even when
the filesystem is reported full, but maybe it's not managing to launch
SMB services.

> If it is, how do I delete files if I can't
> get access through Windows Explorer?

SSH in as root and do it on the command line? Failing that is there a
serial console connection available?

[Mark]

Can you delete files through the web interface?

[F]

Thanks for the suggestion. I've now done that and deleted ~600GB of
files but the web interface is still reporting it's at 96% capacity and
overnight the box has emailed to say 'Snapshot
NA...@auto-20170318.0100-4w failed with the following error: cannot
create snapshots : out of space'.

There are four 2TB drives in there using ZFS, but I can't remember/see
which version. 'Volumes' shows NAS_2, Used 7.0TiB (96%), Available
231.7GiB and, on an indented second row, NAS_2, Used 5.1TiB (100%),
Available 0, Read only inherit (off).

Under 'Reporting - Partition', Disk space (NAS_2) shows 0.0 B free
across the four listings and 3.6TB used across all four listings and the
red shading in the graph is level at 3.6GB.

Disk space (/) shows 10.6GB free across all four listings and 1.1GB used
across all four listings. The green area of the graph reaches 12GB and
the red area 1GB

Are there any clues there?

As may be obvious, I've got next to nothing by way of understanding what
goes on with FreeNAS. I just back up to the box!

--
F

[Jaimie Vandenbergh]

On Sat, 18 Mar 2017 12:58:27 +0000, F <news@nowhere> wrote:

>Thanks for the suggestion. I've now done that and deleted ~600GB of
>files but the web interface is still reporting it's at 96% capacity and
>overnight the box has emailed to say 'Snapshot
>NA...@auto-20170318.0100-4w failed with the following error: cannot
>create snapshots : out of space'.

You've got snapshots set to automatically happen, which means deletion
doesn't actually free up space until the snapshots expire or you clean
them out yourself.

Go to the webUI, "Storage", "Snapshots", and take a look at the NAS_2
volume snapshots in the list - you should be able to spot the ones which
are holding on to lots of gigs in the "Used" column.

You can multi-select several with tickboxes, then pick the destroy icon
at the bottom. It may take a few minutes to complete. You'll get your
free space back after.

>As may be obvious, I've got next to nothing by way of understanding what
>goes on with FreeNAS. I just back up to the box!

You didn't set this up, and the person who did isn't available?

Take a look under "Periodic snapshot tasks" and make sure it's not
storing them indefinitely, or taking too many. I take one a day and keep
them for ten days, myself. But if you aren't aware of how to use them,
they may be completely pointless - I wouldn't disable this without
checking with your support human though.

Cheers - Jaimie
--
"Hard as nails, hard as nails - So would you be if you lived one hundred
and eighty years on sunflower seeds and biscuit crumbs." - Polynesia

[F]

On 18/03/2017 13:46, Jaimie Vandenbergh wrote:
> On Sat, 18 Mar 2017 12:58:27 +0000, F <news@nowhere> wrote:
>
>> Thanks for the suggestion. I've now done that and deleted ~600GB of
>> files but the web interface is still reporting it's at 96% capacity and
>> overnight the box has emailed to say 'Snapshot
>> NA...@auto-20170318.0100-4w failed with the following error: cannot
>> create snapshots : out of space'.
>
> You've got snapshots set to automatically happen, which means deletion
> doesn't actually free up space until the snapshots expire or you clean
> them out yourself.
>
> Go to the webUI, "Storage", "Snapshots", and take a look at the NAS_2
> volume snapshots in the list - you should be able to spot the ones which
> are holding on to lots of gigs in the "Used" column.
>
> You can multi-select several with tickboxes, then pick the destroy icon
> at the bottom. It may take a few minutes to complete. You'll get your
> free space back after.
>
>> As may be obvious, I've got next to nothing by way of understanding what
>> goes on with FreeNAS. I just back up to the box!
>
> You didn't set this up, and the person who did isn't available?
>
> Take a look under "Periodic snapshot tasks" and make sure it's not
> storing them indefinitely, or taking too many. I take one a day and keep
> them for ten days, myself. But if you aren't aware of how to use them,
> they may be completely pointless - I wouldn't disable this without
> checking with your support human though.

Thank you! Snapshots sorted and capacity is now down to 83%.

I set the box up quite some time ago now, but did it by following a
YouTube video. So no real understanding: I was just following orders...

The access problem remains though. It is still refusing connections from

Windows Explorer on Windows 10. Windows diagnostics comes up with:

'The remote device or resource won't accept the connection

Detected

The device or resource (192.168.178.101) is not set up to accept
connections on port "The File and printer sharing (SMB)".
Contact your network administrator Completed

The computer or device you are trying to reach is available, but it
doesn’t support what you’re trying to do. This might be a configuration
issue or a limitation of the device'.

Would shouting at it have any effect? Chocolate?

--
F

[Mark]

;-)

ICBW but Windows firewall (IME) often blocks too much. Maybe playing
with the settings could help?

Also search for "The remote device or resource won't accept the
connection" - you might find something useful.

Also are you sure that your FreeNAS is set-up properly? (i.e. with
valid Windows shares).

[Jaimie Vandenbergh]

On Sat, 18 Mar 2017 14:34:06 +0000, F <news@nowhere> wrote:

Good work anyway, they're not the least complex of devices. Apparently
v10 has just come out with a new UI, I'm going to experiment with it
shortly on my second NAS.

>The access problem remains though. It is still refusing connections from
>Windows Explorer on Windows 10. Windows diagnostics comes up with:
>
>'The remote device or resource won't accept the connection

Ah! Sorry, meant to point you in the right direction for this too.

WebUI, "Services", "Control Services", make sure SMB is enabled. If is,
flip it off and non again :)

If that doesn't work, take a look under "Services", "SMB" - did you set
up an account on the FreeNAS as the default for filesharing? If so, make
sure that's selected in the "Guest account" dropdown. Also that "server
minimum protocol" and the matching max are set to something reasonable.
Mine are "------" and "SMB3", for reference.

>The device or resource (192.168.178.101) is not set up to accept

Check that's the IP address your NAS is actually at, too (it's a funny
one...), in "Network", "Global Config"

Cheers - Jaimie
--
"In my opinion, we don't devote nearly enough scientific research
to finding a cure for jerks." -- Calvin/Bill Watterson

[Mark]

Check out
https://doc.freenas.org/9.3/freenas_sharing.html#windows-cifs-shares

[F]

On 18/03/2017 14:43, Jaimie Vandenbergh wrote:
> On Sat, 18 Mar 2017 14:34:06 +0000, F <news@nowhere> wrote:
>
>> 'The remote device or resource won't accept the connection
>
> Ah! Sorry, meant to point you in the right direction for this too.
>
> WebUI, "Services", "Control Services", make sure SMB is enabled. If is,
> flip it off and non again :)

It did! How bl**dy annoyingly simple.

Thank you again: appreciated!

--
F

[Jaimie Vandenbergh]

NP - always worth a try. I've never seen FreeNAS9 crash Samba before,
but there's always a first time.

I've been experimenting with FreeNAS10 (or rather FreeNAS Corral), and I
don't recommend this .0 release, it's pretty buggy in the UI department.
Give it a few months.

Cheers - Jaimie
--
"I have an asteroid named after me. Isaac Asimov's got one too.
It's smaller and more eccentric." -- Arthur C. Clarke

[newshound]

I know that feeling too!

>>
>> ;-)
>>
>> ICBW but Windows firewall (IME) often blocks too much. Maybe playing
>> with the settings could help?
>>
>> Also search for "The remote device or resource won't accept the
>> connection" - you might find something useful.
>>
>> Also are you sure that your FreeNAS is set-up properly? (i.e. with
>> valid Windows shares).
>
> Check out
> https://doc.freenas.org/9.3/freenas_sharing.html#windows-cifs-shares
>
>

The Freenas documentation is very detailed and comprehensive, but a bit
terse. The problem I have found with it is that almost every instruction
seems to introduce a new term that I don't really understand.

Example from that link:

FreeNAS® uses Samba to share volumes using Microsoft’s CIFS protocol.

Actually I do (sort of) know what Samba is, because I have met it
before. But I keep feeling I could really do with an "idiots guide" that
tries to define new terms in slightly simpler words. I don't expect the
good people who write the FreeNAS support to educate everyone from
scratch, I'd by happy to buy a "dictionary for idiots".

I find the trouble with most of the "Dummies" books is that they don't
really explain stuff that well either, they guide you through the menus,
but when the menus have been revised slightly they leave you completely
stuck.

[F]

On 19/03/2017 12:41, newshound wrote:

> The Freenas documentation is very detailed and comprehensive, but a bit
> terse. The problem I have found with it is that almost every instruction
> seems to introduce a new term that I don't really understand.
>
> Example from that link:
>
> FreeNAS® uses Samba to share volumes using Microsoft’s CIFS protocol.

Or 'sets the ACLs to allow read/write for owner/group and read-only for
others; should only be unchecked when creating a share on a system that
already has custom ACLs set'.

Eh?

--
F

[Mark]

I doubt many home users will make use of ACLs.

[newshound]

At least that one is easy to look up. And actually, might not someone
with teenage children decide to use Access Control Lists? Mine all up
and left home before I had to worry about such things.

[Jaimie Vandenbergh]

Nah, you'd set up whole shares controlled by user login+pass instead.

No-one wants to manage ACLs without an AD or LDAP or similar to make it
sensible.

Cheers - Jaimie
--
"We all recall that the difference between a computer salesman and a car
salesman is that the car salesman *knows* he's lying to you"
"... and probably knows how to drive"
- F O'Donnell and M Smith, in afs

[newshound]

On 3/19/2017 4:57 PM, Jaimie Vandenbergh wrote:
> On Sun, 19 Mar 2017 15:15:58 +0000, newshound
> <news...@stevejqr.plus.com> wrote:
>
>> On 3/19/2017 2:10 PM, Mark wrote:
>>> On Sun, 19 Mar 2017 13:55:13 +0000, F <news@nowhere> wrote:
>>>
>>>> On 19/03/2017 12:41, newshound wrote:
>>>>
>>>>> The Freenas documentation is very detailed and comprehensive, but a bit
>>>>> terse. The problem I have found with it is that almost every instruction
>>>>> seems to introduce a new term that I don't really understand.
>>>>>
>>>>> Example from that link:
>>>>>
>>>>> FreeNAS® uses Samba to share volumes using Microsoft’s CIFS protocol.
>>>>
>>>> Or 'sets the ACLs to allow read/write for owner/group and read-only for
>>>> others; should only be unchecked when creating a share on a system that
>>>> already has custom ACLs set'.
>>>
>>> I doubt many home users will make use of ACLs.
>>>
>> At least that one is easy to look up. And actually, might not someone
>> with teenage children decide to use Access Control Lists? Mine all up
>> and left home before I had to worry about such things.
>
> Nah, you'd set up whole shares controlled by user login+pass instead.
>
> No-one wants to manage ACLs without an AD or LDAP or similar to make it
> sensible.
>
> Cheers - Jaimie
>

I certainly bow to your experience. I'm very glad to say that I have
*never* had to worry about setting up such things!