Tim,

I found mine in "online users".  I looked at the IP address and found that
the machine that couldn't pop the agent up was trying to use the same IP
address.  Our problems have been similar to Tom's and it usually related to
a DHCP shortage or conflict, as mentioned.  Mike Diggins' suggestion to use
heartbeat timers is right on...you must do that or you'll see this problem
over and over.  Incidentally, I've had long long conversations about this
very issue with Cisco, and they acknowledge that it's indeed a problem, but
they rightly point out that the way an enterprise's DHCP server is
configured is out of CCA's scope.  The other thing we can do is to run extra
rich on the pool of DHCP addresses, so that an IP address doesn't have to
immediately be redeployed to a new wireless user.  When we run lean on DHCP,
this problem happens way way more, even with the heartbeat timers.

Cheers.

-Aaron



On Wed, Aug 26, 2009 at 6:05 AM, Tim flynn <[email protected]> wrote:

> Aaron - Stuck in "online users"?  Not the "certified devices"...?
>
> Aaron Abitia wrote:
>
>> Tom, our experience here is that the Agent won't pop up because the CAM
>> still thinks that the IP address is still in use by a different computer.
>>  That is, the couple of machines that you're talking about have gotten new
>> IP addresses from your DHCP server, but the CAM has those same IP addresses
>> attached to different mac addresses in its DB.  The reason for this is often
>> that the the previous machine that had that IP address just didn't log off
>> correctly or something like that.  Do a search in the CAM for the IP
>> addresses that your couple of machines got...you may find that those IP
>> addresses are stuck.  Delete those entries and the Agent will suddenly pop
>> up for your mystery machines.
>>
>> -Aaron, Cal Poly, S.L.O., CA
>>
>>
>> On Tue, Aug 25, 2009 at 10:34 AM, Tom Stachowiak <[email protected]<mailto:
>> [email protected]>> wrote:
>>
>>    I am having an issue where on just a couple of machines the agent
>>    login
>>    window will not pop up not matter what I try.
>>
>>    We are running a full 4.61 cam/cas/client. It is literally just a
>>    couple
>>    of machines, and they just ramdomly dont work. Any ideas?
>>
>>    Tom Stachowiak
>>    D'Youville College
>>    Computer Support Tech
>>
>>
>>
>>
>> --
>> Aaron Abitia
>> Network Analyst
>> Network Administration, ITS
>> Cal Poly State University
>> Tel: 805.756.1295
>>
>
> --
> Tim Flynn
> IT Security Manager
> Illinois State University
> Telecommunications and Networking
>
>


-- 
Aaron Abitia
Network Analyst
Network Administration, ITS
Cal Poly State University
Tel: 805.756.1295

Reply via email to