Question

Setting up a volume in a Host allocated on a different Domain

Laserfiche How To Version 11 Discussions

Updated December 29, 2021

asked on December 28, 2021

I have the following situation:

My laserfiche server is running on Host A, within its own domain "Domain A" and I need to have a volume stored in Host B, but it is located in another domain "Domain B". (Both hosts running windows)

By request, the connection cannot be a simple SMB mounted drive.

So far, I have tried mapping a network drive through SSH with the help of SSHFS for windows. I was able to map the drive, but I ran into some troubles with user permissions.

I would like to know if anyone has tried this sort of configuration. Even better if anyone has succeeded.

The methodology (or protocols implemented) does not need to be the same one I have already tried, if there are some other approaches to this situation, I would also like to try them.

0 0

Replies

replied on December 29, 2021

Hi David,

Thinking about this, the LF system will connect to the volume using whatever the Laserfiche Server Service is running as, which in your scenario I'm guessing would be an account on Domain A, as that likely has the relevant permissions in SQL (ideally DB_OWNER on the LF DB's), and has elevated rights on the LF server itself (ideally local admin). However this user will likely have no rights on the SMB share on domain B.

I'm guessing what you'd need to do is grant the domain A user, access to the SMB share on Domain B via a domain trust of some sort, and then map the drive in the LF admin console in the format \\domainbserver.domain.local\sharename\volumename.

I can't say I've ever tried to host the LF volumes on a different domain to the LF server, nor am I sure this is supported (LF will need to confirm).

Asking the obvious question, why does the LF volume need to be on a different domain to the LF server/s?

Cheers!

Chris Douglas

1 0

replied on December 29, 2021

Hi Chris,

Thanks for your answer!

I also thought of the same solution (giving domain A some sort of domain trust on B) but, by request of the cybersecurity department, this cannot be done.

The reason why volumes need to be stored on a different domain is that I have ran out of storage on my domain A, but I got available storage on Domain B and would like to use it. Therefore, I have been asked to research on this subject but had no success.

0 0

replied on December 29, 2021

Hi David,

Ahhh ok, this makes a little more sense. Although back to my original point, I'm not entirely sure if this is supported (or ever been done before). It's a pretty unique situation!

Personally I'd focus my effort on trying to find some disk space on domain A (on any server, anywhere!) as I'm fairly certain a split domain configuration will only cause you headaches!

Even a NAS drive on domain A as a temporary solution might work (just consider backup if you do go down that road).

Cheers!

Chris

0 0

replied on December 29, 2021

Hi Chris,

I will consider your suggestions. But will keep exploring this subject.

Thank you!

0 0

You are not allowed to follow up in this post.

Question

Question

Setting up a volume in a Host allocated on a different Domain

Replies

Sign in to reply to this post.