Hello,
I was wondering if anyone had ever tried publishing NAV 2015 using the "Web Application Proxy" role in Windows Server 2012 R2.
In my testing I have been able to publish the NAV web client but not the Windows Client.
There is a limitation of the WAP role that only allow HTTPS publishing, which could be an issue.
I know the easy way would be to just open/forward the relevant ports straight to the NAV server but thought this might be a little more robust.
Does anyone have any thoughts?
Thanks in advance,
Tom
*This post is locked for comments
Not yet.
According to you have configured it but it's not being access as required. Could you please share the exact error message at connection time for more details?
Is there any firewall to manage the network connectivity because it may be blocked by firewall?
or
It's working locally on that server which you have configured.
Hello Sandeep,
The Web Application Proxy can only publish resources externally as SSL. However the internal resource can be http.
I can get a connection using SSL directly to the server (opening and forwarding the ports). I can also publish the web client via the WAP. However the Windows/RCT client cannot connect.
Have you tried this configuration?
Kind regards
Is there any configration issue?
or
you want to do it on http instaed of https.
Thanks for the link MMV.
I hadn't seen that particular post but while it give a helpful background it doesn't specifically go into enough detail to help solve my question.
I'm really wondering if anyone else has tried this or knows if it doesn't work. It saves it me banging my head against a wall!
Tom
Sohail Ahmed
2
mmv
2
Amol Salvi
2