Unsolved
This post is more than 5 years old
21 Posts
0
2622
May 18th, 2012 09:00
Web access custom settings doesn't work for me.
I want that when an internal user (users with ip from ip1.ip2.0.0/16) tries to access to the web-it vdi through the ssl-gateway, was directly connected to the Virtual Desktop,
i.e. it doesn't have to use the rdp sslGateway. How can I achieve this?
In my VDI, all servers (brokers, web-it, ssl gateway) are multihomed. They are connected to an internal private LAN-A and also a public LAN-B.
All servers use LAN-A (192.168.1.0/24) to talk to each other, and clients can access to the VDI services through public LAN-B (ip1.ip2.0.0/16)
I've an internal web-it portal ( https://vdi.lameuaempresa.com/inet/ ) where only internal users can access to the VDI. So clients connect to the server's public ip to reach it.
External users must access through a secure gateway at https://www.vdi.lameuaempresa.com/inet/ (ssl gateway redirects web, rdp and broker packets
to the PRIVATE IP address of the vdi.lameuaempresa.com (web-it), broker1.lameuaempresa.com (broker), that are only internally reachable)
It seems that it works fine but, internal users with an IP address from ip1.ip2.0.0/16 always connect to the Virtual Desktop through the rdp SSLGateway,
but I want that if an internal user tries to access through the ssl-gateway, it was directly connected to the virual Desktop,
so I've added a custom setting like
Internal:ip1.ip2.*
but it doesn't work for me (I have read the SOL90532 but I think this isn't my problem).
Here you have my websettings.xml file
[...]
false
broker1.vdi.lameuaempresa.com
broker2.vdi.lameuaempresa.com
443
true
SSL
rdp.lameuaempresa.com:8443
192.168.1.15
false
false
true
Internal:ip1.ip2.*
[...]
[...]
https://www.vdi.lameuaempresa.com/inet/
https://vdi.lameuaempresa.com/inet/
[...]
Suggestions?
Thanks.