I have a FreeNAS file server set up for the house. The wife's computer just refuses to connect to it sometimes (shares via SMB). Today she figured that the share stops working when she starts up Cricut Design Space. Let's not talk about what a hot mess the Cricut app really is and just concentrate on why it's blocking access to the FreeNAS server.

Any idea why an online cloud application would disallow a connection to a shared folder mapped to a drive in Windows 10?

I cannot answer your question because, as I noted in another recent MS-Win10 thread, I don't use it. But I will say this:

MS-Windows, at least as of MS-Win7 (probably Vista, but I never touched that, either), finally properly separated Administrator access from User access. Assuming one had enough sense not to configure users with Administrator rights: Theoretically speaking: No user would have the ability to affect the connectivity of remote file shares and drive mapping created by the Administrator. Thus no application users without Administrator rights ran would have the ability to do so, either.

Theoretically.

quote:

Originally posted by ensigmatic:
I cannot answer your question because, as I noted in another recent MS-Win10 thread, I don't use it. But I will say this:

MS-Windows, at least as of MS-Win7 (probably Vista, but I never touched that, either), finally properly separated Administrator access from User access. Assuming one had enough sense not to configure users with Administrator rights: Theoretically speaking: No user would have the ability to affect the connectivity of remote file shares and drive mapping created by the Administrator. Thus no application users without Administrator rights ran would have the ability to do so, either.

Theoretically.

That's interesting. I'll have to look into the admin rights.

What revision of SMB?
IIRC Win 10 supports 3.1
Other version must be enabled and are generally considered a security risk... At least SMB 1 is.

Search enable SMB on Windows 10.


Billy

quote:

Originally posted by BillyBonesNY:
What revision of SMB?
IIRC Win 10 supports 3.1
Other version must be enabled and are generally considered a security risk... At least SMB 1 is.

Search enable SMB on Windows 10.


Billy

^^^^ This ^^^^

quote:

Originally posted by mark123:

quote:

Originally posted by ensigmatic:
I cannot answer your question because, as I noted in another recent MS-Win10 thread, I don't use it. But I will say this:

MS-Windows, at least as of MS-Win7 (probably Vista, but I never touched that, either), finally properly separated Administrator access from User access. Assuming one had enough sense not to configure users with Administrator rights: Theoretically speaking: No user would have the ability to affect the connectivity of remote file shares and drive mapping created by the Administrator. Thus no application users without Administrator rights ran would have the ability to do so, either.

Theoretically.

That's interesting. I'll have to look into the admin rights.

Yeah, don't think this is an admin rights issue.
You can be an admin on a local computer but that doesn't give you any rights on another.

quote:

Originally posted by smschulz:

quote:

Originally posted by mark123:

quote:

Originally posted by ensigmatic:
I cannot answer your question because, as I noted in another recent MS-Win10 thread, I don't use it. But I will say this:

MS-Windows, at least as of MS-Win7 (probably Vista, but I never touched that, either), finally properly separated Administrator access from User access. Assuming one had enough sense not to configure users with Administrator rights: Theoretically speaking: No user would have the ability to affect the connectivity of remote file shares and drive mapping created by the Administrator. Thus no application users without Administrator rights ran would have the ability to do so, either.

Theoretically.

That's interesting. I'll have to look into the admin rights.

Yeah, don't think this is an admin rights issue.
You can be an admin on a local computer but that doesn't give you any rights on another.

Yeah, I don't think I'm explaining it correctly. We can attach to the share as a mapped drive but when you start the Cricut design space you can't get into the mapped drive any longer.

This message has been edited. Last edited by: mark123,

Have you tried mapping a different drive letter to the NAS? Not that it should make a difference, but I have seen some poorly written software (albeit long ago) that wouldn't work with certain drive letters for some reason. This is assuming you are actually mapping drive letters of course. Just a thought.

quote:

