10-26-2011 05:18 AM
This all works 100% no prob, however(!) we want an AP to be able to terminal both within our network (WAN) and from home ADSL! I tried putting both controller IP and firewall in the LMS and when provisioning but no joy. Any ideas? Or does he need two APS??
10-26-2011 05:45 AM
10-26-2011 05:47 AM
Ok thanks for that, I will define the second AP with another AP Group and thus, our internal AP System Profile. We can lable them internal & external. Thanks. :)
10-26-2011 06:01 AM
That would work as well. The trick is, you need different DNS views or completely separate DNS zones so that different address information is offered for the same host record, based on where the AP connects. The AP needs to always going to ask for "controller.foo.com" (or whatever hostname you give it), so DNS needs to be smart enough to know that when the AP is connected internally, it responds that "controller.foo.com" is actually 18.104.22.168, but when the AP is connected externally, it responds that "controller.foo.com" is actually 10.10.10.1.
It's doable, but the complexity will depend on how/where DNS administration is done within your organization.
10-26-2011 06:33 AM