 Internal resources publishing [message #105977] |
Mon, 02 September 2013 00:34  |
d.kagarlickij
Messages: 22
Registered: September 2013
Location: Kiev
|
|
|
|
Hello!
Inside my company intranet i've got a few web servers:
https:/sharepoint/portal/ 192.168.1.15
https:/exchange/owa/ 192.168.1.6
http:/dynamics/crm/ 192.168.1.16
https:/rds/rdweb/ 192.168.1.4
https:/ca/certsrv/ 192.168.1.3
https:/dc/pswa/ 192.168.1.2
We use Kerio Control 8 as a UTM solution.
We have one public IPv4 address (like 173.252.110.112) and one domain name (like contoso.com).
Now I need to publish services directly to Internet, this way:
https:/portal.contoso.com/
https:/mail.contoso.com/
https:/crm.contoso.com/
https:/rd.contoso.com/
https:/ca.contoso.com/
https:/pswa.contoso.com/
Is it possible by using Kerio Control?
If yes, please, show rule example.
Thank's!
PS: I removed one slash fron http links because rules.
Best regards.
[Updated on: Mon, 02 September 2013 00:36] Report message to a moderator |
|
|
|
| Re: Internal resources publishing [message #105979 is a reply to message #105977] |
Mon, 02 September 2013 03:52  |
mlee (Kerio)
Messages: 211
Registered: October 2012
Location: Sydney
|
|
|
|
AFAIK Kerio Control does not have this functionality.
To make it work I guess you can setup another host and either use reverse proxy/http redirect or URL rewrite.
HTH.
M.
PTSD. BP. OCD. ASPD. BPD. Certified.
|
|
|
|
| Re: Internal resources publishing [message #106009 is a reply to message #105979] |
Mon, 02 September 2013 21:52 |
KursadOlmez
Messages: 25
Registered: December 2006
Location: Ankara - Turkiye
|
|
|
|
Hello,
Right now Kerio Control doesn't have this feature yet. This function is used by ISA Server from the version 2004 with the name "Host Header" in the publishing rules.
It will be useful if Kerio can implement a feature like this.
Regards,
|
|
|
|
| Re: Internal resources publishing [message #106010 is a reply to message #105979] |
Mon, 02 September 2013 21:54 |
silars
Messages: 285
Registered: March 2012
|
|
|
|
This falls under the URL rewrite option that Martin mentioned, but you can also use different ports (other than 80/443) for the other services.
Not very pretty, but should work, depending on the application.
Once on different ports, Control can make internal forwarding decisions.
|
|
|
|
Members
Search
Help
Register
Login
Home
