Map nextcloud (on truenas) folders to windows folders ON LOCAL NETWORK

[Pete_Dubler]

Nextcloud running on TrueNas on Proxmox
App Version: v31.0.5
Version: v1.6.29

I am running the Nextcloud Windows client and that works great when I am on or off of my local network. Just great for remote access to my Nextcloud folders/files. The thing is that it is way too slow when I am on my local network. I would like to just map some of my Nextcloud folders to drive letters on my Windows systems on the local network.

Of course I have read the Nextcloud documentation for mapping drives with windows explorer:

In the Windows Map Network Drive window, I use the following as the “folder”:

https://192.168.1.125/nextcloud/remote.php/dav/files/admin

(The documentation shows both ipaddress/nextcloud/remote.php… and ipaddress/remote.php… neither works)

I then get the login screen and enter the user admin and admin’s password. Then I get:
“The mapped network drive could not be created because the following error has occurred: The network logon failed”

Now I have confirmed that the password for admin is correct.

my TrueNas web interface instance is at http://192.168.1.125/ui/signin
the Nextcloud web interface is at https://192.168.1.125:30027/apps/dashboard/

Do I have to create a different user than admin for this to work?

Is there a way, under the truenas installation of nextcloud to assign a different IP address to the nextcloud so that we end up having the nextcloud and truenas instances at different IP addresses (not just different ports on the same IP address)?

Other things I should be looking at to solve this? (please don’t suggest the client app… that I already have running and, again, it works great going through my Cloudflare tunnel.. but when using from machines on the same lan as the truenas/nextcloud, I loose all of the advantage of my local network speed).

Thank you

[Pete_Dubler]

Wow. A month and a half and still no one can point me in the right direction on this?

[devnull]

Since access with the Nextcloud client works under Windows, it can be assumed that it is a Windows problem and not a Nextcloud problem. It is very likely that your Windows does not like the self-signed SSL certificate. This may be accepted in the browser, but possibly not in Windows directly.

Maybe you can test it manually:

net use Z: https://192.168.1.125/nextcloud/remote.php/dav/files/admin/ /user:admin password

Maybe you must change something in Windows registry. Read here.

You can also create a free Nextcloud account in the internet and test it with the WebDAV url. I think then you do not get an error because correct certificate CAs.

[bb77]

@Pete_Dubler

Of course I have read the Nextcloud documentation for mapping drives with windows explorer:

Did you also read this section? https://docs.nextcloud.com/server/latest/user_manual/en/files/access_webdav.html#id10

@Pete_Dubler

Is there a way, under the truenas installation of nextcloud to assign a different IP address to the nextcloud so that we end up having the nextcloud and truenas instances at different IP addresses (not just different ports on the same IP address)?

I don’t use it my self, but afaik, they introduced “per-app selection of IP addresses” with the release of TrueNAS 25.04 (Fangtooth): 25.04 (Fangtooth) Version Notes | TrueNAS Documentation Hub

@Pete_Dubler

Other things I should be looking at to solve this? (please don’t suggest the client app… that I already have running and, again, it works great going through my Cloudflare tunnel.. but when using from machines on the same lan as the truenas/nextcloud, I loose all of the advantage of my local network speed).

Could possibly be solved with a reverse proxy and a proper split-brain DNS setup.

[Pete_Dubler]

thanks @devnull