Wireless Access

When we assign a static IP address to thin clients the controller doesn't list the IP address and the thin client fails to authenticate but you can see the MAC address listed in the dashboard. However if we set the thin clients to use DHCP (Windows) everything works perfectly. Any idea as to what might be going on here? 

 

650 running 6.2.1.9

 

Do you have "enforce dhcp" enabled on the AAA profile in use?

Enforce DHCP is unchecked

Some additional information:

 

The static addresses being used are in a different subnet then the controller and I just noticed that the default gateway for the subnet being used is not listed on the controller. Is it necessary to have the subnet default gateway listed for a client to authenticate? 

What is the output of:

 

show ip access-list validuser

 

 

ip access-list session validuser
validuser
---------
Priority  Source                   Destination  Service  Action  TimeRange  Log  Expired  Queue  TOS  8021P  Blacklist  Mirror  DisScan  ClassifyMedia  IPv4/6
--------  ------                   -----------  -------  ------  ---------  ---  -------  -----  ---  -----  ---------  ------  -------  -------------  ------
1         169.254.0.0 255.255.0.0  any          any      deny                             Low                                                           4
2         any                      any          any      permit                           Low                                                           4
3         fe80::                   any          any      deny                             Low                                                           6
4         any                      any          any      permit                           Low                                                           6

 

 

This is a remote location that is currently closed so not many connections at the moment.

You'll need to make sure the user is placed into the same VLAN/subnet as the
static address. Static IPs and wireless do not work well together.

There is only one VLAN configured at this location. They are using a multinet configuration to access both subnets. One subnet is for production users and the other is used for machines (manufacturing).  

After doing additional testing it doesn't make any difference what subnet is used (192.168.1.x or 192.168.2.x in this case)  if a static IP address is used the device does not seem to authenticate.

It appears that a Windows based machine (laptop in this case) is able to connect successfully using a static address. The 'thin client' devices are the only devices with this issue.

Well to get around the problem I had to create a new DHCP scope and bind each MAC address to a specific IP address. This works and will get me where I need to be but this sure seems strange. 

Hey, anyone has updates or ideas on this? I have the same issue :(

how did you assign an IP address manually to one MAC address?