Community discussions

MikroTik App
 
mcw
just joined
Topic Author
Posts: 14
Joined: Wed Jun 20, 2012 5:58 pm

URL-based filtering instead of port-based filtering

Wed May 14, 2014 12:39 am

Hello,

consider two servers behind a Mikrotik router: one Microsoft Exchange machine running Outlook WebApp (OWA) and one Terminal Server (RDP), which shall be used as Remote Desktop Gateway.

Both servers share the same internet connection (same external IP).

External users must have the possibility to use OWA and RDP, both via HTTPS, port 443.

Just simply forwarding port 443 to one of the machines poses the problem that the service on the other machine cannot be used, as the machine is not reachable from outside. So port-based forwarding does not work for us.

Is there a possibility to direct incoming traffic to the appropriate machine, maybe based on the url. OWA interface is always accessed by the url https://mydomain.com/owa , whereas Remote Desktop Gateway is always reachable by url https://mydomain.com/rdweb .

Thanks for your input :)

M.
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 12695
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: URL-based filtering instead of port-based filtering

Wed May 14, 2014 11:09 pm

What you ask is not MikroTik feature, but IIS feature...
 
DmitriiP
just joined
Posts: 18
Joined: Sat Mar 09, 2013 9:42 pm

Re: URL-based filtering instead of port-based filtering

Wed May 14, 2014 11:55 pm

What the problem map ports?

wan 443 to Outlook WebApp (OWA) 443
and any other port:
wan 444 to rminal Server (RDP) 443

https://mydomain.com:443/owa
https://mydomain.com:444/rdweb

??
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 12695
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: URL-based filtering instead of port-based filtering

Thu May 15, 2014 12:05 am

What the problem map ports?

wan 443 to Outlook WebApp (OWA) 443
and any other port:
wan 444 to rminal Server (RDP) 443

https://mydomain.com:443/owa
https://mydomain.com:444/rdweb

??
MUST BE SOLVED ON IIS SIDE, NOT ON MIKROTIK.
 
DmitriiP
just joined
Posts: 18
Joined: Sat Mar 09, 2013 9:42 pm

Re: URL-based filtering instead of port-based filtering

Thu May 15, 2014 12:43 am

What the problem map ports?
MUST BE SOLVED ON IIS SIDE, NOT ON MIKROTIK.
What IIS have with 2 differend PC?
This can be solved with IIS/apache on single machine with different path/folders for owa and rdweb
 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 12695
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: URL-based filtering instead of port-based filtering

Thu May 15, 2014 2:06 am

https://mydomain.com/ point to one of two server,
when IIS detect "/owa" request, go to it,
if detect https://mydomain.com/rdweb automatically IIS redirect to other server,
and is not requered manually to use : xxx port numbers, are automatic.
 
DmitriiP
just joined
Posts: 18
Joined: Sat Mar 09, 2013 9:42 pm

Re: URL-based filtering instead of port-based filtering

Thu May 15, 2014 3:04 am

 
User avatar
rextended
Forum Guru
Forum Guru
Posts: 12695
Joined: Tue Feb 25, 2014 12:49 pm
Location: Italy
Contact:

Re: URL-based filtering instead of port-based filtering

Thu May 15, 2014 3:56 am

Yes! another way!

No... BETTER WAY!...