UCA UCWEB not working from the outside world

[RDECIT]

I'm trying to get some internet presence for our UCA 4.0 server. The ultimate goal is for us to be able to use the UCA app for Andriod and iPhone, but firstly I'd just like to get UCWEB working an then a standard client. However I've fallen at the first hurdle.

Internally

https://uca.company.local/ucweb

works fine. So I've setup NAT and firewall rules to point 80 and 443 to the LAN address of the the UCA server (We're using a SonicWall). From an external location, if I enter

http://server.company.co.uk,

I get the cert warning and then I'm taken to server-manager and quickly to the forbidden page as I've not allowed remote web admin, so thats fine. If I use

http://server.company.co.uk/ucweb,

I get the cert warning again but this time I receive a 404 Not Found like the page is not there.

Am I missing something really simple?

 

[Billz66]

try using this as the url

https://server.company.co.uk/ucweb

That worked for ours

 

[RDECIT]

I've already tried that as per my orginal post on the the last line.

 

[RDECIT]

Just done some more digging. I've added the server.company.co.uk 'A' record to our local DNS server to test.

Now when I browse to

https://server.company.co.uk/ucweb,

I get one cert prompt, then another and then it redirects the URL to

https://localservername.company.local/ucweb.

Obviously, if it tries to do this from outside the network the local details would not be available and would result in the page cannot be found. So moving on, my question is why is it redirecting it and how can I stop it.

 

[boycey9]

What system do you have, according to the engineering guidelines this config is supported on the 5000 but the 3300 is not mentioned.

Thoughts from me are that maybe somthing to do with naming, you need to access the UCA by FQDN and your external name is different to your local name.

 

[RDECIT]

This is linked to a 3300Mxe. Our fqdn internally is different from the external fqdn. Do you think this is the problem?

 

[boycey9]

it could be but we would always install it with a web proxy so we are shooting in the dark somewhat, Try adding an entry for your internal fqdn to your host file with the external ip address and see if it makes a difference.

 

[Mitelpassion]

So you need to use split DNS - which I think you have covered.

Are the URL's the same for accessing both internal and external?

What is the UCA server FQDN as configured during UCA/MSL installation is your 'access' FQDN's the same name?

 

[RDECIT]

The FQDN during install was server.domain.local. But I could use a static 'A' record for internal clients to use the server.company.co.uk.