Originally posted by mark123:
Any idea why an online cloud application would disallow a connection to a shared folder mapped to a drive in Windows 10?

Copy protection?

quote:

Originally posted by architect:

quote:

Originally posted by mark123:
Any idea why an online cloud application would disallow a connection to a shared folder mapped to a drive in Windows 10?

Copy protection?

Not copy protection but it may be that the program itself doesn't know how to look at local network connections or just that it only can look locally at the computer.
Unless he is saying that the mapped drive itself is also inaccessible through the file explore once the program starts up.
If the latter is the case then it is a networking issue.
If the former it is most likely a design issue with the program.

I would also look at the firewall policies as well.

It's the mapped drive that becomes inaccessible.

W10 doesn't play well with SMB.

Had a nice Sigforum NAS (karma) that i enjoyed trouble free until i introduced W10 into my network.

Took me some time to figure out the issue and solving it by MANUALLY enabling BACK SMB on W10.
It got disabled by one of the earlier updates.

Then, every now and then, another update would mess with my settings once again.

Fook W10. Whose network is it anyways? Mine or theirs? Fook it!

0-0

Sometimes it works as expected though.

I feel I'm not explaining the problem properly.

quote:

Originally posted by smschulz:
Yeah, don't think this is an admin rights issue.
You can be an admin on a local computer but that doesn't give you any rights on another.

You wouldn't need rights on another device to unmap a drive on a local machine.

quote:

Originally posted by mark123:
It's the mapped drive that becomes inaccessible.

This is what I originally understood you to mean.

Is the share still visible and accessible via the UNC? (I presume so.)

quote:

Originally posted by ensigmatic:
Is the share still visible and accessible via the UNC? (I presume so.

That's a good question. I'll have to try to get it to fail and then try that instead. But we both know it won't happen while I'm trying to make it happen.

quote:

Originally posted by mark123:
Sometimes it works as expected though.

That information actually is significant.
So if it works intermittently and by "works" I mean that you can access whatever data to upload or run offline through the program interface like open, import or whatever nomenclature the program uses THEN that appears to be a network issue or could be a firewall issue or browsing issue.

Network issue: check in File Explorer that no red X is on the connection as the mapped drive can get disconnected for a variety of reasons. If so then "click" on it to reconnect.

Firewall issue: make sure the profile is not set to public.

Browsing issue: SMB share browsing is a phenomena all in it's own by browsing I mean when the share is visible on the network. Sometimes it takes a while for this to occur but it doesn't mean the connection isn't there or isn't working. Generally a mapped drive will mean you don't have to worry about this but I have seen programs that don't have a good way to browse for network connections and if you have to drill down in a window to find the connection it can not always be visible.

quote:

Originally posted by ensigmatic:


Is the share still visible and accessible via the UNC? (I presume so.)

Never presume but the UNC is a good point.

I'm not even talking about the program accessing it. The mapped drive becomes unaccessible in the file browser. It's no longer connected. The mapped drive has the red x. Today it's been steady and accessible. I can't replicate. I'll have to get the wife to do her process.

Oh, by the way, when you say UNC you mean Run -> \\servername\sharename (that was my guess).

quote:

Originally posted by mark123:
I'm not even talking about the program accessing it. The mapped drive becomes inaccessible in the file browser. It's no longer connected. The mapped drive has the red x.

It's why we have to keep asking questions to get the proper data.
Thank you for the info.

Click on it to reconnect, this happens from time to time for various reasons but it should resolve the issue.
I have this occasionally happen but this quickly fixes it and it usually doesn't happen often unless there is a network interruption, power outage etc as the clients servers are always on.
I have never researched the "why" as the fix is simple and easy to train users on.
It wasn't critical enough to spend a lot of time on, IMO.
If it will not reconnect when you click on then we can take it from there.

quote:

Oh, by the way, when you say UNC you mean Run -> \\servername\sharename (that was my guess).

Yes, you can also access (best) through the file manager.