Reset Search



Why domain enrolled device cannot access Captive Portal pages?

« Go Back


TitleWhy domain enrolled device cannot access Captive Portal pages?
Why laptops enrolled to a domain cannot access captive portal pages while end devices (phones, tablets) can?
  • All Summit WM3000 Series Controllers
  • ExtremeWiNG Controllers
  • WirelessWiNG Controllers
  • ExtremeWiNG Access Points
  • WirelessWiNG Acess Points
  • WiNG 5 Software
Most probably this is due loose configuration of captive portal
VX(config-captive-portal-Domain)# server host WORD
        Specify the IPv4/IPv6 address or Hostname of the internal captive
        portal server (controller or access point). For centralized-controller
        mode this should be a virtual hostname, not an IP address

The problem here could be, that <WORD> does not contain domain information.
When this command is used in following form it might create a problem
VX(config-captive-portal-Domain)# server host wing-captive

Domain enrolled device will add its own domain information and will search for wing-captive.device-domain

To avoid this, always use ip domain-name and add this to server host also
VX(config)# profile vx9000 default-vx9000
VX(config-profile-default-vx9000)# ip domain-name captive-portal

VX(config)# captive-portal Domain
VX(config-captive-portal-Domain)# server host wing-captive.captive-portal

You can confirm that client is redirected to proper link using 
VX# remote-debug captive-portal hosts <CaptivePortal server> clients <MAC> max-events 5000 events all

Additional notes
You can check current domain name using this command
VX# show ip domain-name
IP domain lookup: enable
Domain name:      extr.local




Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255