niftybit

Hi, Tagging the VLAN from the controller to the APs was the missing part. Using HP Airwave, I had convinced myself that VLAN 240 was on hardly on any switches, this wasn't entirely true - it was on some of them, which was in turn the exact areas that DSHS Visitor was in use. To further muddy things, one area had DSHS Visitor but it didn't have VLAN 240 set as it's egress VLAN, so worked but not in the correct way by giving out addresses in another VLAN. I've added VLAN 250 to key switches and ports, so now IPs are being given out correctly as they should. Huge thanks for the help received here.

We have a HP MSM765 Integrated Controller Software version: 5.7.3.0-13117 This is mounted in slot C of an E5412zl switch. Amongst the SSIDs on the controller is one called ‘DSHS Visitor’ which uses VLAN 240 and WPA/WPA2. This was set up by a managed service engineer years ago and works perfectly. When I try to make an exact copy for a new one called ‘DSHS Public’ with VLAN 250 clients are unable to get a DHCP IP address. The VSC bindings are set up the same, if I change the binding for ‘DSHS Public’ to use the VLAN 240 profile, it words – but obviously gives out the wrong IP range. The DHCP ranges are set up on our domain controllers the same, and if accessed via ethernet cable addresses are picked up from DHCP. I feel I’m missing something simple, I’ve followed many guides but never find a solution. Any suggestions of what to try next would be very appreciated. Roger.