You are viewing limited content. For full access, please sign in.

Question

Question

Connecting to Web Access outside internal network

asked on November 19, 2015

Hey all,

 

Just trying to figure out what url needs to be entered when connecting to Web Access outside a network.

 

They have default web site in IIS and Web Access is defaulted to Laserfiche.    I would have thought it to be the server name/Laserfiche.

 

But that would only work internally.

0 0

Answer

SELECTED ANSWER
replied on November 19, 2015

It will at least require the domain name, http://server.example.com/laserfiche (aka the FQDN).  Of course, this name must be resolvable externally and your network must allow http(s) traffic to it, so there may be some DNS and firewall configuration necessary.

0 0

Replies

replied on November 19, 2015

Is the Server exposed to the Internet?

0 0
replied on November 19, 2015

Are you meaning you would like to access Web Access from the public web? If that is the case, the system admin would need to do some port forwarding on the firewall and you would need a public domain name routed to a static ip or have some dynamic dns being updated. Either way, that is not something that is part of a default installation that I'm aware of.

0 0
replied on November 19, 2015

Ah perfect.  Thanks guys.  Yeah I figured they may have to forward to the server to open up.  I will contact them and let them know what ports need to be forwarded and check their domain settings.

0 0
replied on June 2, 2017

We have a client that is trying to do the same thing, make Web Access available outside their internal network.  Which ports need to be opened?  I got the port fowarding part, just need to know which ports?

 

Thank you!

0 0
replied on June 6, 2017

Just 80 (http) or 443 (https).

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.