Configuring Web access to use a Domain url and non standard port

asked on March 4, 2016 • Show version history

Hi All,

I am sure this is quite simple for someone :-) I am trying to configure web access to work with a non standard external port that points to port 80 on my Web access server.

So my firewall is configured to point port say port 50000 ( external ) to Port 80 Internal all good

Now if i use the URL Http://<MyPublicIPAddreee:50000/Laserfiche nothing happens

BUT if i use Http://<MyPublicIPAddreee:50000/Laserfiche/browse.aspx?repo=<repository name> all works OK and i can access all my repositories and login

This is also the same if i use a custom url :

I have setup a subdomain called laserfiche so i have http://laserfiche.<mydomain>.com pointing to Http://<MyPublicIPAddreee:50000/Laserfiche and this doesn't work

But http://laserfiche.<mydomain>.com pointing to Http://<MyPublicIPAddreee:50000/Laserfiche/browse.aspx?repo=<repository name> does work.

Is there another port i must open, or is there something i need to change on IIS

Hope somone can help

Regards

Mark

0 0

replied on March 4, 2016

The way I would troubleshoot this is by looking in the logs on the various machines to see if they are receiving the requests. For the attempts where "nothing happens", check the IIS logs on the Web Access machine to see if the request made it that far. If not, check the firewall logs to see what it did with the request. We run Web Access on non-default ports all the time, so it's unlikely that it's a problem in Web Access.

0 0

replied on March 4, 2016

Thanks for responsing Brian,

I think what is happening is when i call the url Http://<MyPublicIPAddreee:50000/Laserfiche what i think it is returning is http://<MyPublicAddress>/Laserfiche/browse.aspx?repo=<repository name> i.e from port 80 as IIS is running on port 80. But from the ouside this url is not available.

So hence why it does not respond

0 0

Question

Question

Configuring Web access to use a Domain url and non standard port

Replies

Sign in to reply to this post.